From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Adam Borowski <kilobyte@angband.pl>,
"Lentes, Bernd" <bernd.lentes@helmholtz-muenchen.de>,
Btrfs ML <linux-btrfs@vger.kernel.org>
Subject: Re: SLES 11 SP4: can't mount btrfs
Date: Tue, 24 Oct 2017 10:20:22 -0400 [thread overview]
Message-ID: <7c8034fb-ef03-5185-eeb4-79008313d211@gmail.com> (raw)
In-Reply-To: <CAA91j0UBDVASmicBKjoVrZ9md-+2G_JPNqxqDWpwVUCYhG0bow@mail.gmail.com>
On 2017-10-24 10:12, Andrei Borzenkov wrote:
> On Tue, Oct 24, 2017 at 2:53 PM, Austin S. Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>>
>> SLES (and OpenSUSE in general) does do something special though, they use
>> subvolumes and qgroups to replicate multiple independent partitions (which
>> is a serious pain in the arse), and they have snapshotting with snapper by
>> default as well. On OpenSUSE at least you can dispense with all that crap
>> by telling the installer to not enable snapshot support, not sure about SLES
>> though.
>
> SUSE is using so many subvolumes because
> a) it wants to use snapshot of operating system to enable rollback
> b) data that needs to be part of snapshot includes RPM database
> c) RPM database is located on /var
>
> So they were forced to make /var part of root subvolume and explicitly
> exclude everything below /var by making it separate subvolumes.
>
> Fortunately it is going to change now with both RH and SUSE moving RPM
> database under /usr. Which leaves you basically with / and /var as
> default subvolumes.
>
And /tmp, and /opt, and /usr/local, etc. With /var as one subvolume, I
still count at least 8.
That said, the issue I have with it is not as much the number, as the
choice of layout (the whole /@ crap is ridiculous), and the fact that
qgroups are enabled by default and not very well documented anywhere
that I could find (seriously, this needs to be better documented, it
took me an hour despite my background with BTRFS and as a system
administrator to figure out why I couldn't fill the disk completely
anywhere to wipe free space with zeroes so I could compact the disk
image for the VM I was using).
next prev parent reply other threads:[~2017-10-24 14:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 17:43 SLES 11 SP4: can't mount btrfs Lentes, Bernd
2017-10-19 18:57 ` Lentes, Bernd
2017-10-19 20:04 ` Chris Murphy
2017-10-20 4:09 ` Andrei Borzenkov
2017-10-20 17:26 ` Lentes, Bernd
2017-10-20 18:40 ` Lentes, Bernd
2017-10-21 2:31 ` Duncan
2017-10-21 11:46 ` Lentes, Bernd
2017-10-21 18:07 ` Adam Borowski
2017-10-22 10:36 ` Lentes, Bernd
2017-10-24 11:53 ` Austin S. Hemmelgarn
2017-10-24 13:28 ` Lentes, Bernd
2017-10-24 14:05 ` Austin S. Hemmelgarn
2017-10-24 16:43 ` Lentes, Bernd
2017-10-26 12:18 ` Lentes, Bernd
2017-10-26 12:55 ` Peter Grandi
2017-10-26 16:37 ` Lentes, Bernd
2017-10-26 20:48 ` Peter Grandi
2017-10-26 16:51 ` Andrei Borzenkov
2017-10-26 18:01 ` Lentes, Bernd
2017-10-24 14:12 ` Andrei Borzenkov
2017-10-24 14:20 ` Austin S. Hemmelgarn [this message]
2017-10-20 6:32 ` Duncan
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=7c8034fb-ef03-5185-eeb4-79008313d211@gmail.com \
--to=ahferroin7@gmail.com \
--cc=arvidjaar@gmail.com \
--cc=bernd.lentes@helmholtz-muenchen.de \
--cc=kilobyte@angband.pl \
--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).