linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Florian Gamböck" <ml@floga.de>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Promote Snapshot to Subvolume? (again)
Date: Thu, 11 Dec 2014 13:50:03 +0100	[thread overview]
Message-ID: <548992FB.9060404@floga.de> (raw)
In-Reply-To: <54494AA6.60804@pobox.com>

Sorry to come up with an old thread, but I'm really interested if 
something is going on with that idea. It would help in many situations 
if you could "promote" snapshots to "regular" subvolumes.

Let's for example take btrfs-restore: It does not restore snapshots by 
default, which is rather smart, because a snapshot should merely be a 
somewhat older version of an existing subvolume. But let's assume in 
some point in the past, you really messed up your /home and you used a 
snapshot to recreate it, like deleting the dirty /home subvolume and 
snapshotting the latest backup to a writeable /home again. Then, 
whatever the reason be, you see yourself confronted with using the 
btrfs-restore tool. Now per default you cannot restore /home, since it 
is officially a snapshot, but on the other hand, you do not want to 
restore all other snapshots together with /home (without fiddling with 
some regular expression path filter, that is).

To truly achieve the desired outcome, instead of snapshotting a backup 
to /home, you would have had to create a new subvolume /home and to 
reflink-cp all the contents from the snapshot to the new /home. I find 
this somehow irritating, given that snapshotting is almost instantly 
while cp takes quite some time on a big enough /home.

So I hereby want to push this snapshot-promoting request and would be 
interested in the developers' opinions!

-- 
Flo

      reply	other threads:[~2014-12-11 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 18:36 Promote Snapshot to Subvolume? (again) Robert White
2014-12-11 12:50 ` Florian Gamböck [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=548992FB.9060404@floga.de \
    --to=ml@floga.de \
    --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;
as well as URLs for NNTP newsgroup(s).