All of lore.kernel.org
 help / color / mirror / Atom feed
From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: chris.mason@oracle.com, zheng.yan@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Way to quickly "revert back" to a snapshot?
Date: Fri, 30 Oct 2009 15:52:16 +0900	[thread overview]
Message-ID: <4AEA8D20.3020504@jp.fujitsu.com> (raw)
In-Reply-To: <20091026093842.GF5564@think>

I'm trying to make this snapshots/subvolumes listing feature,
I wonder how the interface should be.

I tried to make this feature using ioctl interface, but I don't
know how to notify all subvolume informations because number
of subvolumes are not known before search.
(It may work, that we call number-notify ioctl before subvol-
 listing ioctl itself, or we call subvol-listing ioctl repeatedly
 to last subvolume. But both seem to be not good to me.)

Is there any other idea?

Chris Mason wrote:
> On Sat, Oct 17, 2009 at 01:20:28PM -0400, John Dong wrote:
>> Suppose I want to do test something insane (like a massive OS
>> update) to my system, and create a snapshot before doing so.
>> Afterwards, if I decide my system is hosed and I'd like to revert
>> back to the snapshot and forget any of this actually happened,
>> what's the quickest way of doing it. It seems like by btrfs's design
>> there should be a way to just "set the head" of the filesystem back
>> to the snapshot, like git-reset, right?
> 
> This is near the top of the list of features I want to add for 2.6.33.
> Basically all we need is a way to swap the default subvolume (which is
> just a directory entry) pointer with another subvolume.
> 
> We also want a way to find an snapshot all the subvolumes and snapshots
> underneath a given root.  That way the user won't have to do it
> manually (snapshotting isn't recursive by default).
> 
> If anyone is interested in a coding project, both are fairly easy, just
> let me know.
> 
> -chris
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
taruisi


  reply	other threads:[~2009-10-30  6:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-17 17:20 Way to quickly "revert back" to a snapshot? John Dong
2009-10-26  9:38 ` Chris Mason
2009-10-30  6:52   ` TARUISI Hiroaki [this message]
2009-10-30 15:35     ` Chris Mason
2009-11-02  1:16       ` TARUISI Hiroaki
2009-11-04 21:57     ` David Nicol
2009-11-04 22:33       ` Andrey Kuzmin
2009-11-05  5:31         ` TARUISI Hiroaki

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=4AEA8D20.3020504@jp.fujitsu.com \
    --to=taruishi.hiroak@jp.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zheng.yan@oracle.com \
    /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.