From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Imran Geriskovan <imran.geriskovan@gmail.com>,
Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Small fs
Date: Mon, 12 Sep 2016 14:55:47 -0400 [thread overview]
Message-ID: <8dc76c71-aa15-8b9d-87e1-c21732a97779@gmail.com> (raw)
In-Reply-To: <CAK5rZE55nTKh7u6B56MaGcoezmgOrbjrkzSt+WipcGO1mjEGsw@mail.gmail.com>
On 2016-09-12 14:46, Imran Geriskovan wrote:
>> Wait wait wait a second:
>> This is 256 MB SINGLE created
>> by GPARTED, which is the replacement of MANUALLY
>> CREATED 127MB DUP which is now non-existant..
>> Which I was not aware it was a DUP at the time..
>> Peeww... Small btrfs is full of surprises.. ;)
>
> What's more, I also have another 128MB SINGLE
> which I've been using for some years and did not
> bother with its DUP/SINGLENESS. And I compared
> them all to draw some conclusions. Heh..
> That's the story.
>
> Verdict is: DUP/SINGLE is a very serious fun stuff
> when used unknowingly. Small btrfs is such a case.
> And third party tools (ex: gparted) plays with it.
>
> Let's warn users with some documentation,
> together with "A formal small fs" behaviour..
I'm not sure about gparted, but the default behavior for mkfs is as follows:
1. Is the device rotational? (check /sys/block/<device>/rotational). If
not, do some extra stuff to try and ID it as an SSD. If it is an SSD,
use SINGLE mode for metadata, otherwise use DUP mode for metadata.
2. Is the FS set for mixed-bg? If so, use the same profile for data as
metadata, otherwise use SINGLE mode for data.
It would not surprise me if gparted switches to single metadata mode for
a small enough FS, but I'm not certain. I do think that they just use
the default selection for mixed-bg though, which means not using it in
current btrfs-progs versions.
next prev parent reply other threads:[~2016-09-12 18:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 15:27 Small fs Imran Geriskovan
2016-09-11 15:32 ` Martin Steigerwald
2016-09-11 16:44 ` Duncan
2016-09-11 18:56 ` Imran Geriskovan
2016-09-11 19:21 ` Martin Steigerwald
2016-09-12 12:41 ` Austin S. Hemmelgarn
2016-09-12 14:09 ` Henk Slager
2016-09-12 14:12 ` Austin S. Hemmelgarn
2016-09-12 14:51 ` Chris Murphy
2016-09-12 14:56 ` Austin S. Hemmelgarn
2016-09-12 3:33 ` Duncan
2016-09-12 14:11 ` Imran Geriskovan
2016-09-12 17:43 ` Imran Geriskovan
2016-09-12 18:46 ` Imran Geriskovan
2016-09-12 18:55 ` Austin S. Hemmelgarn [this message]
2016-09-12 21:32 ` Mike Fleetwood
2016-09-11 19:13 ` Martin Steigerwald
2016-09-11 19:46 ` Hugo Mills
2016-09-11 19:51 ` Martin Steigerwald
2016-09-12 12:45 ` Austin S. Hemmelgarn
2016-09-11 20:33 ` Chris Murphy
2016-09-12 2:00 ` Duncan
2016-09-12 3:03 ` Chris Murphy
2016-09-12 4:54 ` Duncan
2016-09-12 14:48 ` Chris Murphy
2016-09-13 4:25 ` Duncan
2016-09-12 12:54 ` Imran Geriskovan
2016-09-12 13:01 ` Austin S. Hemmelgarn
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=8dc76c71-aa15-8b9d-87e1-c21732a97779@gmail.com \
--to=ahferroin7@gmail.com \
--cc=1i5t5.duncan@cox.net \
--cc=imran.geriskovan@gmail.com \
--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).