public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
Cc: linux-xfs@oss.sgi.com
Subject: Re: [UNSURE] can't remove dir
Date: Fri, 14 Sep 2007 04:45:31 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709140444131.752@p34.internal.lan> (raw)
In-Reply-To: <20070914084125.GA31074@apartia.fr>



On Fri, 14 Sep 2007, Louis-David Mitterrand wrote:

> On Fri, Sep 14, 2007 at 04:38:22AM -0400, Justin Piszcz wrote:
>>
>> On Fri, 14 Sep 2007, Louis-David Mitterrand wrote:
>>>
>>> While cleaning up /lost+found a directory resisted removal:
>>>
>>> 	sylla:/lost+found# rm 1879629858 -rf
>>> 	rm: cannot remove directory `1879629858': Directory not empty
>>>
>>> The directory _is_ empty and "-rf" should remove it anyway, so this
>>> looks like a fs error.
>>>
>>> This is on debian unstable with 2.6.23-rc6.
>>
>> what does "ls -al 1879629858" say?
>>
>
> I knew someone would ask, and this is slightly insulting ;-)
>
> sylla:/lost+found# ls -al 1879629858
> total 24
> drwxr-xr-x 2 root root   8192 2007-09-14 09:25 ./
> drwxr-xr-x 3 root root 299008 2007-09-14 10:05 ../
>
>

What happens if you reboot to (e.g., knoppix)

and run: xfs_check /dev/that_partition?

and/or:

xfs_repair -n /dev/that_partition?

        -n     No modify mode.  Specifies that xfs_repair should not modify the
               filesystem but should only scan the filesystem and indicate what
               repairs would have been made.

This would be useful to figure out what went wrong.

Justin.

  reply	other threads:[~2007-09-14  8:45 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 [this message]
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
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=Pine.LNX.4.64.0709140444131.752@p34.internal.lan \
    --to=jpiszcz@lucidpixels.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