All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Small fs
Date: Tue, 13 Sep 2016 04:25:05 +0000 (UTC)	[thread overview]
Message-ID: <pan$35973$28ba0970$9a667dbd$d35e0fd9@cox.net> (raw)
In-Reply-To: CAJCQCtTQfPGndDvL+mrMOMp4MH2E0Gd3xapGT5B9QP53aTi2sQ@mail.gmail.com

Chris Murphy posted on Mon, 12 Sep 2016 08:48:49 -0600 as excerpted:

> On Sun, Sep 11, 2016 at 10:54 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> 
>> On the bright side, the double-whammy of being under such tight
>> filesystem size constraints, coupled with finding out you have less
>> than half the space of the filesystem actually available due to
>> default-mixed-mode AND default dup-metadata (thus dup everything),
> 
> I'm not following what you mean by default dup everything. You mean
> that's how it used to work? Because on a real USB stick, 2GiB:


Yes.  What I meant is that now that --mixed isn't default, it avoids auto-
halving the space due to duping the data as well (which AFAIK it used to 
do by default since mixed-mode treated everything as metadata, and 
metadata defaults are dup except on ssd), in mixed-mode.

Tho now that I think of it, it's possible I'm mistaken, since I always 
specify single/dup/raid1/whatever, as well as mixed if I want it, 
choosing not to rely on the defaults, myself.

Which seems a pretty wise choice, with the defaults changing over time, 
sometimes, as with removal of the old default mixed under a GiB, to 
strongly dis-recommended defaults. =:^(

-- 
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


  reply	other threads:[~2016-09-13  4:25 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
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 [this message]
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='pan$35973$28ba0970$9a667dbd$d35e0fd9@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 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.