All of lore.kernel.org
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Shriramana Sharma <samjnaa@gmail.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Possible to undo subvol delete?
Date: Tue, 2 Dec 2014 16:11:54 +0900	[thread overview]
Message-ID: <547D663A.3020201@jp.fujitsu.com> (raw)
In-Reply-To: <CAH-HCWW+C9VSV0vb5D1SfU+5md8=zfrZiAbK4cqFiGFW4bKR4w@mail.gmail.com>

Hi,

(2014/11/30 12:33), Shriramana Sharma wrote:
> IIUC with BtrFS while it is possible to easily undelete a file or
> ordinary directory if a snapshot of the containing subvol exists, it
> seems that it's not elementary to undelete a subvol itself, because
> all subvols are under the root-level subvol (id 0 or 5, see my other
> q) but even snapshotting the root subvol will not snapshot any subvols
> under it.
>
> So is there any way to undo a subvol delete?
>
> [If no, then ordinary users should probably prefer regular directories
> to subvols.]
>

One solution is using snapper instead of using btrfs directly.
Snapper can automatically take a snapshot just before
taking/deleting snapshots. So, if you delete a snapshot
by mistake, it's still alive.

For more information, please refer to the following URLs.

https://en.opensuse.org/Portal:Snapper
http://events.linuxfoundation.org/sites/events/files/slides/LinuxCon_Europe_2014_Full_system_rollback_btrfs_snapper_0.pdf

Thanks,
Satoru


  parent reply	other threads:[~2014-12-02  7:14 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30  3:33 Possible to undo subvol delete? Shriramana Sharma
2014-11-30  4:23 ` Marc MERLIN
2014-12-01 13:12   ` Austin S Hemmelgarn
2014-12-01 13:19     ` Shriramana Sharma
2014-12-01 13:46       ` Roman Mamedov
2014-12-01 16:39         ` Shriramana Sharma
2014-12-02  3:14           ` Zygo Blaxell
2014-12-02  3:40             ` Shriramana Sharma
2014-12-02  5:39               ` MegaBrutal
2014-12-02 12:56               ` David Sterba
2014-12-02 15:15                 ` Shriramana Sharma
2014-12-03 18:53                   ` David Sterba
2014-12-04 14:06                     ` Shriramana Sharma
2014-12-04 14:18                       ` Austin S Hemmelgarn
2014-12-05 17:46                       ` David Sterba
2014-12-05 17:56                         ` Shriramana Sharma
2014-12-05 18:11                           ` Shriramana Sharma
2014-12-08 13:01                             ` Austin S Hemmelgarn
2014-12-08 14:16                               ` Shriramana Sharma
2014-12-08 14:53                                 ` Austin S Hemmelgarn
2014-12-02 12:52             ` David Sterba
2014-12-02 14:09               ` Hugo Mills
2014-12-03 18:26                 ` David Sterba
2014-12-03 19:54                   ` Zygo Blaxell
2014-12-05 17:55                     ` David Sterba
2014-12-02 15:25               ` Zygo Blaxell
2014-12-03 18:48                 ` David Sterba
2014-12-03 19:49                   ` Zygo Blaxell
2014-12-02  5:33           ` MegaBrutal
2014-12-02  5:50             ` Marc MERLIN
2014-12-01 13:38     ` MegaBrutal
2014-12-01 13:47       ` Roman Mamedov
2014-12-01 13:54         ` MegaBrutal
2014-12-01 16:40           ` Shriramana Sharma
2014-12-01 17:19             ` Robert White
2014-12-01 17:24           ` Austin S Hemmelgarn
2014-12-01 13:50       ` Austin S Hemmelgarn
2014-12-01 17:28         ` David Sterba
2014-12-01 13:50       ` Holger Hoffstätte
2014-12-01 17:35     ` David Sterba
2014-12-02  7:11 ` Satoru Takeuchi [this message]
2014-12-02 15:17   ` Shriramana Sharma
2014-12-03  0:11     ` Satoru Takeuchi
2014-12-03  2:35       ` Shriramana Sharma
2014-12-03 19:17         ` David Sterba
2014-12-03 19:12       ` David Sterba
2014-12-04  4:46         ` Satoru Takeuchi
2014-12-03 19:06   ` David Sterba

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=547D663A.3020201@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=samjnaa@gmail.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.