From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: MegaBrutal <megabrutal@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: Roman Mamedov <rm@romanrm.net>, Marc MERLIN <marc@merlins.org>,
Shriramana Sharma <samjnaa@gmail.com>
Subject: Re: Possible to undo subvol delete?
Date: Mon, 01 Dec 2014 12:24:34 -0500 [thread overview]
Message-ID: <547CA452.6030009@gmail.com> (raw)
In-Reply-To: <CAE8gLhnyTWjfTk-W+BHdfovV8pJH-yqo7joR+kf6vgs1FU00hw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
On 2014-12-01 08:54, MegaBrutal wrote:
> 2014-12-01 14:47 GMT+01:00 Roman Mamedov <rm@romanrm.net>:
>> On Mon, 1 Dec 2014 14:38:16 +0100
>> MegaBrutal <megabrutal@gmail.com> 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
>>> deletions with exact "btrfs subvolume delete" commands, and they
>>
>> This is already the case. 'rm -r' will remove all files in a subvolume, but
>> the empty subvolume itself is only deletable via the 'btrfs' command.
>
> That's great! And there is no way to protect against recursive
> deletions (besides setting the subvolume read-only, as you suggested
> below), as files are processes individually by "rm". But it's OK,
> people should always be very careful with "rm", and it doesn't change
> with btrfs. ;)
>
>
>> If you want to make snapshots which can't be removed by ordinary tools, use
>> the 'read-only' mode when creating them.
>
> Yeah, good idea! Anyway, is it possible to change a read-only snapshot
> to read-write and vica-versa, or you can only specify read-only while
> creating them?
>
IIRC, there is something that you can do with the properties interface.
Personally though, I just make the snapshot RW to start with, and then
recursively make it immutable (chattr -r +I), as I never use immutable
files for anything else, and it works on any _sane_ filesystem, not just
btrfs.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
next prev parent reply other threads:[~2014-12-01 17:24 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 [this message]
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=547CA452.6030009@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.org \
--cc=megabrutal@gmail.com \
--cc=rm@romanrm.net \
--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.