All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Possible to undo subvol delete?
Date: Mon, 1 Dec 2014 13:50:57 +0000 (UTC)	[thread overview]
Message-ID: <pan.2014.12.01.13.50.56@googlemail.com> (raw)
In-Reply-To: CAE8gLhmn3aX88t1FO2=BnHXk0-+2xQ4dnW57dga93iA-bFaUzQ@mail.gmail.com

On Mon, 01 Dec 2014 14:38:16 +0100, MegaBrutal wrote:

> I've also noticed, a subvolume can just be deleted with an "rm -r",
> just like an ordinary directory. I'd consider to only allow subvolume

Nope:

root>btrfs subvolume create foo
Create subvolume './foo'
root>touch foo/bla
root>ll foo 
total 0
-rw-r--r-- 1 root root 0 Dec  1 14:47 bla
root>rm -rf foo 
rm: cannot remove ‘foo’: Operation not permitted
root>

The files of the subvolume do get deleted though, but that's correct.

Not sure what you did, but what you want is already the case.

-h


  parent reply	other threads:[~2014-12-01 13:51 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 [this message]
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=pan.2014.12.01.13.50.56@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --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 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.