From: David Chinner <dgc@sgi.com>
To: Barry Naujok <bnaujok@sgi.com>
Cc: David Chinner <dgc@sgi.com>,
linux-xfs@oss.sgi.com,
Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
Subject: Re: can't remove dir
Date: Mon, 22 Oct 2007 11:17:29 +1000 [thread overview]
Message-ID: <20071022011729.GY995458@sgi.com> (raw)
In-Reply-To: <op.t0kpkzft3jf8g2@pc-bnaujok.melbourne.sgi.com>
On Mon, Oct 22, 2007 at 10:42:25AM +1000, Barry Naujok wrote:
> On Mon, 22 Oct 2007 09:50:52 +1000, David Chinner <dgc@sgi.com> wrote:
> >On Fri, Oct 19, 2007 at 12:10:08PM +0200, Louis-David Mitterrand wrote:
> >>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?
>
> Being a symbolic link, xfs_io follows them rather than operates on
> them directory.
Actually, I tested that before posting. If the symlink is dangling,
then the symlink gets the attributes attached to it:
# ls -l /mnt/scratch/
total 0
lrwxrwxrwx 1 root root 22 Oct 22 11:09 foo -> /mnt/scratch/unix.7.gz
# ls -l /mnt/scratch/unix.7.gz
/bin/ls: /mnt/scratch/unix.7.gz: No such file or directory
# xfs_io -f -r -c "lsattr" /mnt/scratch/foo
-------------- /mnt/scratch/foo
# xfs_io -f -c "chattr +i" /mnt/scratch/foo
# xfs_io -f -r -c "lsattr" /mnt/scratch/foo
--i----------- /mnt/scratch/foo
# umount /mnt/scratch
# mount !$
mount /mnt/scratch
# xfs_io -f -r -c "lsattr" /mnt/scratch/foo
--i----------- /mnt/scratch/foo
# xfs_io -f -c "chattr -i" /mnt/scratch/foo -r
# xfs_io -f -r -c "lsattr" /mnt/scratch/foo
-------------- /mnt/scratch/foo
#
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-10-22 1:17 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 [this message]
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=20071022011729.GY995458@sgi.com \
--to=dgc@sgi.com \
--cc=bnaujok@sgi.com \
--cc=linux-xfs@oss.sgi.com \
--cc=vindex+lists-xfs@apartia.org \
/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