From: Chris Murphy <lists@colorremedies.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Small fs
Date: Mon, 12 Sep 2016 08:48:49 -0600 [thread overview]
Message-ID: <CAJCQCtTQfPGndDvL+mrMOMp4MH2E0Gd3xapGT5B9QP53aTi2sQ@mail.gmail.com> (raw)
In-Reply-To: <pan$612d5$bc50d5d7$f1744b5$1e6b9281@cox.net>
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:
[chris@f24m ~]$ mkfs.btrfs -M /dev/sdb
btrfs-progs v4.7.2
See http://btrfs.wiki.kernel.org for more information.
probe of /dev/sdb failed, cannot detect existing filesystem.
ERROR: use the -f option to force overwrite of /dev/sdb
[chris@f24m ~]$ sudo mkfs.btrfs -M /dev/sdb
btrfs-progs v4.7.2
See http://btrfs.wiki.kernel.org for more information.
Label: (null)
UUID: 237d8ab9-b22f-435c-bbd8-2117afa1760c
Node size: 4096
Sector size: 4096
Filesystem size: 1.87GiB
Block group profiles:
Data+Metadata: single 8.00MiB
System: single 4.00MiB
SSD detected: no
Incompat features: mixed-bg, extref, skinny-metadata
Number of devices: 1
Devices:
ID SIZE PATH
1 1.87GiB /dev/sdb
Whereas without the -M
[chris@f24m ~]$ sudo mkfs.btrfs -f /dev/sdb
[sudo] password for chris:
btrfs-progs v4.7.2
See http://btrfs.wiki.kernel.org for more information.
Label: (null)
UUID: a7c79550-10b8-4a4c-9b23-9c9110e30121
Node size: 16384
Sector size: 4096
Filesystem size: 1.87GiB
Block group profiles:
Data: single 8.00MiB
Metadata: DUP 95.56MiB
System: DUP 8.00MiB
SSD detected: no
Incompat features: extref, skinny-metadata
Number of devices: 1
Devices:
ID SIZE PATH
1 1.87GiB /dev/sdb
So with -M, it's single by default..
--
Chris Murphy
next prev parent reply other threads:[~2016-09-12 14:48 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 [this message]
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=CAJCQCtTQfPGndDvL+mrMOMp4MH2E0Gd3xapGT5B9QP53aTi2sQ@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=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 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).