From: Marc Lehmann <schmorp@schmorp.de>
To: xfs@oss.sgi.com
Subject: Re: corruption, xfs_repair 3.1.4 segfaults, xfs_repair 2.9.8 works
Date: Fri, 4 Mar 2011 18:30:22 +0100 [thread overview]
Message-ID: <20110304173021.GA7912@schmorp.de> (raw)
In-Reply-To: <4D71001D.2040506@sandeen.net> <20110304121407.065d9f17@harpe.intellique.com>
On Fri, Mar 04, 2011 at 12:14:07PM +0100, Emmanuel Florac <eflorac@intellique.com> wrote:
> Lenny's xfs_repair (v 2.9.x IIRC). Just in case, it may do better.
It did, and with a lot fewer scary messages (no -P or -m was necessary):
http://ue.tst.eu/f3860347ab2147d87fdf8f961d6d4358.txt
afterwards, I had the contents of the single directory that caused issues
in lost+found, and no unreadable directories left.
So definitely a regression in 3.1.4.
Thanks a lot for your all your input - I will reformat the partition soon
and restore the files, assuming that the lenny xfs_repair destroyed any
evidence.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-03-04 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:58 corruption, xfs_repair 3.1.4 segfaults Marc Lehmann
2011-03-02 21:43 ` Emmanuel Florac
2011-03-04 7:11 ` Marc Lehmann
2011-03-04 7:51 ` Emmanuel Florac
2011-03-04 10:29 ` Marc Lehmann
2011-03-04 11:14 ` Emmanuel Florac
2011-03-04 16:31 ` Marc Lehmann
2011-03-04 19:18 ` Eric Sandeen
2011-03-04 17:30 ` Marc Lehmann [this message]
2011-03-04 18:17 ` corruption, xfs_repair 3.1.4 segfaults, xfs_repair 2.9.8 works Emmanuel Florac
2011-03-04 15:07 ` corruption, xfs_repair 3.1.4 segfaults Eric Sandeen
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=20110304173021.GA7912@schmorp.de \
--to=schmorp@schmorp.de \
--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.