From: Philip Seeger <p0h0i0l0i0p@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Got 10 csum errors according to dmesg but 0 errors according to dev stats
Date: Tue, 12 May 2015 02:14:34 +0200 [thread overview]
Message-ID: <555145EA.6040009@googlemail.com> (raw)
In-Reply-To: <201505111141.54771.russell@coker.com.au>
> Sounds like you are having errors in your RAM, CPU, motherboard, or hard drive
> cabling. Turn the machine off ASAP and plug the disks into a different system,
> if you keep it running you will make it worse.
>
I know it sounds like it, but the host is fine. The host filesystem (on
which the vm virtual hdd resides) is healthy. Other vms are running on
the same host, no problems there. Just to be sure, I will run memtest,
but I'm pretty sure that's not it. The system is under high load a lot,
but I don't think btrfs would fail because of a slow system.
So I have deleted all those corrupted files in this Arch vm, ran a
scrub, 0 errors, all fixed. I restored them, fixed some other things and
now - I get checksum errors again. Interestingly, it looks like the
corruption is not happening randomly, because the same sqlite files are
affected under ~/.mozilla/ and exactly one library file (ghostscript).
Meanwhile, other vms (not Arch but Fedora and Debian) are running
without a problem (one of them using btrfs as well).
Is it possible that systemd isn't unmounting the filesystem properly, so
it gets corrupted on shutdown? (Juest a wild guess.) Although I'm not
sure if all this happened between reboots.
Philip
next prev parent reply other threads:[~2015-05-12 0:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 14:37 Got 10 csum errors according to dmesg but 0 errors according to dev stats Philip Seeger
2015-05-10 14:58 ` Philip Seeger
[not found] ` <CABR0jERqzkdTJxX_1S5WEZHDzX8=O8P7r+Bk0mesPLsR2n=w8A@mail.gmail.com>
2015-05-10 17:32 ` Philip Seeger
2015-05-11 1:41 ` Russell Coker
2015-05-12 0:14 ` Philip Seeger [this message]
2015-05-12 1:04 ` Paul Jones
2015-05-12 1:37 ` Chris Murphy
2015-05-15 18:40 ` Philip Seeger
2015-05-15 18:33 ` Philip Seeger
2015-05-17 1:53 ` Philip Seeger
2015-05-17 8:19 ` Duncan
2015-05-17 8:36 ` Omar Sandoval
2015-05-17 8:57 ` Duncan
2015-05-23 12:49 ` Philip Seeger
2015-05-23 16:52 ` Duncan
2015-05-27 20:25 ` Philip Seeger
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=555145EA.6040009@googlemail.com \
--to=p0h0i0l0i0p@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 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).