From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: subvols and parents - how?
Date: Sat, 12 Dec 2015 04:07:59 +0100 [thread overview]
Message-ID: <1449889679.31388.92.camel@scientia.net> (raw)
In-Reply-To: <1449887577.31388.91.camel@scientia.net>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
On Sat, 2015-12-12 at 03:32 +0100, Christoph Anton Mitterer wrote:
> What's still missing now, IMHO, is:
> - a guide when one should make subvole (e.g. keeping things on the
> root
> fs together, unless it's separate like /var/www is usually, but
> /var/lib typically "corresponds" to a state of /etc and /usr.
I just added that:
https://btrfs.wiki.kernel.org/index.php/SysadminGuide#When_To_Make_Subvolumes
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-12-12 3:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 4:56 subvols and parents - how? Christoph Anton Mitterer
2015-11-24 8:29 ` Duncan
2015-11-24 21:25 ` Christoph Anton Mitterer
2015-11-24 21:55 ` Hugo Mills
2015-11-24 23:20 ` Christoph Anton Mitterer
2015-11-24 23:30 ` Hugo Mills
2015-11-24 23:38 ` Christoph Anton Mitterer
2015-11-27 1:02 ` Duncan
2015-12-09 4:36 ` Christoph Anton Mitterer
2015-12-09 10:53 ` Duncan
2015-12-09 19:04 ` Austin S Hemmelgarn
2015-12-10 3:56 ` Duncan
2015-12-10 12:31 ` Austin S Hemmelgarn
2015-12-12 19:58 ` Christoph Anton Mitterer
2015-11-27 2:02 ` Duncan
2015-12-09 4:38 ` Christoph Anton Mitterer
2015-12-09 11:26 ` Duncan
2015-12-10 21:13 ` subvols, ro- and bind mounts " Christoph Anton Mitterer
2015-12-10 22:36 ` S.J.
2015-12-10 23:41 ` Christoph Anton Mitterer
2015-12-11 2:32 ` Chris Murphy
2015-12-12 20:27 ` Christoph Anton Mitterer
2015-12-12 2:32 ` subvols and parents " Christoph Anton Mitterer
2015-12-12 3:07 ` Christoph Anton Mitterer [this message]
2015-12-12 10:20 ` Duncan
2015-12-09 14:49 ` Axel Burri
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=1449889679.31388.92.camel@scientia.net \
--to=calestyo@scientia.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.