public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: "Grozdan Nikolov (openSUSE Linux)" <microchip@telenet.be>
Cc: xfs@oss.sgi.com
Subject: Re: Cannot delete a directory on a XFS file system
Date: Sun, 13 Jan 2008 15:51:57 -0600	[thread overview]
Message-ID: <478A87FD.60203@sandeen.net> (raw)
In-Reply-To: <200801132238.52075.microchip@telenet.be>

Grozdan Nikolov (openSUSE Linux) wrote:

> I do not know what version is the latest of xfsprogs. I use my distro's 
> default (2.8.11)

Ok, 2.9.4 is latest.  2.8.11 is from Aug 2006.... Perhaps the more
recent version will properly fix your fs.

>From the changelog:

xfsprogs-2.8.15 (19 October 2006)
        - Fix up nlink checks and repairs in phase 7 for xfs_repair.


>> using xfs_metadump to provide a filesystem image for Barry to reproduce
>> with would be helpful.
> 
> I can't find xfs_metadump on my system. I only have xfsdump. Is this the same?

Nope, it's not there in your older xfsprogs.

>>> 3. run ls -lR on the dir that has problems
>>> 4. run ls -li on the director(ies) that cannot be deleted for the inode
>>> #s
>> ls -a on the dir to be sure there are no hidden dotfiles

> ls -a "MusicApps/Loops/loops/Acid Loops/Bass"
> 
> .  ..

Ok, no hidden files.

> 
>> ls -id on the dir to see if it is inode 184549517
> 
> ls -id "MusicApps/Loops/loops/Acid Loops/Bass"

So, the dir you can't delete is the one with the link count mismatch
stated by xfs_check - that's what I figured but wanted to double check.

I'd be willing to bet that the latest xfsprogs would fix this for you.

Alternately some xfs_db hackery could too, but using more recent repair
would be the best route I think.

-Eric

> 184549517 MusicApps/Loops/loops/Acid Loops/Bass
> 
>> -Eric
> 

  reply	other threads:[~2008-01-13 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 16:23 Cannot delete a directory on a XFS file system Grozdan Nikolov (openSUSE Linux)
2008-01-13 19:49 ` Justin Piszcz
2008-01-13 21:26   ` Grozdan Nikolov (openSUSE Linux)
2008-01-13 21:27   ` Eric Sandeen
2008-01-13 21:38     ` Grozdan Nikolov (openSUSE Linux)
2008-01-13 21:51       ` Eric Sandeen [this message]
2008-01-13 22:56         ` Grozdan Nikolov (openSUSE Linux)

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=478A87FD.60203@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=microchip@telenet.be \
    --cc=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