From: Jeff Mahoney <jeffm@suse.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: syntax for deleting subvolumes?
Date: Wed, 18 Mar 2015 20:47:29 -0400 [thread overview]
Message-ID: <550A1CA1.9040303@suse.com> (raw)
In-Reply-To: <CAJCQCtRvbiKAQ3iwA6y0QXNaYPnXUh7nf7AGF89Xj48q3GWUpw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 3/18/15 7:33 PM, Chris Murphy wrote:
> On Wed, Mar 18, 2015 at 5:01 PM, K Richard Pixley
> <rpixley@graphitesystems.com> wrote:
>
>> My complaint is a) about multiple subvols and b) about an
>> unnecessary and redundant subvol for the top level file system.
>
> The current granularity supplied by root and home subvolumes is
> minor. Eventually there'd also be a boot subvolume too, but that's
> not supported yet due to a very old grubby bug that's like a booger
> that can't be flicked off.
>
> openSUSE uses ~13 subvolumes by default, for an idea of much finer
> granularity (which I don't like, personally, it's too much and
> really is unnecessary).
We use this layout in SLES too and it's necessary for both compliance
and principle-of-lease-surprise purposes in concert with our
snapshot-rollback facility. If you roll back your root file system,
would you really expect to lose all your logs? How about your mail? Do
you want snapshots of /tmp to hang around eating up disk space,
causing you to reduce the number of snapshots you can retain? Keeping
these as separate subvolumes also allows us to mount them seamlessly
when you boot from a snapshot to either recover or reset your system.
Does it look nice and neat? That's a matter of style. But the reasons
for having separate subvolumes are well thought out and completely
necessary.
BTW, going back to the original issue of why you'd even have a
separate non-top-level subvolume for root - if you boot from a
snapshot and choose to continue from there, you wouldn't be able to
remove the old "root" if it weren't a separate subvolume.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
iQIcBAEBAgAGBQJVChyhAAoJEB57S2MheeWyQoAQAKVJmrh+BA8MBApVqmpOADUi
o7RvsSx0D/2lReqep9p2zCyLq0RCorClP7ESKqu+VXCl4gLkZmLszr1G5btTthk8
524vN0ErR5vb2L7hbZ/Rexkd5+H3CRmKsgLPeHeO8ladx57k1lF3bDEX4J6ssfd/
4MbIhZ/B3Xu8kxe7Te69T/86kL8A0teVesBARRlxewtm1AzMn6ABXVrAIWhJU9rk
vOe+8L/kMXTqOod0cv9wQNKWu5y587dHrrjGsTQ9qcrdTrudbFq0GKzO5gDaFTm+
RZ8LWucjMKdTDzLVxdmt0KxcBCS/fLTWjSoKeVjHk3If/ciFRYM7DZeCxKsmLU1j
5Fwtlm3VjcquzLRyAZST3buJ0atuP9w1Onu2LNKn4xymQlLvoF2U/Fp/gerNiDxe
ZxVBA6JuwG8PktAFqKNYZC9Wd3+BBmYUTyV7JXM5qXbuXZ8uN1O0e0I3XcN3zgh/
56FPQ7cKIe9AxCjxJzlho8ZDQ8kpYB1p+NiGAs7qiCIfsNKwH3ZfuwoBizdagM8M
KmFUVLC/y7b9vVQW5bQX+4NPJU9dmAYe0/dVD68ZK6ROF4b+pV5baP+qlFu8Hp1+
8DFxlG3wJ51WSoZuIvAWV+9y0drhamOONAQ0D1smddnbWvG1HoiL+Z4v36iYc9+3
kGXR3LtcuNWaV5rCjZ3i
=dToy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-03-19 0:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 20:42 syntax for deleting subvolumes? K Richard Pixley
2015-03-18 21:06 ` Chris Murphy
2015-03-18 21:39 ` K Richard Pixley
2015-03-18 21:55 ` Hugo Mills
2015-03-18 23:01 ` K Richard Pixley
2015-03-18 23:33 ` Chris Murphy
2015-03-19 0:47 ` Jeff Mahoney [this message]
2015-03-19 2:55 ` Chris Murphy
2015-03-18 22:15 ` Chris Murphy
2015-03-18 23:22 ` K Richard Pixley
2015-03-18 23:50 ` Chris Murphy
2015-03-19 7:18 ` Erkki Seppala
2015-03-21 3:20 ` Russell Coker
2015-03-19 19:09 ` Chris Murphy
2015-03-20 4:18 ` Duncan
2015-03-21 3:17 ` Russell Coker
2015-03-18 21:09 ` Hugo Mills
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=550A1CA1.9040303@suse.com \
--to=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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.