From: Chris Mason <clm@fb.com>
To: "Diego Call." <diegocg@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Reproducible corruption issue in stable, with possible patch unmerged?
Date: Sat, 7 Nov 2015 15:17:27 -0500 [thread overview]
Message-ID: <20151107201727.GB26661@ret.masoncoding.com> (raw)
In-Reply-To: <CAFhRPx8LiHHuuv+JfZZV+d9+rCDv2Y97WYm-eniFJTBhwKmdsw@mail.gmail.com>
On Sat, Nov 07, 2015 at 04:36:56PM +0100, Diego Call. wrote:
> [repost, since the previous mail was rejected by vger.kernel.org]
>
> I got these messages in my dmesg:
>
> [ 2587.841376] BTRFS error (device sdc1): partial page write in btrfs
> with offset 0 and length 8392704
> [ 2588.814182] BTRFS critical (device sdc1): bad ordered accounting
> left 0 size 4096
>
> With no other errors before. After rebooting I got btrfs
> errors and widespreading filesystem corruption (pool
> of three disks created with -d raid0 and -m raid1)
>
> I reinstalled the system (current arch linux installer, which
> runs 4.2) and started to restore the backup. Surprisingly,
> I got exactly the same errors again. I reinstalled again,
> and after rebooting to the new system, running 4.2.5,
> I tried to restore the backup and got the same messages
> and corruption again. Then I tried reinstalling with
> the 4.1.12 LTS version, and it all worked fine.
>
> Now, the interesting thing is that, after googling this error, I didn't
> found any interesting references except a patch sent to this
> mailing list which seems to fix a problem that causes the same
> error output. The patch doesn't seem to have been merged:
>
Good catch. Can you describe your configuration?
-chris
next prev parent reply other threads:[~2015-11-07 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 15:36 Reproducible corruption issue in stable, with possible patch unmerged? Diego Call.
2015-11-07 20:17 ` Chris Mason [this message]
2015-11-09 19:52 ` dcg
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=20151107201727.GB26661@ret.masoncoding.com \
--to=clm@fb.com \
--cc=diegocg@gmail.com \
--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 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.