From: Eric Sandeen <sandeen@sandeen.net>
To: Sean Caron <scaron@umich.edu>
Cc: Leslie Rhorer <lrhorer@mygrande.net>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Corrupted files
Date: Wed, 10 Sep 2014 00:09:08 -0500 [thread overview]
Message-ID: <540FDCF4.3020202@sandeen.net> (raw)
In-Reply-To: <CAA43vkX8Ve3g7=w16742b4vT3=yRdCMR7m66g2M7fYPmEMmctA@mail.gmail.com>
On 9/9/14 5:57 PM, Sean Caron wrote:
> Hey, just sharing some hard-won (believe me) professional experience.
> I have seen xfs_repair take a bad situation and make it worse many
> times. I don't know that a filesystem fuzzer or any other simulation
> can ever provide true simulation of users absolutely pounding the tar
> out of a system. There seems to be a real disconnect between what
> developers are able to test and observe directly, and what happens in
> the production environment in a very high-throughput environment.
>
> Best,
>
> Sean
Fair enough, but I don't want to let stand an assertion that you should
avoid xfs_repair at all (most) costs. It, like almost any software,
has some bugs, but they don't get fixed if they don't get well reported.
We do our best to improve it when we get useful reports from
users - usually including a metadata dump - and we beat on it as best
we can in the lab.
"pounding the tar out of a filesystem" should not, in general, require
an xfs_repair run. ;)
Yes, it's always good advice to do a dry run before committing to a
repair, in case something goes off the rails. But most times I've seen
things go very very badly was when the storage device under the filesystem
was no longer consistent, and the filesystem really had no pieces to
pick up.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-10 5:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 15:21 Corrupted files Leslie Rhorer
2014-09-09 15:50 ` Sean Caron
2014-09-09 16:03 ` Sean Caron
2014-09-09 22:24 ` Eric Sandeen
2014-09-09 22:57 ` Sean Caron
2014-09-10 1:00 ` Roger Willcocks
2014-09-10 1:23 ` Leslie Rhorer
2014-09-10 5:09 ` Eric Sandeen [this message]
2014-09-10 0:48 ` Leslie Rhorer
2014-09-10 1:10 ` Roger Willcocks
2014-09-10 1:31 ` Leslie Rhorer
2014-09-10 14:24 ` Emmanuel Florac
2014-09-10 14:49 ` Sean Caron
2014-09-09 16:08 ` Emmanuel Florac
2014-09-09 22:06 ` Dave Chinner
2014-09-10 1:12 ` Leslie Rhorer
2014-09-10 1:25 ` Sean Caron
2014-09-10 1:43 ` Leslie Rhorer
2014-09-10 14:31 ` Emmanuel Florac
2014-09-10 14:52 ` Grozdan
2014-09-10 15:12 ` Emmanuel Florac
2014-09-10 15:32 ` Grozdan
2014-09-10 14:54 ` Sean Caron
2014-09-10 23:18 ` Leslie Rhorer
2014-09-11 13:24 ` Greg Freemyer
2014-09-12 7:06 ` Emmanuel Florac
2014-09-10 1:53 ` Dave Chinner
2014-09-10 3:10 ` Leslie Rhorer
2014-09-10 3:33 ` Dave Chinner
2014-09-10 4:14 ` Leslie Rhorer
2014-09-10 4:22 ` Leslie Rhorer
2014-09-10 14:34 ` Emmanuel Florac
2014-09-10 4:51 ` Leslie Rhorer
2014-09-10 5:23 ` Dave Chinner
2014-09-11 5:47 ` Leslie Rhorer
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=540FDCF4.3020202@sandeen.net \
--to=sandeen@sandeen.net \
--cc=lrhorer@mygrande.net \
--cc=scaron@umich.edu \
--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