On Fri, Sep 14, 2007 at 07:10:32PM +1000, David Chinner wrote:
>
> Can you tell us the output of 'xfs_info <mntpt>'?
sylla:~# xfs_info /
meta-data=/dev/root isize=256 agcount=41, agsize=15252656 blks
= sectsz=4096 attr=1
data = bsize=4096 blocks=610178720, imaxpct=25
= sunit=16 swidth=80 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=2
= sectsz=4096 sunit=1 blks, lazy-count=0
realtime =none extsz=327680 blocks=0, rtextents=0
> Also, get the inode number of the bad directory (ls -i) and then
> run:
>
> # xfs_db -r -c "inode <inode_num>" -c "p" <device of fs>
sylla:/lost+found# xfs_db -r -c "inode 1879629858" -c "p" /dev/md1
core.magic = 0x494e
core.mode = 040755
core.version = 1
core.format = 2 (extents)
core.nlinkv1 = 2
core.uid = 0
core.gid = 0
core.flushiter = 9
core.atime.sec = Tue Aug 1 20:49:16 2006
core.atime.nsec = 000000000
core.mtime.sec = Fri Sep 14 09:25:29 2007
core.mtime.nsec = 589593557
core.ctime.sec = Fri Sep 14 09:25:29 2007
core.ctime.nsec = 589593557
core.size = 8192
core.nblocks = 3
core.extsize = 0
core.nextents = 2
core.naextents = 0
core.forkoff = 0
core.aformat = 2 (extents)
core.dmevmask = 0
core.dmstate = 0
core.newrtbm = 0
core.prealloc = 0
core.realtime = 0
core.immutable = 0
core.append = 0
core.sync = 0
core.noatime = 0
core.nodump = 0
core.rtinherit = 0
core.projinherit = 0
core.nosymlinks = 0
core.extsz = 0
core.extszinherit = 0
core.nodefrag = 0
core.gen = 0
next_unlinked = null
u.bmx[0-1] = [startoff,startblock,blockcount,extentflag] 0:[0,117476868,2,0]
1:[8388608,125865476,1,0]
> So we can see what the state of the inode is?
>
> BTW, what problem led you to running xfs_repair in the first
> place (i.e. what led to lost+found getting populated)?
The infamous 2.6.17.1 corruption.
Thanks,
|