From: Goffredo Baroncelli <kreijack@inwind.it>
To: Imran Geriskovan <imran.geriskovan@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Accessing Parent Subvolume
Date: Sun, 03 May 2015 09:09:51 +0200 [thread overview]
Message-ID: <5545C9BF.9090500@inwind.it> (raw)
In-Reply-To: <CAK5rZE55PB79N6CeSP-O3ugYfWR-u9dSemht_M6zVEG-KZu3YQ@mail.gmail.com>
On 2015-05-03 08:19, Imran Geriskovan wrote:
> ** QUESTIONS **
> 1- Is it safe to access /mnt/debian ?
> 2- Is it safe to access /mnt/debian/@arch ?
> (Yeah, I'm pushing my chances recursively)
>
>
> ** POSSIBLE ANSWERS **
> X- Sure.. Accessing parent subvolumes recursively is a
> non issue. Even /arch/debian/arch/debian... is no problem.
> (Then, add this to features/decumentation to show how
> generic btrfs subvolume mount machinery is)
It is safe. However I suggest to use the root subvolume only to host other subvolumes.
In your case the layout should be:
/@debian
/@arch
The biggest advantage is that all subvolume are equal, so it could be
manage in the same way when you do a snapshot/rollback...
BR
G.Baroncelli
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
prev parent reply other threads:[~2015-05-03 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 6:19 Accessing Parent Subvolume Imran Geriskovan
2015-05-03 7:09 ` Goffredo Baroncelli [this message]
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=5545C9BF.9090500@inwind.it \
--to=kreijack@inwind.it \
--cc=imran.geriskovan@gmail.com \
--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.