From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: spurious full btrfs corruption
Date: Mon, 26 Mar 2018 16:32:04 +0200 [thread overview]
Message-ID: <1522074724.6830.31.camel@scientia.net> (raw)
In-Reply-To: <1521158625.4352.16.camel@scientia.net>
Hey Qu.
Some update on the corruption issue on my Fujitsu notebook:
Finally got around running some memtest on it... and few seconds after
it started I already got this:
https://paste.pics/1ff8b13b94f31082bc7410acfb1c6693
So plenty of bad memory...
I'd say it's probably not so unlikely that *this* was the actual reason
for btrfs-metadata corruption.
It would perfectly fit to the symptom that I saw shortly before the fs
was completely destroyed:
The spurious csum errors on reads that went away when I read the file
again.
I'd guess you also found no further issue with the v1 space cache
and/or the tree log in the meantime?
So it's probably safe to turn them on again?
We(aka you + me testing fixes) can still look in the issue that newer
btrfsprogs no longer recover anything from the broken fs, while older
to.
I can keep the image around, so no reason to hurry from your side.
Cheers,
Chris.
next prev parent reply other threads:[~2018-03-26 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26306A4D-2D8E-4661-B89E-9F050FD184D5@scientia.net>
[not found] ` <BF03A3DF-684D-47FE-A9AD-320256F64763@scientia.net>
[not found] ` <b6b4ed0e-9569-158d-19ad-82c885bab4ec@gmx.com>
[not found] ` <BB977A40-847C-4611-A468-9BF1137CE711@scientia.net>
[not found] ` <d2a14d69-dfa9-8794-6375-03d1b209632f@gmx.com>
[not found] ` <68697875-6E77-49C4-B54E-0FADB94700DA@scientia.net>
[not found] ` <99ee9b31-a38a-d479-5b1d-30e9c942d577@gmx.com>
[not found] ` <A19E863A-F83C-4630-9675-4309CECB318E@scientia.net>
[not found] ` <1b24e69e-2c1e-71af-fb1d-9d32f72cc78c@gmx.com>
[not found] ` <8DB99A3B-6238-497D-A70F-8834CC014DCF@gmail.com>
2018-02-28 8:36 ` Fwd: Re: BUG: unable to handle kernel paging request at ffff9fb75f827100 Qu Wenruo
[not found] ` <1519833022.3714.122.camel@scientia.net>
2018-03-01 1:25 ` spurious full btrfs corruption Qu Wenruo
2018-03-06 0:57 ` Christoph Anton Mitterer
2018-03-06 1:50 ` Qu Wenruo
2018-03-08 14:38 ` Christoph Anton Mitterer
2018-03-08 23:48 ` Qu Wenruo
2018-03-16 0:03 ` Christoph Anton Mitterer
2018-03-21 22:03 ` Christoph Anton Mitterer
2018-03-26 14:32 ` Christoph Anton Mitterer [this message]
2018-03-07 3:09 ` Duncan
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=1522074724.6830.31.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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.