From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: USB-to-SATA and RAID
Date: Thu, 25 Jan 2018 01:36:28 +0100 [thread overview]
Message-ID: <20180125003628.GB1756@otheros> (raw)
In-Reply-To: <ea8286c7-d5de-610a-8bd0-40481dfa2cd4@hardwarefreak.com>
Hi,
Many thanks for all the quick and helpful responses so far!
On Tue, Jan 23, 2018 at 06:40:14PM -0600, Stan Hoeppner wrote:
> > Could someone elaborate further on this? Does "interacts very
> > badly" mean that there will be potential data loss / data
> > corruption? Or does "very badly" just mean short, temporary
> > performance issues / lags upon a disk failure?
>
> Potential data loss / data corruption. Don't use USB. Use eSATA instead.
> The list archives of linux-raid and linux-xfs are dotted with USB disk
> horror stories.
Interesting. Do you know what they could be attributed to
technically? Were they usually similar to what Vojtěch had
described, so connectivity issues due to the poor connectors and
thin cables which can often be found with USB? And things then
fell over when for a brief moment connectivity issues occured for
more disks than redundant disks were configured? Or do the extra
latencies with USB create an extended exposure to the write loop
hole in RAID5? Or something else?
Would you guys say that ARM boards with a SATA connector
internally weird to USB (for instance the Ordoid HC2[*]), and then
maybe some SATA Port Multiplier are similarly affected? Or would say
that those are mainly unaffected of the common issues with RAIDs
via SATA over USB?
Regards, Linus
[*]: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G151505170472&tab_idx=2
next prev parent reply other threads:[~2018-01-25 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 20:16 USB-to-SATA and RAID Linus Lüssing
2018-01-23 20:46 ` Wol's lists
2018-01-23 22:23 ` Vojtěch Kletečka
2018-01-24 15:46 ` Wols Lists
2018-01-24 0:40 ` Stan Hoeppner
2018-01-25 0:36 ` Linus Lüssing [this message]
2018-01-25 1:39 ` Stan Hoeppner
2018-01-25 3:32 ` John Stoffel
2018-01-25 15:38 ` Roger Heflin
2018-01-26 11:10 ` Wols Lists
2018-01-25 8:05 ` David Brown
2018-01-26 11:23 ` Linus Lüssing
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=20180125003628.GB1756@otheros \
--to=linus.luessing@c0d3.blue \
--cc=linux-raid@vger.kernel.org \
--cc=stan@hardwarefreak.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).