mirror_zfs/tests/runfiles
Paul Zuchowski f12e42cccf zdb -d should accept the numeric objset id
As an alternative to the dataset name, zdb now allows the decimal 
or hexadecimal objset ID to be specified.  When permanent errors
are reported as 2 hexadecimal numbers (objset ID : object ID) in 
zpool status; you can now use 'zdb <pool>[/objset ID] object' to
determine the names of the objset and object which have the error.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Ryan Moeller <ryan@ixsystems.com>
Signed-off-by: Paul Zuchowski <pzuchowski@datto.com>
Closes #9733
2020-01-16 09:22:49 -08:00
..
common.run zdb -d should accept the numeric objset id 2020-01-16 09:22:49 -08:00
linux.run Don't fail to apply umask for O_TMPFILE files 2019-12-13 15:02:23 -08:00
longevity.run OpenZFS 9166 - zfs storage pool checkpoint 2018-06-26 10:07:42 -07:00
Makefile.am ZTS: Add sunos.run to dist data 2020-01-07 12:38:12 -08:00
perf-regression.run OpenZFS 9184 - Add ZFS performance test for fixed blocksize random read/write IO 2018-07-02 13:46:06 -07:00
sunos.run ZTS: Move dumpdev tests to sunos.run 2020-01-03 09:08:23 -08:00