From: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
To: linux-xfs@oss.sgi.com
Subject: Re: can't remove dir
Date: Fri, 14 Sep 2007 11:27:21 +0200 [thread overview]
Message-ID: <20070914092712.GA31997@apartia.fr> (raw)
In-Reply-To: <20070914091032.GE734179@sgi.com>
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,
next prev parent reply other threads:[~2007-09-14 9:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 8:09 can't remove dir Louis-David Mitterrand
2007-09-14 8:38 ` [UNSURE] " Justin Piszcz
2007-09-14 8:41 ` Louis-David Mitterrand
2007-09-14 8:45 ` Justin Piszcz
2007-09-14 9:10 ` David Chinner
2007-09-14 9:27 ` Louis-David Mitterrand [this message]
2007-09-16 22:32 ` David Chinner
2007-09-18 2:43 ` Barry Naujok
2007-09-14 14:14 ` Eric Sandeen
2007-09-14 14:18 ` Eric Sandeen
2007-10-17 16:15 ` Louis-David Mitterrand
2007-10-17 16:18 ` Justin Piszcz
2007-10-17 16:30 ` Louis-David Mitterrand
2007-10-17 21:24 ` David Chinner
2007-10-18 13:11 ` Louis-David Mitterrand
2007-10-18 22:07 ` David Chinner
2007-10-19 10:10 ` Louis-David Mitterrand
2007-10-21 23:50 ` David Chinner
2007-10-22 0:42 ` Barry Naujok
2007-10-22 1:17 ` David Chinner
2007-10-22 7:04 ` Louis-David Mitterrand
2007-10-18 1:37 ` Barry Naujok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070914092712.GA31997@apartia.fr \
--to=vindex+lists-xfs@apartia.org \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox