From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: MegaBrutal <megabrutal@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: Marc MERLIN <marc@merlins.org>, Shriramana Sharma <samjnaa@gmail.com>
Subject: Re: Possible to undo subvol delete?
Date: Mon, 01 Dec 2014 08:50:09 -0500 [thread overview]
Message-ID: <547C7211.3070809@gmail.com> (raw)
In-Reply-To: <CAE8gLhmn3aX88t1FO2=BnHXk0-+2xQ4dnW57dga93iA-bFaUzQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On 2014-12-01 08:38, MegaBrutal wrote:
> 2014-12-01 14:12 GMT+01:00 Austin S Hemmelgarn <ahferroin7@gmail.com>:
>>
>> We might want to consider adding an option to btrfs subvol del to ask for
>> confirmation (or make it do so by default and add an option to disable
>> asking for confirmation).
>>
>
> 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
> deletions with exact "btrfs subvolume delete" commands, and they
> should be protected against an ordinary "rm". There also could be a
> tunable FS feature to allow or disable ordinary subvolume deletions,
> which could be set or unset by btrfstune. I think a subvolume really
> deserves to be treated specially over an ordinary directory.
I don't know what distro/kernel version you might be using, but every
version of btrfs I have used required the use of 'btrfs subvol del' to
actually delete a subvolume, even an empty one. It would not surprise
me though if RHEL or SuSE had patched the kernel to allow using rm on a
subvolume.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
next prev parent reply other threads:[~2014-12-01 13: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
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 [this message]
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=547C7211.3070809@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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.