xfs
[Top] [All Lists]

Re: "No such file or directory" (still) (was Re: file corruption during

To: "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx>
Subject: Re: "No such file or directory" (still) (was Re: file corruption during emacs build on XFS logical volume
From: Steve Lord <lord@xxxxxxx>
Date: 08 Jan 2002 08:57:40 -0600
Cc: Linux XFS <linux-xfs@xxxxxxxxxxx>
In-reply-to: <E16NxYk-0003n9-00@ADSL-Bergs.RZ.RWTH-Aachen.DE>
References: <E16NxYk-0003n9-00@ADSL-Bergs.RZ.RWTH-Aachen.DE>
Sender: owner-linux-xfs@xxxxxxxxxxx
OK, so now go into xfs_db again, go back to the same inode and
use the bmap command this will print the locations where there
are blocks in the directory, it should look a little like this:


xfs_db: bmap
data offset 0 startblock 196623 (6/15) count 1 flag 0
data offset 1 startblock 196642 (6/34) count 2 flag 0
data offset 3 startblock 196667 (6/59) count 1 flag 0
data offset 4 startblock 196826 (6/218) count 1 flag 0
data offset 5 startblock 196840 (6/232) count 1 flag 0
data offset 6 startblock 196847 (6/239) count 1 flag 0
data offset 7 startblock 196865 (6/257) count 1 flag 0
data offset 8 startblock 196890 (6/282) count 1 flag 0
data offset 9 startblock 196911 (6/303) count 1 flag 0
data offset 10 startblock 196936 (6/328) count 1 flag 0
data offset 11 startblock 196954 (6/346) count 1 flag 0
data offset 12 startblock 196968 (6/360) count 1 flag 0
data offset 13 startblock 196986 (6/378) count 2 flag 0
data offset 15 startblock 197013 (6/405) count 1 flag 0
data offset 16 startblock 197019 (6/411) count 1 flag 0
data offset 17 startblock 197041 (6/433) count 1 flag 0
data offset 18 startblock 197075 (6/467) count 1 flag 0
data offset 19 startblock 197093 (6/485) count 1 flag 0
data offset 20 startblock 197110 (6/502) count 1 flag 0
data offset 21 startblock 197124 (6/516) count 2 flag 0
data offset 23 startblock 197151 (6/543) count 1 flag 0
data offset 24 startblock 197169 (6/561) count 1 flag 0
data offset 8388608 startblock 196629 (6/21) count 1 flag 0
data offset 8388609 startblock 196665 (6/57) count 2 flag 0
data offset 8388611 startblock 196827 (6/219) count 1 flag 0
data offset 8388612 startblock 196841 (6/233) count 1 flag 0
data offset 8388613 startblock 196864 (6/256) count 1 flag 0
data offset 8388614 startblock 196891 (6/283) count 1 flag 0
data offset 8388615 startblock 196937 (6/329) count 1 flag 0
data offset 8388616 startblock 196955 (6/347) count 1 flag 0
data offset 8388617 startblock 196969 (6/361) count 1 flag 0
data offset 8388618 startblock 197012 (6/404) count 1 flag 0
data offset 8388619 startblock 197018 (6/410) count 1 flag 0
data offset 8388620 startblock 197040 (6/432) count 1 flag 0
data offset 8388621 startblock 197050 (6/442) count 1 flag 0
data offset 8388622 startblock 197092 (6/484) count 1 flag 0
data offset 8388623 startblock 197111 (6/503) count 1 flag 0
data offset 8388624 startblock 197150 (6/542) count 1 flag 0
data offset 8388625 startblock 197168 (6/560) count 1 flag 0
data offset 16777216 startblock 196664 (6/56) count 1 flag 0

One of the data offsets will be 8388614 I hope. Use the
dblock command on this:

dblock 8388614
and then use
p
to print it.

This should be the block it is complaining about.

Steve



-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx


<Prev in Thread] Current Thread [Next in Thread>