From: Chris Mason <clm@fb.com>
To: David Arendt <admin@prnet.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send and kernel 3.17
Date: Tue, 7 Oct 2014 09:19:52 -0400 [thread overview]
Message-ID: <1412687992.2562.2@mail.thefacebook.com> (raw)
In-Reply-To: <DC336054-F307-4A86-AD6D-204E700DE9AA@prnet.org>
On Tue, Oct 7, 2014 at 1:25 AM, David Arendt <admin@prnet.org> wrote:
> I did a revert of this commit. After creating a snapshot, the
> filesystem was no longer usable, even with kernel 3.16.3 (crashes 10
> seconds after mount without error message) . Maybe there was some
> previous damage that just appeared now. This evening, I will restore
> from backup and report back.
>
> On October 7, 2014 12:22:11 AM CEST, Chris Mason <clm@fb.com> wrote:
>> On Mon, Oct 6, 2014 at 4:51 PM, David Arendt <admin@prnet.org> wrote:
>>> I just tried downgrading to 3.16.3 again. In 3.16.3 btrfs send is
>>> working without any problem. Afterwards I upgraded again to 3.17
>>> and
>>> the
>>> problem reappeared. So the problem seems to be kernel version
>>> related.
>>
>> [ backref errors during btrfs-send ]
>>
>> Ok then, our list of suspects is pretty short. Can you easily build
>> test kernels?
>>
>> I'd like to try reverting this commit:
>>
>> 51f395ad4058883e4273b02fdebe98072dbdc0d2
Oh no! Reverting this definitely should not have caused corruptions,
so I think the problem was already there. Do you still have the
filesystem image?
Please let us know if you're missing files off the backup, we'll help
pull them out.
-chris
next parent reply other threads:[~2014-10-07 13:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DC336054-F307-4A86-AD6D-204E700DE9AA@prnet.org>
2014-10-07 13:19 ` Chris Mason [this message]
2014-10-07 20:45 ` btrfs send and kernel 3.17 David Arendt
2014-10-07 20:46 ` Chris Mason
2014-10-12 11:11 ` David Arendt
2014-10-12 15:24 ` john terragon
2014-10-12 21:35 ` David Arendt
2014-10-13 4:11 ` David Arendt
2014-10-13 12:40 ` john terragon
2014-10-13 15:40 ` David Arendt
2014-10-13 17:22 ` Rich Freeman
2014-10-13 20:27 ` btrfs random filesystem corruption in " David Arendt
2014-10-13 20:42 ` Rich Freeman
2014-10-13 22:36 ` Duncan
2014-10-14 11:17 ` admin
2014-10-14 21:35 ` Duncan
2014-10-14 22:03 ` Robert White
2014-10-14 22:55 ` Duncan
2014-10-14 17:00 ` David Arendt
2014-10-13 20:48 ` john terragon
2014-10-13 20:55 ` Rich Freeman
2014-10-13 20:57 ` Rich Freeman
2014-10-13 21:22 ` john terragon
2014-10-13 21:25 ` David Arendt
2014-10-13 21:49 ` Duncan
2014-10-13 23:18 ` Rich Freeman
2014-10-14 1:30 ` john terragon
2014-10-13 21:22 ` David Arendt
2014-10-06 18:50 btrfs send and " David Arendt
2014-10-06 19:06 ` Chris Mason
2014-10-06 19:48 ` David Arendt
2014-10-06 20:51 ` David Arendt
2014-10-06 22:22 ` Chris Mason
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=1412687992.2562.2@mail.thefacebook.com \
--to=clm@fb.com \
--cc=admin@prnet.org \
--cc=linux-btrfs@vger.kernel.org \
/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).