From: Alexandre Oliva <oliva@gnu.org>
To: Jerome Haltom <wasabi@cogito.cx>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Q: Why subvolumes?
Date: Sun, 04 Aug 2013 11:56:56 -0300 [thread overview]
Message-ID: <ory58h7bd3.fsf@livre.home> (raw)
In-Reply-To: <CA+V+5QriWTMdyX+M=hi=e_nZkK2oLKhXus8kmjX_KpYPBTRVrw@mail.gmail.com> (Jerome Haltom's message of "Tue, 23 Jul 2013 14:43:13 -0500")
On Jul 23, 2013, Jerome Haltom <wasabi@cogito.cx> wrote:
> Why not just create the new dev_id on the destination snapshot of any
> directory? That way the snapshot can share inodes with is source.
Agreed. Nothing stops us from implementing snapshotting of any
directory whatsoever: all it takes is to take a snapshot of the
subvolume enclosing the directory we want to snapshot, removing
everything that's not in the requested directory from the snapshot, and
making that directory the root of the snapshot. The only tricky bit
here AFAICT is to arrange for the non-snapshotted subtree components to
be cleaned up in background. If we had some primitive to unlink an
entire subtree and clean it up in background we could use that.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
prev parent reply other threads:[~2013-08-04 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 11:59 Q: Why subvolumes? Jerome Haltom
2013-07-23 14:52 ` AW: " Andreas Buschka
2013-07-23 15:06 ` Q: " Hugo Mills
2013-07-23 17:47 ` Gabriel de Perthuis
2013-07-23 19:30 ` Hugo Mills
2013-07-23 19:41 ` Gabriel de Perthuis
2013-07-23 19:43 ` Jerome Haltom
2013-07-23 21:52 ` Chris Murphy
2013-07-23 23:39 ` Jerome Haltom
2013-07-24 1:27 ` Josef Bacik
2013-07-24 2:02 ` Chris Murphy
2013-08-04 14:56 ` Alexandre Oliva [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=ory58h7bd3.fsf@livre.home \
--to=oliva@gnu.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wasabi@cogito.cx \
/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).