From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: csum failed on raid1 even after clean scrub?
Date: Wed, 1 Aug 2018 07:52:58 +0000 (UTC) [thread overview]
Message-ID: <pan$52810$75612769$2a695738$2cb031b6@cox.net> (raw)
In-Reply-To: CAMOu_z0d+CB3JXBgwXtj2gZGTdtCjKOZNHEuB43DxXprubKW=w@mail.gmail.com
Sterling Windmill posted on Mon, 30 Jul 2018 21:06:54 -0400 as excerpted:
> Both drives are identical, Seagate 8TB external drives
Are those the "shingled" SMR drives, normally sold as archive drives and
first commonly available in the 8TB size, and often bought for their
generally better price-per-TB without fully realizing the implications.
There have been bugs regarding those drives in the past, and while I
believe those bugs were fixed and AFAIK current status is no known SMR-
specific bugs, they really are /not/ particularly suited to btrfs usage
even for archiving, and definitely not to general usage (that is, pretty
much anything but the straight-up archiving use-case they are sold for)
use-cases.
Of course USB connections are notorious for being unreliable in terms of
btrfs usage as well, and I'd really hate to think what a combination of
SMR on USB might wreak.
If they're not SMR then carry-on! =:^)
--
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:[~2018-08-01 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 0:43 csum failed on raid1 even after clean scrub? Sterling Windmill
2018-07-31 0:56 ` Qu Wenruo
2018-07-31 1:06 ` Sterling Windmill
2018-08-01 7:52 ` 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$52810$75612769$2a695738$2cb031b6@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 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).