From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Do different btrfs volumes compete for CPU?
Date: Fri, 07 Apr 2017 01:17:59 +0100 [thread overview]
Message-ID: <oc6lrh$k7k$1@blaine.gmane.org> (raw)
In-Reply-To: <e4849b22-8311-f5f7-fa2e-2a56b1b78aa5@rqc.ru>
On 05/04/17 08:04, Marat Khalili wrote:
> On 04/04/17 20:36, Peter Grandi wrote:
>> SATA works for external use, eSATA works well, but what really
>> matters is the chipset of the adapter card.
> eSATA might be sound electrically, but mechanically it is awful. Try to
> run it for months in a crowded server room, and inevitably you'll get
> disconnections and data corruption. Tried different cables, brackets --
> same result. If you ever used eSATA connector, you'd feel it.
Been using eSATA here for multiple disk packs continuously connected for
a few years now for 48TB of data (not enough room in the host for the
disks).
Never suffered am eSATA disconnect.
Had the usual cooling fan fails and HDD fails due to old age.
All just a case of ensuring undisturbed clean cabling and a good UPS?...
(BTRFS spanning four disks per external pack has worked well also.)
Good luck,
Martin
prev parent reply other threads:[~2017-04-07 0:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 7:05 Do different btrfs volumes compete for CPU? Marat Khalili
2017-03-31 11:49 ` Duncan
2017-03-31 12:28 ` Marat Khalili
2017-04-01 2:04 ` Duncan
2017-04-01 10:17 ` Peter Grandi
2017-04-03 8:02 ` Marat Khalili
2017-04-04 17:36 ` Peter Grandi
2017-04-05 7:04 ` Marat Khalili
2017-04-07 0:17 ` Martin [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='oc6lrh$k7k$1@blaine.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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.