From: Josef Bacik <jbacik@fb.com>
To: Rich Freeman <r-btrfs@thefreemanclan.net>
Cc: Juan Orti Alcaine <juan.orti@miceliux.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Random file system corruption in 3.17 (not BTRFS related...?)
Date: Wed, 15 Oct 2014 16:20:15 -0400 [thread overview]
Message-ID: <543ED6FF.1080501@fb.com> (raw)
In-Reply-To: <CAGfcS_moK9JLoz=nb54iNb_LCu3rtgBkYLkHLceT8eaiLJsL9g@mail.gmail.com>
On 10/15/2014 03:30 PM, Rich Freeman wrote:
> On Wed, Oct 15, 2014 at 10:30 AM, Josef Bacik <jbacik@fb.com> wrote:
>> We've found it, the Fedora guys are reverting the bad patch now, we'll get
>> the fix sent back to stable shortly. Sorry about that.
>
> After reverting this commit, can the bad snapshots be
> deleted/repaired/etc without wiping and restoring the entire
> filesystem? Copying 2.3TB of data isn't a particularly fast
> operation...
>
I would certainly like to make fsck repair this sort of problem, let me
reproduce the corruption locally and then make fsck fix it and then you
can use that. Thanks,
Josef
next prev parent reply other threads:[~2014-10-15 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 16:54 Random file system corruption in 3.17 (not BTRFS related...?) Robert White
2014-10-14 17:22 ` David Arendt
2014-10-14 20:06 ` Robert White
2014-10-14 22:35 ` Duncan
2014-10-15 7:08 ` Juan Orti Alcaine
2014-10-15 8:53 ` Duncan
2014-10-15 13:46 ` Josef Bacik
2014-10-15 14:05 ` Juan Orti Alcaine
2014-10-15 14:30 ` Josef Bacik
2014-10-15 14:34 ` Juan Orti Alcaine
2014-10-15 19:30 ` Rich Freeman
2014-10-15 20:20 ` Josef Bacik [this message]
2014-10-17 16:26 ` Filipe David Manana
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=543ED6FF.1080501@fb.com \
--to=jbacik@fb.com \
--cc=juan.orti@miceliux.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=r-btrfs@thefreemanclan.net \
/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;
as well as URLs for NNTP newsgroup(s).