From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Nikolay Borisov <nborisov@suse.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel paging request at ffff9fb75f827100
Date: Wed, 21 Feb 2018 15:51:44 +0100 [thread overview]
Message-ID: <1519224704.4313.13.camel@scientia.net> (raw)
In-Reply-To: <1519222829.4313.10.camel@scientia.net>
Interestingly, I got another one only within minutes after the scrub:
Feb 21 15:23:49 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 257 ino 7703 off 56852480 csum 0x42d1b69c expected csum 0x3ce55621 mirror 1
Feb 21 15:23:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 257 ino 7703 off 66146304 csum 0xc739c174 expected csum 0x62e6ce8b mirror 1
Feb 21 15:23:56 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 257 ino 7703 off 87212032 csum 0x183aff6d expected csum 0x3dacaab0 mirror 1
The file (a tgz - which seems to unpack fine) was probably read, but
definitely not written to in ages...
SMART for the SSD looks ok...
Strange...
Cheers,
Chris.
next prev parent reply other threads:[~2018-02-21 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 4:09 BUG: unable to handle kernel paging request at ffff9fb75f827100 Christoph Anton Mitterer
2018-02-21 6:34 ` Nikolay Borisov
2018-02-21 14:20 ` Christoph Anton Mitterer
2018-02-21 14:51 ` Christoph Anton Mitterer [this message]
2018-02-21 17:18 ` Christoph Anton Mitterer
2018-02-21 17:56 ` Nikolay Borisov
2018-02-21 17:59 ` Christoph Anton Mitterer
2018-02-21 16:42 ` Christoph Anton Mitterer
2018-02-21 16:48 ` Christoph Anton Mitterer
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=1519224704.4313.13.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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 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).