From: Waxhead <waxhead@online.no>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs scrub failure for raid 6 kernel 4.3
Date: Sun, 27 Dec 2015 14:59:18 +0100 [thread overview]
Message-ID: <567FEEB6.3080701@online.no> (raw)
Hi,
I have a "toy-array" of 6x USB drives hooked up to a hub where I made a
btrfs raid 6 data+metadata filesystem.
I copied some files to the filesystem, ripped out one USB drive and
ruined it dd if=/dev/random to various locations on the drive. Put the
USB drive back and the filesystem mounts ok.
If i start scrub I after seconds get the following
kernel:[ 50.844026] CPU: 1 PID: 91 Comm: kworker/u4:2 Not tainted 4.3.0-1-686-pae #1 Debian 4.3.3-2
kernel:[ 50.844026] Hardware name: Acer AOA150/ , BIOS v0.3310 10/06/2008
kernel:[ 50.844026] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs]
kernel:[ 50.844026] task: f642c040 ti: f664c000 task.ti: f664c000
kernel:[ 50.844026] Stack:
kernel:[ 50.844026] 00000005 f0d20800 f664ded0 f86d0262 00000000 f664deac c109a0fc 00000001
kernel:[ 50.844026] f79eac40 edb4a000 edb7a000 edb8a000 edbba000 eccc1000 ecca1000 00000000
kernel:[ 50.844026] 00000000 f664de68 00000003 f664de74 ecb23000 f664de5c f5cda6a4 f0d20800
kernel:[ 50.844026] Call Trace:
kernel:[ 50.844026] [<f86d0262>] ? finish_parity_scrub+0x272/0x560 [btrfs]
kernel:[ 50.844026] [<c109a0fc>] ? set_next_entity+0x8c/0xba0
kernel:[ 50.844026] [<c127d130>] ? bio_endio+0x40/0x70
kernel:[ 50.844026] [<f86891fe>] ? btrfs_scrubparity_helper+0xce/0x270 [btrfs]
kernel:[ 50.844026] [<c107ca7d>] ? process_one_work+0x14d/0x360
kernel:[ 50.844026] [<c107ccc9>] ? worker_thread+0x39/0x440
kernel:[ 50.844026] [<c107cc90>] ? process_one_work+0x360/0x360
kernel:[ 50.844026] [<c10821a6>] ? kthread+0xa6/0xc0
kernel:[ 50.844026] [<c1536181>] ? ret_from_kernel_thread+0x21/0x30
kernel:[ 50.844026] [<c1082100>] ? kthread_create_on_node+0x130/0x130
kernel:[ 50.844026] Code: 6e c1 e8 ac dd f2 ff 83 c4 04 5b 5d c3 8d b6 00 00 00 00 31 c9 81 3d 84 f0 6e c1 84 f0 6e c1 0f 95 c1 eb b9 8d b4 200 00 00 00 0f 0b 8d b4 26 00 00 00 00 8d bc 27 00
kernel:[ 50.844026] EIP: [<c1174858>] kunmap_high+0xa8/0xc0 SS:ESP 0068:f664de40
This is only a test setup and I will keep this filesystem for a while if
it can be of any use...
next reply other threads:[~2015-12-27 14:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 13:59 Waxhead [this message]
2015-12-27 18:29 ` Btrfs scrub failure for raid 6 kernel 4.3 Chris Murphy
2015-12-27 23:06 ` Waxhead
2015-12-28 1:48 ` Duncan
2015-12-28 2:04 ` Waxhead
2015-12-28 2:18 ` Chris Murphy
2015-12-28 21:08 ` Waxhead
2015-12-28 21:23 ` Chris Murphy
[not found] ` <5681BDD0.1060407@online.no>
2015-12-29 0:29 ` Chris Murphy
2015-12-29 20:19 ` Waxhead
2015-12-30 4:22 ` Chris Murphy
2015-12-30 18:31 ` Waxhead
2015-12-30 19:08 ` Waxhead
2015-12-28 4:02 ` Duncan
2015-12-28 21:17 ` Waxhead
2015-12-28 21:50 ` Chris Murphy
2015-12-28 0:39 ` Christoph Anton Mitterer
2015-12-28 0:58 ` Chris Murphy
2015-12-28 1:09 ` Christoph Anton Mitterer
2015-12-28 1:23 ` Chris Murphy
2015-12-28 1:31 ` Christoph Anton Mitterer
2015-12-28 2:16 ` Duncan
2015-12-28 1:21 ` 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=567FEEB6.3080701@online.no \
--to=waxhead@online.no \
--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).