From: Dave Chinner <david@fromorbit.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: broken XFS filesystem not to be repaired by xfs_repair 3.1.2
Date: Thu, 2 Sep 2010 11:52:07 +1000 [thread overview]
Message-ID: <20100902015207.GT705@dastard> (raw)
In-Reply-To: <201009010226.46771@zmi.at>
On Wed, Sep 01, 2010 at 02:26:46AM +0200, Michael Monnerie wrote:
> http://zmi.at/x/big.xfs.metadump.bz2
>
> After I did the big "rm -r" on that 4TB volume, 4 subdirs with a file in
> each are still left even after 20 "xfsrepair;mount;rm -r;umount" cycles.
> So I dare to say it can't be repaired here.
Ok, so those inodes have corrupted data/attribute forks - I'd say
they are victims of the xfs_fsr swapext problems with dynamic
attribute forks.
I'll use the image to write a fix for repair to detect and correct
the problem.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-02 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 0:26 broken XFS filesystem not to be repaired by xfs_repair 3.1.2 Michael Monnerie
2010-09-02 1:52 ` Dave Chinner [this message]
2010-10-09 21:54 ` Michael Monnerie
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=20100902015207.GT705@dastard \
--to=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--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