From: "Andrew E. Mileski" <andrewm@isoar.ca>
To: Francesco Turco <fturco@fastmail.fm>, linux-btrfs@vger.kernel.org
Subject: Re: Frequent btrfs corruption on a USB flash drive
Date: Thu, 07 Jul 2016 18:38:59 -0400 [thread overview]
Message-ID: <577EDA03.9000308@isoar.ca> (raw)
In-Reply-To: <0ad5fc23-9b10-5e95-888d-9717a8fb480d@fastmail.fm>
On 2016-07-07 17:13, Francesco Turco wrote:
>
> On 2016-07-07 23:11, Andrew E. Mileski wrote:
>> How large is this USB flash device?
>
> 64 GB.
>
I don't know if there is an official recommended minimum size for btrfs, but I
would expect 64 GB to be okay.
I've personally set my minimum recommendation for btrfs at 120 GB based on my
experience with failures in various flash devices from 4 to 30 GB.
If you want to experiment, I have a theory that formatting single volumes with
"-m single" can avoid a potential controller race in one specific situation,
plus it helps to reduce the meta overhead on smaller devices.
Lastly, the last two USB issues I investigated were both fixed by replacing the
cables. Something to try if it is a cabled device.
~~
Andrew E. Mileski
next prev parent reply other threads:[~2016-07-07 22:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 13:49 Frequent btrfs corruption on a USB flash drive Francesco Turco
2016-07-07 14:27 ` Austin S. Hemmelgarn
2016-07-07 14:55 ` Francesco Turco
2016-07-07 15:42 ` Austin S. Hemmelgarn
2016-07-07 18:25 ` Chris Murphy
2016-07-07 18:41 ` Francesco Turco
2016-07-07 17:57 ` Chris Murphy
2016-07-08 16:10 ` Francesco Turco
2016-07-08 16:53 ` Austin S. Hemmelgarn
2016-07-08 18:16 ` Henk Slager
2016-07-07 21:11 ` Andrew E. Mileski
2016-07-07 21:13 ` Francesco Turco
2016-07-07 22:38 ` Andrew E. Mileski [this message]
2016-07-07 23:07 ` Chris Murphy
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=577EDA03.9000308@isoar.ca \
--to=andrewm@isoar.ca \
--cc=fturco@fastmail.fm \
--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.