From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Martin Steigerwald <martin@lichtvoll.de>,
Hugo Mills <hugo@carfax.org.uk>,
linux-btrfs@vger.kernel.org
Subject: Re: Small fs
Date: Mon, 12 Sep 2016 08:45:51 -0400 [thread overview]
Message-ID: <7efbc874-d1e8-011e-20c8-f887aef8a4ac@gmail.com> (raw)
In-Reply-To: <34273168.IdA9o4YR3V@merkaba>
On 2016-09-11 15:51, Martin Steigerwald wrote:
> Am Sonntag, 11. September 2016, 19:46:32 CEST schrieb Hugo Mills:
>> On Sun, Sep 11, 2016 at 09:13:28PM +0200, Martin Steigerwald wrote:
>>> Am Sonntag, 11. September 2016, 16:44:23 CEST schrieb Duncan:
>>>> * Metadata, and thus mixed-bg, defaults to DUP mode on a single-device
>>>> filesystem (except on ssd where I actually still use it myself, and
>>>> recommend it except for ssds that do firmware dedupe). In mixed-mode
>>>> this means two copies of data as well, which halves the usable space.
>>>>
>>>> IOW, when using mixed-mode, which is recommended under a gig, and dup
>>>> replication which is then the single-device default, effective usable
>>>> space is **HALVED**, so 256 MiB btrfs size becomes 128 MiB usable. (!!)
>>>
>>> I don´t get this part. That is just *metadata* being duplicated, not the
>>> actual *data* inside the files. Or am I missing something here?
>>
>> In mixed mode, there's no distinction: Data and metadata both use
>> the same chunks. If those chunks are DUP, then both data and metadata
>> are duplicated, and you get half the space available.
>
> In german I´d say "autsch", in english according to pda.leo.org "ouch", to
> this.
>
> Okay, I just erased using mixed mode as an idea from my mind altogether :).
Until recently (when DUP mode for data on a single device got added), it
did have advantages. If you're running on a single disk and need
replication, it's a lot more efficient to just run a single partition in
DUP mode than two in RAID1 mode. It also makes it a bit less likely to
hit ENOSPC issues on small filesystems.
>
> Just like I think I will never use a BTRFS below 5 GiB. Well, with one
> exception, maybe on the eMMC flash of the new Omnia Turris router that I hope
> will arrive soon at my place.
>
FWIW, I don't use anything smaller than 8G unless I have to (with the
notable exception of /boot), and when I do need to, I usually just use
mixed mode because once you get that small, you need all the help you
can get to keep from the whole FS being allocated to chunks.
next prev parent reply other threads:[~2016-09-12 12:45 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
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 [this message]
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=7efbc874-d1e8-011e-20c8-f887aef8a4ac@gmail.com \
--to=ahferroin7@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
/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).