All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Rafa Grimán" <rafagriman@gmail.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Empty dir can't be removed ... because it's not empty?
Date: Wed, 11 Jan 2012 09:10:24 +1100	[thread overview]
Message-ID: <20120110221024.GC24410@dastard> (raw)
In-Reply-To: <201201102126.35268.rafagriman@gmail.com>

On Tue, Jan 10, 2012 at 09:26:35PM +0100, Rafa Grimán wrote:
> Hi all :)
> 
> My /home is on an XFS partition all to it's own. The other day the lights went 
> out and when I rebooted, there's an empty directory that can't be erased. This 
> directory is a subdirectory in ~/.kde4/

Is your system using barriers (i.e. mounting with nobarrier option,
or hardware that doesn't support FUA)? Directory corruption like
this on power failure is a classic sign of a voltile drive cache
being lost on power failure.

The output of dmesg from a system boot will tell us what hardware
you have...

> The funny thing about this is that I can rename the directory, but I can't 
> delete it:
> 
> [root@mine albumcovers]# ls
> .  ..  cache
> 
> [root@mine albumcovers]# ls -lah cache/
> total 0
> drwx------ 1 rafa users  6 Jan 10 02:23 .
> drwx------ 3 rafa users 18 Jan 10 02:23 ..
            ^^^

It's link count is 3, meaning that it thinks that there is an entry
in the directory. You need to run xfs_repair to fix it (and whatever
else is broken).

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2012-01-10 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 20:26 Empty dir can't be removed ... because it's not empty? Rafa Grimán
2012-01-10 20:58 ` Markus Trippelsdorf
2012-01-10 22:10 ` Dave Chinner [this message]
2012-01-11 18:28   ` Rafa Grimán

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=20120110221024.GC24410@dastard \
    --to=david@fromorbit.com \
    --cc=rafagriman@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.