From: David Sterba <dsterba@suse.cz>
To: Chris Mason <clm@fb.com>
Cc: Josef Bacik <jbacik@fb.com>,
russell@coker.com.au, linux-btrfs@vger.kernel.org
Subject: Re: GPF on access to presumably corrupted file
Date: Fri, 31 Jan 2014 18:43:20 +0100 [thread overview]
Message-ID: <20140131174320.GI1364@twin.jikos.cz> (raw)
In-Reply-To: <52EBAF11.7080603@fb.com>
On Fri, Jan 31, 2014 at 09:11:29AM -0500, Chris Mason wrote:
> On Fri 31 Jan 2014 09:07:15 AM EST, Josef Bacik wrote:
> >
> >On 01/31/2014 02:24 AM, Russell Coker wrote:
> >>The attached dmesg log shows the results of trying to cat a file on a
> >>BTRFS
> >>filesystem when running the latest Debian/Unstable kernel (upstream
> >>3.12.8
> >>with some Debian patches that probably aren't relevant to BTRFS).
> >>
> >>I've rebooted the Thinkpad in question and repeated the problem after a
> >>reboot. So I am fairly sure that the problem isn't directly caused
> >>by memory
> >>corruption. I presume that it's corruption on disk causing this
> >>repeatable
> >>problem and such corruption could be caused by a memory error (which is
> >>something I've had happen before on a different system). But I don't
> >>think
> >>that such corruption should cause a GPF.
> >>
> >>So while I think we should consider the possibility that the
> >>filesystem was
> >>corrupted due to a hardware fault (of which there are several
> >>possibilities
> >>when dealing with a laptop) the inability to recover seems like a bug in
> >>BTRFS.
> >>
> >>When this happens every process that tries to access the file in
> >>question is
> >>reported as being stuck in D state. Sometimes such processes respond
> >>to kill
> >>-9 (I thought that was impossible) and sometimes they remain until
> >>reboot.
> >>
> >This may be a bug we just fixed in the recent git pull, are you
> >running with compression? If you are try the recent for-linus branch
> >from Chris and see if you still have the problem. Thanks,
> >
>
> It does look like one we fixed, even without compression please give
> for-linus a shot.
Yes it is the bug, https://bugzilla.kernel.org/show_bug.cgi?id=68411 .
prev parent reply other threads:[~2014-01-31 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 7:24 GPF on access to presumably corrupted file Russell Coker
2014-01-31 14:07 ` Josef Bacik
2014-01-31 14:11 ` Chris Mason
2014-01-31 17:43 ` David Sterba [this message]
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=20140131174320.GI1364@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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