From: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
To: linux-xfs@oss.sgi.com
Subject: Re: can't remove dir
Date: Mon, 22 Oct 2007 09:04:25 +0200 [thread overview]
Message-ID: <20071022070425.GA15091@apartia.fr> (raw)
In-Reply-To: <20071021235052.GV995458@sgi.com>
On Mon, Oct 22, 2007 at 09:50:52AM +1000, David Chinner wrote:
> On Fri, Oct 19, 2007 at 12:10:08PM +0200, Louis-David Mitterrand wrote:
> > On Fri, Oct 19, 2007 at 08:07:14AM +1000, David Chinner wrote:
> > > On Thu, Oct 18, 2007 at 03:11:16PM +0200, Louis-David Mitterrand wrote:
> > > > On Thu, Oct 18, 2007 at 07:24:39AM +1000, David Chinner wrote:
> > > > > On Wed, Oct 17, 2007 at 06:15:04PM +0200, Louis-David Mitterrand wrote:
> > > > > > Using a 2.6.23 kernel and after a clean xfs_repair-2.9.4 run I can't
> > > > > > remove that file:
> > > > > >
> > > > > > sylla:/# rm /lost+found/3912672557
> > > > > > rm: cannot remove `/lost+found/3912672557': Operation not permitted
> > > > > >
> > > > > > sylla:/# ls -li /lost+found/3912672557
> > > > > > 3912672557 lrwxrwxrwx 1 root root 9 2006-04-09 19:10 /lost+found/3912672557 -> unix.7.gz
> > > > >
> > > > > Can you post the output of:
> > > > >
> > > > > # xfs_db -r -c "inode 3912672557" -c "p" <device>
> > > >
> > > > Here:
> > > >
> > > > core.magic = 0x494e
> > > > core.mode = 0120777
> > > > core.version = 1
> > > > core.format = 1 (local)
> > > > core.nlinkv1 = 1
> > > .....
> > > > core.immutable = 1
> > > ^^^^^^^^^^^^^^^^^^
> > >
> > > You can't remove this link until you remove the immutable flag.
> > >
> > > # xfs_io -r -c "chattr -i" /lost+found/3912672557
> >
> > sylla:~# xfs_io -r -c "chattr -i" /lost+found/3912672557
> > /lost+found/3912672557: No such file or directory
>
> Strange. This implies that lookup can't find inode # 3912672557.
> We know it is there...
>
> How many other files in the directory? Can you get the inode number
> for the lost+found directory and dump that with xfs_db (as per above)?
>
> Also, what happens if you "touch /lost+found/unix.7.gz" and try again?
sylla:/lost+found# touch /lost+found/unix.7.gz
sylla:/lost+found# l
total 0
lrwxrwxrwx 1 root root 9 2006-04-09 19:10 3912672557 -> unix.7.gz
-rw-r--r-- 1 root root 0 2007-10-22 09:02 unix.7.gz
sylla:/lost+found# xfs_io -r -c "chattr -i" /lost+found/3912672557
sylla:/lost+found# rm 3912672557
rm: remove symbolic link `3912672557'? y
rm: cannot remove `3912672557': Operation not permitted
next prev parent reply other threads:[~2007-10-22 7:06 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
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 [this message]
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=20071022070425.GA15091@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