I've used this to track down the filename and other tidbits using the object ID
from zpool status -v:
errors: The following persistent errors have been detected:
DATASET OBJECT RANGE
zfspool01/nb60openv 292 1835008-1966080
zfspool01/nb60openv 292 2752512-2883584
zdb -vvv zfspool01/nb60openv 292
Object lvl iblk dblk lsize asize type
292 3 16K 128K 25.1M 25.1M ZFS plain file
264 bonus ZFS znode
path /db/data/EMM_DATA.db
atime Sat Feb 10 08:44:07 2007
mtime Sat Feb 10 09:40:19 2007
ctime Sat Feb 10 09:40:19 2007
crtime Sun Oct 8 16:15:31 2006
gen 150
mode 100600
size 26226688
parent 288
links 1
xattr 0
rdev 0x0000000000000000
if the objID from zpool status is in hex, you might need to specify it as
0x..., as in 0x21e382 in your case.
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
