From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs scrub failure for raid 6 kernel 4.3
Date: Mon, 28 Dec 2015 01:21:54 +0000 (UTC) [thread overview]
Message-ID: <pan$ec56c$f5c0c35d$65d6e7dd$4eded2b8@cox.net> (raw)
In-Reply-To: 567FEEB6.3080701@online.no
Waxhead posted on Sun, 27 Dec 2015 14:59:18 +0100 as excerpted:
> I have a "toy-array" of 6x USB drives hooked up to a hub where I made a
> btrfs raid 6 data+metadata filesystem.
Just noting as an aside comment to the main thread...
While doing this with a "toy-array" for experimental purposes is fine and
indeed encouraged, do your research and LOTS of testing before trying to
setup particularly multi-device btrfs over USB for normal use. There
have been a number of trouble reports posted for USB connected devices,
where the trouble simply vanished when the devices were attached via
(e)SATA. Apparently various SATA/USB bridge controllers aren't entirely
reliable, a few USB root hubs likewise (tho the bridge-controllers are
the most common culprit), and USB itself wasn't really designed for this
sort of thing, tho obviously many people use it for attaching storage
today.
Personally, while I might use btrfs on single-device USB attached
storage, I'd be extremely hesitant to do multi-device btrfs via USB, and
would definitely test it (VERY!) well before considering it usable if I
did, as there's just too many ways multiple USB-attached devices can get
out of sync with each other, breaking the filesystem.
--
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
prev parent reply other threads:[~2015-12-28 1:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 13:59 Btrfs scrub failure for raid 6 kernel 4.3 Waxhead
2015-12-27 18:29 ` 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 [this message]
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$ec56c$f5c0c35d$65d6e7dd$4eded2b8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.