From: Chris Mason <chris.mason@oracle.com>
To: Goffredo Baroncelli <kreijack@gmail.com>
Cc: linux-btrfs@vger.kernel.org, Chris Ball <cjb@laptop.org>
Subject: Re: [RFC] proposal for a btrfs filesystem layout
Date: Fri, 20 Nov 2009 14:54:08 -0500 [thread overview]
Message-ID: <20091120195408.GA3110@think> (raw)
In-Reply-To: <200911201950.06662.kreijack@libero.it>
On Fri, Nov 20, 2009 at 07:50:06PM +0100, Goffredo Baroncelli wrote:
> Hi all,
>
> after the Chirs (Ball) email, I thought about a possible btrfs file-system
> layout, which may permit to snapshot the root and mount (if required) an old
> snapshot of the root.
[ very clear description of a filesystem tree layout ]
>
>
> Any comments ?
This is definitely possible, but not strictly required. We'll be able
to create an ioctl (or mount option) that replaces the default subvolume
('.' in your examples) pointer with a pointer to another subvolume, and
an ioctl to delete the old root.
Basically it will end up hiding the extra layer of indirection your
proposal adds. This doesn't mean your ideas were bad, my plan all along
has been to leave this up to the distros to work out with the users, and
give them enough tools that they have the flexibility to do what they
need.
-chris
next prev parent reply other threads:[~2009-11-20 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 18:50 [RFC] proposal for a btrfs filesystem layout Goffredo Baroncelli
2009-11-20 19:24 ` David Nicol
2009-11-20 19:50 ` Chris Mason
2009-11-20 20:05 ` David Nicol
2009-11-24 1:26 ` Chris Mason
2009-11-20 19:54 ` Chris Mason [this message]
2009-11-20 23:31 ` Goffredo Baroncelli
2009-11-24 1:27 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2009-11-24 18:27 Goffredo Baroncelli
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=20091120195408.GA3110@think \
--to=chris.mason@oracle.com \
--cc=cjb@laptop.org \
--cc=kreijack@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox