summaryrefslogtreecommitdiffstats
path: root/cddl
Commit message (Collapse)AuthorAgeFilesLines
* MFC r264400,r265836:ngie2014-12-315-5/+5
| | | | | | | | | | | | | | r264400: NO_MAN= has been deprecated in favor of MAN= for some time, go ahead and finish the job. ncurses is now the only Makefile in the tree that uses it since it wasn't a simple mechanical change, and will be addressed in a future commit. r265836: Remove last two NO_MAN= in the tree. In both of these cases, MAN= is what is needed.
* MFC r272671:markj2014-12-261-0/+23
| | | | | | | | Treat D keywords as identifiers in certain postfix expressions. This allows one to, for example, access the "provider" field of a struct g_consumer, even though "provider" is a D keyword. PR: 169657
* MFC r275011:markj2014-12-261-3/+3
| | | | | | | | The module load address always needs to be included when setting the dm_*_va fields of dt_module_t. Previously, this was only done on architectures where kernel modules have type ET_REL; this change fixes that. As a result, symbol name resolution in the stack() action now works properly for kernel modules on i386.
* MFC r274337,r274673,274681,r275515:delphij2014-12-2211-39/+180
| | | | | | | | | | | | | | | | | | | | | ZFS large block support. The default recordsize remains at 128KB. A new tunable/sysctl variable, vfs.zfs.max_recordsize is added to allow adjusting the permitted maximum record size, or zfs_max_recordsize, with a default of 1MB. ZFS will not allow setting recordsize greater than zfs_max_recordsize as a safety belt, because larger recordsize means greater read and write latency and more memory usage. Please note that booting from datasets that have recordsize greater than 128KB is not supported (but it's Okay to enable the feature on the pool). Limited safety belt is provided for mounted root filesystem but use caution when using a larger value. Illumos issue: 5027 zfs large block support
* MFC r271695:markj2014-12-052-3/+3
| | | | Fix some incorrect endianness checks.
* MFC r274276: MFV r274271:delphij2014-12-041-2/+25
| | | | | | | | | | | | Improve zdb -b performance: - Reduce gethrtime() call to 1/100th of blkptr's; - Skip manipulating the size-ordered tree; - Issue more (10, previously 3) async reads; - Use lighter weight testing in traverse_visitbp(); Illumos issue: 5243 zdb -b could be much faster
* MFC r274303:delphij2014-12-041-0/+2
| | | | | | | | | | | | Apply upstream 13597:3eac1e8e0f4c (git: illumos-gate@aa846ad9): Initialize tqent_flags in the userland taskq implementation. Without this the assertion of tq->tq_freelist != NULL may fail in taskq_destroy. The problem is that tqent_flags is never initialized in the userland implementation while the kernel one does initialize it. Without proper initialization, the flag may have its lowest bit set, making it treated as TQENT_FLAG_PREALLOC and never removing taskq_ent_t from tq_freelist.
* MFC r272484:rodrigc2014-11-292-4/+8
| | | | | | Add dependencies to various libraries to libzfs and libzpool. Submitted by: sef
* MFC r264852smh2014-11-131-0/+1
| | | | | | Silence compiler warning Sponsored by: Multiplay
* MFC r273370:markj2014-10-281-1/+1
| | | | | Correct the calculation of tcps_rto in the struct tcpcb -> tcpsinfo_t translator.
* MFC r258902:markj2014-10-241-8/+0
| | | | | The uaddr, ufunc, umod and usym functions all seem to work as expected on FreeBSD, so stop hiding them behind a "#if defined(sun)".
* MFC r272806: MFV r272802:delphij2014-10-231-4/+22
| | | | | | | | | | | | | | - Limit ARC for zdb at 256MB. zdb do not typically revisit data in the ARC. - Increase default max_inflight from 200 to 1000 (can be overriden by -I) so we can queue more I/Os when doing scrubbing. - Print status while loading meataslabs for leak detection. Illumos issues: 5169 zdb should limit its ARC size 5170 zdb -c should create more scrub i/os by default 5171 zdb should print status while loading metaslabs for leak detection
* MFC r272599: MFV r272588:delphij2014-10-201-0/+5
| | | | | | | Handle old format deadlist. Illumos issue: 5178 zdb -vvvvv on old-format pool fails in dump_deadlist()
* MFC r272598: MFV r272585:delphij2014-10-201-4/+6
| | | | | | | | Split the godfather zio into CPU number's to reduce lock contention. Illumos issue: 5176 lock contention on godfather zio
* MFC r272502: MFV r272493:delphij2014-10-132-37/+62
| | | | | | | Show individual disk capacity when doing zpool list -v. Illumos issue: 5147 zpool list -v should show individual disk capacity
* MFC r261893: zfs.8: fix garbled options in a sample zfs send -R command lineavg2014-10-071-1/+1
|
* MFC r261892: zpool.8: fix typo in option description of labelclear commandavg2014-10-071-1/+1
|
* MFC r271527: MFV r271511:delphij2014-10-021-12/+6
| | | | | | | | | Use fnvlist_* to make code more readable. Illumos issue: 5135 zpool_find_import_cached() can use fnvlist_* Approved by: re (gjb)
* MFC r271227: MFV r271225:delphij2014-09-251-17/+18
| | | | | | | | | | | | Iterate through all the children instead of returning error when we hit the first error. This makes the error message give more information rather than just the first device that causes problem. Illumos issue: 5118 When verifying or creating a storage pool, error messages only show one device Approved by: re (gjb)
* MFC r271934:smh2014-09-241-3/+8
| | | | | | | | Output boot code warning when zpool upgrade -a is used to add features. PR: 188328 Approved by: re (marius) Sponsored by: Multiplay
* MFC r271222:delphij2014-09-101-1/+1
| | | | | | | Fix typo. Submitted by: Dmitry Morozovsky <marck rinet ru> Approved by: re (gjb)
* MFC r269524:markj2014-08-203-11/+14
| | | | | | Preserve the errno value of an ioctl before calling free(3). Previously, errno was very occasionally being clobbered, resulting in a bogus error from dt_consume() and thus an error from dtrace(1).
* MFC r269430: MFV r269426:delphij2014-08-181-1/+1
| | | | | | | | Double test device size for ztest(1). Illumos issue: 5039 ztest should default to larger device sizes Author: Matthew Ahrens <mahrens@delphix.com>
* MFC r267875:pfg2014-08-161-2/+7
| | | | | | | | | | | | 4251 libdtrace leaks open file handles Illumos commit: 93ed8d0d4b068b95d0bb50d57bb854df462a8485 (partial) Reference: https://www.illumos.org/issues/4251 Discussed with: Robert Mustacchi Obtained from: Illumos
* MFC r257877:markj2014-08-141-3/+1
| | | | | | | | | | | | | Don't try to use the 32-bit drti.o unless the data model is explicitly set to ILP32. Otherwise dtrace -G will attempt to use it on amd64 if it can't determine which data model to use, which happens when -64 is omitted and no object files are provided, e.g. with # dtrace -G -n BEGIN This would result in a linker error, but now works properly. Also remove an unnecessary #ifdef.
* MFC r269776rpaulo2014-08-131-52/+0
| | | | Remove the BROKEN_LIBELF section.
* MFC r269229,269404,269466: MFV r269223:delphij2014-08-121-5/+34
| | | | | | | Change dn->dn_dbufs from linked list to AVL tree. Illumos issues: 4873 zvol unmap calls can take a very long time for larger datasets
* MFC r269118: MFV r269010:delphij2014-08-105-41/+144
| | | | | | | | | | | | | Import Illumos changes to address the following Illumos issues: 4976 zfs should only avoid writing to a failing non-redundant top-level vdev 4978 ztest fails in get_metaslab_refcount() 4979 extend free space histogram to device and pool 4980 metaslabs should have a fragmentation metric 4981 remove fragmented ops vector from block allocator 4982 space_map object should proactively upgrade when feature is enabled 4984 device selection should use fragmentation metric
* MFC r269100:delphij2014-08-082-7/+16
| | | | Diff reduction against Illumos.
* MFC r268621 (smh) + r268625:delphij2014-08-082-2/+4
| | | | | | | | | | | | | Don't report non-native block-size pools under zpool status -x zpool status -x is used to identify pools that are exhibiting errors or are otherwise unavailable, therefore non-native block-size pools shouldn't be reported. Also update man page to clarify other additional conditions which won't cause a pool to be displayed under zpool status -x. Sponsored by: Multiplay
* MFC the cddl/contrib/opensolaris/cmd/zpool portion of r267803 (joel):delphij2014-08-081-1/+0
| | | | mdoc: remove superfluous paragraph macros.
* MFC r265631:markj2014-08-081-1/+1
| | | | | | | | | | Re-apply r248644. This fixes an annoying problem which caused dtrace -c to fail to attach to stripped binaries. With the _r_debug_postinit symbol, dtrace(1) can now set a breakpoint in the victim process after it has registered its DOF table(s) with the kernel. r_debug_state cannot be used for this purpose since it is called before DOF is made available, in which case dtrace(1) cannot create USDT probes before the program begins execution.
* MFC r256571:markj2014-08-042-1/+6
| | | | | | | | | | | | | | | | | | | | | | | Add a function, memstr, which can be used to convert a buffer of null-separated strings to a single string. This can be used to print the full arguments of a process using execsnoop (from the DTrace toolkit) or with the following one-liner: dtrace -n 'syscall::execve:return {trace(curpsinfo->pr_psargs);}' Note that this relies on the process arguments being cached via the struct proc, which means that it will not work for argvs longer than kern.ps_arg_cache_limit. However, the following rather non-portable script can be used to extract any argv at exec time: fbt::kern_execve:entry { printf("%s", memstr(args[1]->begin_argv, ' ', args[1]->begin_envv - args[1]->begin_argv)); } The debug.dtrace.memstr_max sysctl limits the maximum argument size to memstr().
* MFC r268855: MFV r268848:delphij2014-08-021-6/+37
| | | | | | | | | | | | | | | | | | Instead of asserting all zio's be properly aligned, only assert on the logical ones. Cap uberblocks at 8k, otherwise with ashift=17, there would be only one uberblock. This fixes a problem that zdb would trip assert on pools with ashift >= 0xe (8k). While there, also change the code so it only attempt to condense space map unless the uncondensed size consumes greater than zfs_metaslab_condense_block_threshold blocks. Illumos issue: 4958 zdb trips assert on pools with ashift >= 0xe
* MFC r264486:markj2014-07-291-0/+5
| | | | | Use the correct format specifiers for wide characters and strings of wide characters.
* MFC r262669:markj2014-07-291-30/+58
| | | | | | | | | | When our linker merges .SUNW_dof sections from multiple files, it simply concatenates the DOF tables into one section. Previously, the USDT init code in drti.o would only look at the first table in the DOF section; with this change, it iterates over all the tables, passing each DOF table to the kernel. PR: 186821
* MFC r268720: MFV r268714:delphij2014-07-291-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improve extreme rewind import. When doing an "extreme rewind" import ("zpool import -XF"), we attempt to verify all data in the pool, essentially scrubbing the entire pool. The problem is that spa_load_verify_cb() issues an unbounded number of concurrent scrub i/os. This can lead to all of memory being used for these zio's, wedging the system. Like normal scrub, we need to put a cap on the number of outstanding i/os, and have the traverse thread block when we reach this cap. For this purpose the cap can be very large (10,000) to optimize the elevator algorithm. Three kernel tunables have been added: vfs.zfs.spa_load_verify_maxinflight vfs.zfs.spa_load_verify_metadata vfs.zfs.spa_load_verify_data The latter two tunables controls whether metadata and/or user data when doing extreme rewind. Make 'zpool import -T' imply scrub. Make zpool import -T <txg> accept hexadecimal values for the txg when prefixed with 0x. Skip txg's for which there is no uberblock when doing extreme rewind. Skip reading all user data twice by skipping prefetches when doing extreme rewinds as we do not access via the ARC. Illumos issues: 4970 need controls on i/o issued by zpool import -XF 4971 zpool import -T should accept hex values 4972 zpool import -T implies extreme rewind, and thus a scrub 4973 spa_load_retry retries the same txg 4974 spa_load_verify() reads all data twice
* MFC r268473: MFV r268455:delphij2014-07-232-5/+9
| | | | Use reserved space for ZFS administrative commands.
* MFC r260156: MFV r260152:delphij2014-07-231-2/+2
| | | | 4208 Typo in zfs_main.c: "posxiuser"
* MFC r268470: MFV r268454:delphij2014-07-231-10/+10
| | | | | | | Refresh zpool list for each interval in order to produce fresh output. Illumos issue: 4966 zpool list iterator does not update output
* MFC r268469: MFV r268453:delphij2014-07-232-19/+19
| | | | Diff reduction against Illumos.
* MFC r268116:delphij2014-07-171-10/+17
| | | | | | | | - Fix handling of "new" style of ioctl in compatiblity mode [1]; - Reorganize code and reduce diff from upstream; - Improve forward compatibility shims for previous kernel; Reported by: sbruno [1]
* MFC r268126: MFV r268121:delphij2014-07-151-9/+12
| | | | 4924 LZ4 Compression for metadata
* MFC r268123: MFV r268119:delphij2014-07-153-20/+24
| | | | 4914 zfs on-disk bookmark structure should be named *_phys_t
* MFC r268086: MFV r267570:delphij2014-07-151-1/+3
| | | | 4756 metaslab_group_preload() could deadlock
* MFC r268084: MFV r267568:delphij2014-07-154-7/+49
| | | | 4891 want zdb option to dump all metadata
* MFC r268079: MFV r267566:delphij2014-07-152-2/+3
| | | | | 4390 i/o errors when deleting filesystem/zvol can lead to space map corruption
* MFC r268075: MFV r267565:delphij2014-07-1514-56/+287
| | | | | 4757 ZFS embedded-data block pointers ("zero block compression") 4913 zfs release should not be subject to space checks
* MFC r260142: MFV r258972:delphij2014-07-152-4/+123
| | | | 4373 add block contents print to zstreamdump
* MFC r266771: MFV r266766:delphij2014-07-151-2/+49
| | | | | | | | | | | | | | | | | | | Add a new zfs property, "redundant_metadata" which can have values "all" or "most". The default will be "all", which is the current behavior. When set to all, ZFS stores an extra copy of all metadata. If a single on-disk block is corrupt, at worst a single block of user data (which is recordsize bytes long) can be lost. Setting to "most" will cause us to only store 1 copy of level-1 indirect blocks of user data files. This can improve performance of random writes, because less metadata has to be written. In practice, at worst about 100 blocks (of recordsize bytes each) of user data can be lost if a single on-disk block is corrupt. The exact behavior of which metadata blocks are stored redundantly may change in future releases. Illumos issue: 3835 zfs need not store 2 copies of all metadata
OpenPOWER on IntegriCloud