All of lore.kernel.org
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Shriramana Sharma <samjnaa@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Possible to undo subvol delete?
Date: Wed, 3 Dec 2014 09:11:48 +0900	[thread overview]
Message-ID: <547E5544.7090907@jp.fujitsu.com> (raw)
In-Reply-To: <CAH-HCWV8upw8prPvCiJcpL2NRmuiWaAM+5ZEayD3OoEZrcsyaw@mail.gmail.com>

(2014/12/03 0:17), Shriramana Sharma wrote:
> On Tue, Dec 2, 2014 at 12:41 PM, Satoru Takeuchi
> <takeuchi_satoru@jp.fujitsu.com> wrote:
>>
>> Snapper can automatically take a snapshot just before
>> taking/deleting snapshots. So, if you delete a snapshot
>> by mistake, it's still alive.
>
> Sorta contradicts the whole point of deleting a snapshot, no? Or is it
> some sort of trash vs (real) delete mechanism?
>

It's not a Btrfs itself's feature. It's a snapper's feature.
It works as a helper of snapshot management.

1. You takes /snap by "snapper create" command.
2. You delete /snap by "snapper delete" command by mistake.
    Then snapper takes a "pre" snapshot just before deleting
    /snap.
3. Now /snap is deleted, however, a "pre" snapshot which is
    the same as /snap before deleting, is still alive.

I don't know how Btrfs itself undo the deletion of a snapshot.
It works if you manages snapshots not by btrfs directly,
but by snapper.

If I misunderstanding something, sorry for noise.

Thanks,
Satoru


  reply	other threads:[~2014-12-03  0:13 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
2014-12-02 15:17   ` Shriramana Sharma
2014-12-03  0:11     ` Satoru Takeuchi [this message]
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=547E5544.7090907@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.