From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Documentation for BTRFS error (device dev): bdev /dev/xx errs: wr 22, rd 0, flush 0, corrupt 0, gen 0
Date: Tue, 23 Feb 2016 23:22:47 +0000 (UTC) [thread overview]
Message-ID: <pan$84c48$1f5c952c$5c23be23$5799c3a@cox.net> (raw)
In-Reply-To: pan$1ce2f$38765775$42544d39$1c9fd0a5@cox.net
Duncan posted on Tue, 23 Feb 2016 23:17:06 +0000 as excerpted:
> Marc MERLIN posted on Tue, 23 Feb 2016 13:59:11 -0800 as excerpted:
>
>> I have a freshly created md5 array, with drives that I specifically
>> scanned one by one block by block, and for good measure, I also scanned
>> the entire software raid with a check command which took 3 days to run.
>>
>> Everything passed.
>>
>> Then, I made a bcache of that device, an ssd that seems to work fine
>> otherwise (brand new), and dmcrypted the result
>>
>> md5 - bache - dmcrypt - btrfs ssd /
>>
>> Now, I'm copying data over with btrfs send, and I'm seeing these slowly
>> show up and the write counter go up one by one.
>> BTRFS error (device dm-7): bdev /dev/mapper/oldds1 errs: wr 17, rd 0,
>> flush 0, corrupt 0, gen 0
>>
>> Where is the documentation for those counters?
>> Is the write error fatal, or a recovered error?
>> Should I consider that my filesystem is corrupted as soon as any of
>> those counters go up?
>> (I couldn't find an exact meaning of each of them)
>
> I believe all formal documentation of what the error counters actually
> mean is developer-level -- "Trust the Source, Luke."
Forgot to mention, tho you're probably already considering it, if this is
the same raid5-backed btrfs you were complaining about being slow in the
other thread, and considering redoing with bcache to an ssd added, as
seems very likely, if it /is/ actually storage device or bus errors, that
could be one reason the previous one was getting so slow... Maybe it
wasn't btrfs after all.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-02-23 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 21:59 Documentation for BTRFS error (device dev): bdev /dev/xx errs: wr 22, rd 0, flush 0, corrupt 0, gen 0 Marc MERLIN
2016-02-23 23:17 ` Duncan
2016-02-23 23:22 ` Duncan [this message]
2016-02-24 0:19 ` Marc MERLIN
2016-02-24 0:38 ` Duncan
2016-03-07 15:13 ` Marc MERLIN
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='pan$84c48$1f5c952c$5c23be23$5799c3a@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).