From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Make existing snapshots read-only?
Date: Tue, 29 May 2012 12:56:13 +0100 [thread overview]
Message-ID: <20120529115613.GB7397@chaz.gmail.com> (raw)
In-Reply-To: <20120528183700.GA9588@untroubled.org>
2012-05-28 12:37:00 -0600, Bruce Guenter:
>
> Is there any way to mark existing snapshots as read-only? Making new
> ones read-only is easy enough, but what about existing ones?
[...]
you can always do
btrfs sub snap -r vol vol-ro
btrfs sub del vol
mv vol-ro vol
--
Stephane
prev parent reply other threads:[~2012-05-29 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 18:37 Make existing snapshots read-only? Bruce Guenter
2012-05-29 0:40 ` Li Zefan
2012-05-29 11:18 ` David Sterba
2012-05-29 11:33 ` cwillu
2012-05-29 11:56 ` Stephane Chazelas [this message]
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=20120529115613.GB7397@chaz.gmail.com \
--to=stephane.chazelas@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).