From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: experiences running btrfs on external USB disks?
Date: Tue, 04 Dec 2018 15:13:53 +0900 [thread overview]
Message-ID: <0dcadfd3d9d1a36341d017ca4804e2b6@wpkg.org> (raw)
In-Reply-To: <CAJCQCtRCu5ED+L+j0vWaiPO1ujm=MpMTxD1OvW1v3ZYpT_SMyw@mail.gmail.com>
On 2018-12-04 14:59, Chris Murphy wrote:
>> Running 4.19.6 right now, but was experiencing the issue also with
>> 4.18
>> kernels.
>>
>>
>>
>> # btrfs device stats /data
>> [/dev/sda1].write_io_errs 0
>> [/dev/sda1].read_io_errs 0
>> [/dev/sda1].flush_io_errs 0
>> [/dev/sda1].corruption_errs 0
>> [/dev/sda1].generation_errs 0
>
>
> Hard to say without a complete dmesg; but errno=-5 IO failure is
> pretty much some kind of hardware problem in my experience. I haven't
> seen it be a bug.
It is a complete dmesg - in sense:
# grep -i btrfs -A5 -B5 /var/log/syslog
Dec 4 05:06:56 step snapd[747]: udevmon.go:184: udev monitor observed
remove event for unknown device
"/sys/skbuff_head_cache(1481:anacron.service)"
Dec 4 05:06:56 step snapd[747]: udevmon.go:184: udev monitor observed
remove event for unknown device "/sys/buffer_head(1481:anacron.service)"
Dec 4 05:06:56 step snapd[747]: udevmon.go:184: udev monitor observed
remove event for unknown device
"/sys/ext4_inode_cache(1481:anacron.service)"
Dec 4 05:15:01 step CRON[9352]: (root) CMD (command -v debian-sa1 >
/dev/null && debian-sa1 1 1)
Dec 4 05:17:01 step CRON[9358]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
Dec 4 05:23:13 step kernel: [77760.444607] BTRFS error (device sdb1):
bad tree block start, want 378372096 have 0
Dec 4 05:23:13 step kernel: [77760.550933] BTRFS error (device sdb1):
bad tree block start, want 378372096 have 0
Dec 4 05:23:13 step kernel: [77760.550972] BTRFS: error (device sdb1)
in __btrfs_free_extent:6804: errno=-5 IO failure
Dec 4 05:23:13 step kernel: [77760.550979] BTRFS info (device sdb1):
forced readonly
Dec 4 05:23:13 step kernel: [77760.551003] BTRFS: error (device sdb1)
in btrfs_run_delayed_refs:2935: errno=-5 IO failure
Dec 4 05:23:13 step kernel: [77760.553223] BTRFS error (device sdb1):
pending csums is 4096
Dec 4 05:23:14 step postfix/pickup[8993]: 13BBE460F86: uid=0
from=<root@step>
Dec 4 05:23:14 step postfix/cleanup[9398]: 13BBE460F86:
message-id=<20181204052314.13BBE460F86@step>
Dec 4 05:23:14 step postfix/qmgr[2745]: 13BBE460F86: from=<root@step>,
size=404, nrcpt=1 (queue active)
Dec 4 05:23:14 step postfix/pickup[8993]: 40A964603EC: uid=0
from=<root@step>
[...some emails follow, usual CRON messages etc., but noting at all
generated by the kernel, no hardware issue reported...]
Tomasz Chmielewski
next prev parent reply other threads:[~2018-12-04 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 5:37 experiences running btrfs on external USB disks? Tomasz Chmielewski
2018-12-04 5:59 ` Chris Murphy
2018-12-04 6:13 ` Tomasz Chmielewski [this message]
2018-12-04 12:38 ` Austin S. Hemmelgarn
2018-12-04 13:37 ` Graham Cobb
2018-12-04 13:55 ` Austin S. Hemmelgarn
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=0dcadfd3d9d1a36341d017ca4804e2b6@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).