From: Marc MERLIN <marc@merlins.org>
To: MegaBrutal <megabrutal@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Shriramana Sharma <samjnaa@gmail.com>
Subject: Re: Possible to undo subvol delete?
Date: Mon, 1 Dec 2014 21:50:02 -0800 [thread overview]
Message-ID: <20141202055002.GD8916@merlins.org> (raw)
In-Reply-To: <CAE8gLhkiv0YnFArrzwLfnrGcqm1pRsuYBgakwrMs2W61xuothw@mail.gmail.com>
On Tue, Dec 02, 2014 at 06:33:38AM +0100, MegaBrutal wrote:
> 2014-12-01 17:39 GMT+01:00 Shriramana Sharma <samjnaa@gmail.com>:
> >
> > When btrfs has so many features (esp snapshots) to prevent user
> > accidentally deleting data (I liked especially
> > http://www.youtube.com/v/9H7e6BcI5Fo?start=209) I think there has to
> > be *some* modicum of support for warning against deleting a subvolume
> > (and it seems others agree too).
> >
>
> WOW, this is pretty neat? How can I do the same actions from the
> command-line? E.g. I would be curious whether a file changed since the
> last snapshot. Today I have to use traditional methods like plain "ls
It's not trivial. See
http://marc.merlins.org/perso/btrfs/2014-05.html#Btrfs-diff-Between-Snapshots
>From what I understand, the only way to do this better is to use
btrfs-send and parse the output, but that's not trivial either since
btrfs-send has lots of intermediate renames.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-12-02 5:50 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 [this message]
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
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=20141202055002.GD8916@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=megabrutal@gmail.com \
--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.