linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: "Zoltán Ivánfi" <zoltan1980@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Is it safe to use btrfs on top of different types of devices?
Date: Mon, 16 Oct 2017 07:53:58 -0400	[thread overview]
Message-ID: <d27ec863-d4fb-3ffd-78a4-c12789054bd9@gmail.com> (raw)
In-Reply-To: <CAGtRCvfqUP_79cKC_Rzs6MD_uZiVbjt9QW0_BeOpACN_c3ev5w@mail.gmail.com>

On 2017-10-15 04:30, Zoltán Ivánfi wrote:
> Hi,
> 
> Thanks for the replies.
> 
> As you both pointed out, I shouldn't have described the issue having
> to do with hotplugging. I got confused by this use-case being somewhat
> emphasized in the description of the bug I linked to. As for the
> question of why I think that I got bitten by that bug in particular:
> It matches my experiences as I can recall them (used RAID on SATA+USB,
> got bio too big device error messages, data got corrupted).
The actual issue isn't exactly just USB, but externally connected 
hot-pluggable devices on unreliable buses, which mostly consists of USB, 
but also includes things like IEEE 1394 and eSATA (although eSATA isn't 
always an issue, it depends on the cabling and the physical connections).
> 
> You assumed correctly that what I really wanted to ask about was btrfs
> on SATA+USB, thanks for answering that questions as well. Based on
> your replies I feel assured that btrfs should not be affected by this
> particular issue due to operating on the filesystem level and not on
> the block device level; but USB connectivity issues can still lead to
> problems.
Indeed, and I would in fact personally recommend against using USB for 
any kind of always connected persistent storage if at all possible. 
Even if the USB controller, storage controller, and cabling are 100% 
reliable, you still run a pretty significant risk of issues just from 
bumping the system because USB-A and USB-C connectors do not provide 
particularly solid connections from a mechanical perspective.
> 
> Do these USB connectivity issues lead to data corruption? Naturally
> for raid0 they will, but for raid1 I suppose they shouldn't as one
> copy of the data remains intact.
For raid1, they _normally_ won't cause data corruption with BTRFS, 
provided you ensure proper maintenance of the filesystem.  They will 
however cause performance issues, even if you're using USB 3.0 or 3.1, 
as you will end up re-writing bits and pieces of the filesystem 
regularly (because you will need to scrub regularly to avoid data 
corruption).


  parent reply	other threads:[~2017-10-16 11:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-14 19:00 Is it safe to use btrfs on top of different types of devices? Zoltán Ivánfi
2017-10-15  0:19 ` Peter Grandi
2017-10-15  3:42 ` Duncan
2017-10-15  8:30 ` Zoltán Ivánfi
2017-10-15 12:05   ` Duncan
2017-10-16 11:53   ` Austin S. Hemmelgarn [this message]
2017-10-16 16:57     ` Zoltan
2017-10-16 17:27       ` Austin S. Hemmelgarn
2017-10-17  1:14         ` Adam Borowski
2017-10-17 11:26           ` Austin S. Hemmelgarn
2017-10-17 11:42             ` Zoltan
2017-10-17 12:40               ` Austin S. Hemmelgarn
2017-10-17 17:06                 ` Adam Borowski
2017-10-17 19:19                   ` Austin S. Hemmelgarn
2017-10-17 20:21                     ` Adam Borowski
2017-10-17 21:56                       ` Zoltán Ivánfi
2017-10-18  4:44                         ` Duncan
2017-10-18 14:07                         ` Peter Grandi
2017-10-18 11:30                       ` Austin S. Hemmelgarn
2017-10-18 11:59                         ` Adam Borowski
2017-10-18 14:30                           ` Austin S. Hemmelgarn
2017-10-18  4:50                     ` Duncan
2017-10-18 13:53               ` Peter Grandi
2017-10-18 14:30                 ` Austin S. Hemmelgarn
2017-10-19 11:01                   ` Peter Grandi
2017-10-19 12:32                     ` Austin S. Hemmelgarn
2017-10-19 18:39                       ` Peter Grandi
2017-10-20 11:53                         ` Austin S. Hemmelgarn
2017-10-19 13:48                     ` Zoltan
2017-10-19 14:27                       ` Austin S. Hemmelgarn
2017-10-19 14:42                         ` Zoltan
2017-10-19 15:07                           ` Austin S. Hemmelgarn
2017-10-19 18:00                         ` Peter Grandi
2017-10-19 17:56                       ` Peter Grandi
2017-10-19 18:59                         ` Peter Grandi

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=d27ec863-d4fb-3ffd-78a4-c12789054bd9@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zoltan1980@gmail.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).