So, I attempting to find the inode from the result of a "zpool status
-v":
errors: The following persistent errors have been detected:
DATASET OBJECT RANGE
cc 21e382 lvl=0 blkid=0
Well, 21e282 appears to not be a valid number for "find . -inum blah"
Any suggestions?
The object number is in hex. 21e282 hex is 2220674 decimal -- give that a whirl. This is all better now thanks to some recent work by Eric Kustarz: 6410433 ''zpool status -v'' would be more useful with filenames This was integrated into Nevada build 57. Jeff On Sat, Feb 10, 2007 at 05:18:05PM -0800, Joe Little wrote:> So, I attempting to find the inode from the result of a "zpool status -v": > > errors: The following persistent errors have been detected: > > DATASET OBJECT RANGE > cc 21e382 lvl=0 blkid=0 > > > Well, 21e282 appears to not be a valid number for "find . -inum blah" > > Any suggestions? > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
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
On 10 February, 2007 - Joe Little sent me these 0,4K bytes:> So, I attempting to find the inode from the result of a "zpool status -v": > > errors: The following persistent errors have been detected: > > DATASET OBJECT RANGE > cc 21e382 lvl=0 blkid=0 > > > Well, 21e282 appears to not be a valid number for "find . -inum blah"Looks very hexadecimal to me.. Try 2220930 instead. /Tomas -- Tomas ?gren, stric at acc.umu.se, http://www.acc.umu.se/~stric/ |- Student at Computing Science, University of Ume? `- Sysadmin at {cs,acc}.umu.se
Hi Joe, Joe Little wrote:> So, I attempting to find the inode from the result of a "zpool status -v": > > errors: The following persistent errors have been detected: > > DATASET OBJECT RANGE > cc 21e382 lvl=0 blkid=0>> Well, 21e282 appears to not be a valid number for "find . -inum blah"It''s not an inode, it''s a ZFS object - see this thread: http://www.opensolaris.org/jive/thread.jspa?messageID=39450&tstart=0 for info on how to track it down. There was a recent putback by EricK for 6410433 which makes zpool status -v a bit more useful in the future. Hope this helps ? cheers, tim -- Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops http://blogs.sun.com/timf
On 2/11/07, Jeff Bonwick <Jeff.Bonwick at sun.com> wrote:> The object number is in hex. 21e282 hex is 2220674 decimal -- > give that a whirl. > > This is all better now thanks to some recent work by Eric Kustarz: > > 6410433 ''zpool status -v'' would be more useful with filenames > > This was integrated into Nevada build 57. > > Jeff > > On Sat, Feb 10, 2007 at 05:18:05PM -0800, Joe Little wrote: > > So, I attempting to find the inode from the result of a "zpool status -v": > > > > errors: The following persistent errors have been detected: > > > > DATASET OBJECT RANGE > > cc 21e382 lvl=0 blkid=0 > > > > > > Well, 21e282 appears to not be a valid number for "find . -inum blah" > > > > Any suggestions?Ok.. but using the hex as suggested gave me an odder error result that I can''t parse.. zdb -vvv tier2 0x21e382 version=3 name=''tier2'' state=0 txg=353444 pool_guid=3320175367383032945 vdev_tree type=''root'' id=0 guid=3320175367383032945 children[0] type=''disk'' id=0 guid=1858965616559880189 path=''/dev/dsk/c3t4d0s0'' devid=''id1,sd at t534245692d494e4350534353493a736e2e37353538346435623365323a305f305f305f30/a'' whole_disk=1 metaslab_array=16 metaslab_shift=33 ashift=9 asize=1500336095232 children[1] type=''disk'' id=1 guid=2406851811694064278 path=''/dev/dsk/c3t5d0s0'' devid=''id1,sd at t534245692d494e4350534353493a736e2e37353538346435623365323a315f305f305f30/a'' whole_disk=1 metaslab_array=13 metaslab_shift=33 ashift=9 asize=1500336095232 children[2] type=''disk'' id=2 guid=4840324923103758504 path=''/dev/dsk/c3t6d0s0'' devid=''id1,sd at t5059582d5342456950534353493a3c4e554c4c3e3a305f305f315f30/a'' whole_disk=1 metaslab_array=4408 metaslab_shift=33 ashift=9 asize=1500336095232 children[3] type=''disk'' id=3 guid=18356839793156279878 path=''/dev/dsk/c3t7d0s0'' devid=''id1,sd at t5059582d5342456950534353493a3c4e554c4c3e3a315f305f305f30/a'' whole_disk=1 metaslab_array=4407 metaslab_shift=33 ashift=9 asize=1500336095232 Uberblock magic = 0000000000bab10c version = 3 txg = 2834960 guid_sum = 12336413438187464178 timestamp = 1171223485 UTC = Sun Feb 11 11:51:25 2007 rootbp = [L0 DMU objset] 400L/200P DVA[0]=<2:3aa12a3600:200> DVA[1]=<3:378957f000:200> DVA[2]=<0:7d2312f200:200> fletcher4 lzjb LE contiguous birth=2834960 fill=3672 cksum=f65361601:5b3233d8018:117d616a33b47:24feff94a90701 Dataset mos [META], ID 0, cr_txg 4, 294M, 3672 objects, rootbp [L0 DMU objset] 400L/200P DVA[0]=<2:3aa12a3600:200> DVA[1]=<3:378957f000:200> DVA[2]=<0:7d2312f200:200> fletcher4 lzjb LE contiguous birth=2834960 fill=3672 cksum=f65361601:5b3233d8018:117d616a33b47:24feff94a90701 Object lvl iblk dblk lsize asize type zdb: dmu_bonus_hold(2220930) failed, errno 2> > _______________________________________________ > > zfs-discuss mailing list > > zfs-discuss at opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >