From: Chris Mason <clm@fb.com>
To: Tomasz Torcz <tomek@pipebreaker.pl>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: unexplainable corruptions 3.17.0
Date: Fri, 17 Oct 2014 08:53:06 -0400 [thread overview]
Message-ID: <1413550386.755.1@mail.thefacebook.com> (raw)
In-Reply-To: <20141017085448.GA1050018@mother.pipebreaker.pl>
On Fri, Oct 17, 2014 at 4:54 AM, Tomasz Torcz <tomek@pipebreaker.pl>
wrote:
> On Fri, Oct 17, 2014 at 04:29:36PM +0800, Liu Bo wrote:
>> On Fri, Oct 17, 2014 at 10:10:09AM +0200, Tomasz Torcz wrote:
>> > On Fri, Oct 17, 2014 at 04:02:03PM +0800, Liu Bo wrote:
>> > > > Recently I've observed some corruptions to systemd's journal
>> > > > files which are somewhat puzzling. This is especially worrying
>> > > > as this is btrfs raid1 setup and I expected auto-healing.
>> > > > read(4, 0x1001000, 65536) = -1 EIO
>> (Input/output error)
>>
>> Well..I don't know exactly what's the cause, but as the file is
>> NOCOW, it writes
>> data in place, have you experienced a hard reboot or something
>> recently?
>
> Nothing like that. Server is on an UPS, there were couple normal
> shutdowns
> this year (few kernel upgrades).
>
>> And any message in dmesg log while getting EIO by reading the file?
>
> Nothing in dmesg, no btrfs messages, no SCSI/SATA errors, nothing.
> That's
> why I find those corruptions mysterious.
> Maybe there is some way to inspect internal btrfs state and find
> out what
> causing the problems? Or maybe this is related to patch mentioned in
> this thread?
This sounds like the problem fixed with some patches to our extent
mapping code that went in with the merge window. I've cherry picked a
few for stable and I'm running them through tests now. They are in my
stable-3.17 branch, and I'll send to Greg once Linus grabs the revert
for the last one.
But, if you want to try that branch out, it may fix this EIO.
Otherwise we'll start sending you debugging.
-chris
next prev parent reply other threads:[~2014-10-17 12:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 9:17 unexplainable corruptions 3.17.0 Tomasz Torcz
2014-10-17 8:02 ` Liu Bo
2014-10-17 8:10 ` Tomasz Torcz
2014-10-17 8:17 ` Hugo Mills
2014-10-20 14:04 ` Zygo Blaxell
2014-10-20 14:52 ` Rich Freeman
2014-10-17 8:29 ` Liu Bo
2014-10-17 8:54 ` Tomasz Torcz
2014-10-17 12:53 ` Chris Mason [this message]
2014-10-17 18:09 ` Rich Freeman
2014-10-18 7:32 ` Chris Samuel
2014-10-19 3:01 ` Chris Samuel
2014-10-20 8:01 ` Marc Dietrich
2014-10-20 9:14 ` Chris Samuel
2014-10-20 19:09 ` Tomasz Torcz
2014-10-17 11:38 ` Duncan
2014-10-17 15:07 ` Chris Murphy
2014-10-17 17:29 ` Tomasz Torcz
2014-10-17 8:17 ` Marc Dietrich
2014-10-17 15:01 ` Chris Murphy
2014-10-20 19:10 ` Tomasz Torcz
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=1413550386.755.1@mail.thefacebook.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tomek@pipebreaker.pl \
/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