From: Juergen Sauer <juergen.sauer@automatix.de>
To: "Lentes, Bernd" <bernd.lentes@helmholtz-muenchen.de>,
"'linux-btrfs@vger.kernel.org'" <linux-btrfs@vger.kernel.org>
Subject: Re: rollback of a snapshot is just read-only
Date: Mon, 27 Apr 2015 12:38:16 +0200 [thread overview]
Message-ID: <553E1198.9000705@automatix.de> (raw)
In-Reply-To: <15785B7E063D464C86DD482FCAE4EBA501CAC3EF69DA@XCH11.scidom.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 24.04.2015 um 16:08 schrieb Lentes, Bernd:
> Hi,
>
> it should be just a small problem, but it is one. How can I rollback t
o a snapshot of my root filesystem ?
> Googeling, I found a lot of solutions, each different.
> I finally choosed this one: https://btrfs.wiki.kernel.org/index.php/Us
eCases#I_want_to_be_able_to_do_rollbacks_with_Btrfs
>
> I made the snapshot, changed some configuration, and afterwards I'd li
ke to rollback to the snapshot:
>
> - btrfs subvolume snapshot -r / /.snapshots/vor_nvidia
>
> - change some configuration
>
> - btrfs subvolume set-default 625 (id of the snapshot)
>
> - reboot
...
It seems, that you has set the RO "readonly" flag on the subvolume.
The btrfs tool may se/unset the flag like
# mount /dev/sdXY /mnt -o subvol=/
# btrfs su list .
ID 258 gen 13711 top level 5 path backup
[ ... ]
# btrfs prop list backup
ro Set/get read-only flag of subvolume.
compression Set/get compression for a file or directory
root@pc6:/mnt# btrfs prop get backup
ro=true
root@pc6:/mnt# btrfs prop set backup ro false
root@pc6:/mnt# btrfs prop get backup
ro=false
This worked on:
root@pc6:/mnt# uname -a ; btrfs --version
Linux pc6 3.19.3-3-ARCH #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015
x86_64 GNU/Linux
btrfs-progs v3.19
mit freundlichen Grüßen
Jürgen Sauer
- --
Jürgen Sauer - automatiX GmbH,
+49-4209-4699, juergen.sauer@automatix.de
Geschäftsführer: Jürgen Sauer,
Gerichtstand: Amtsgericht Walsrode • HRB 120986
Ust-Id: DE191468481 • St.Nr.: 36/211/08000
GPG Public Key zur Signaturprüfung:
http://www.automatix.de/juergen_sauer_publickey.gpg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlU+EZgACgkQW7UKI9EqarFm9ACgzHjBGXV8Jlscn2ADV1fmdSo6
qgcAn0wWESh7XADCX2Lp8DWrz3FPSnMS
=5tHu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-04-27 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 14:08 rollback of a snapshot is just read-only Lentes, Bernd
2015-04-24 14:42 ` Hugo Mills
2015-04-27 10:38 ` Juergen Sauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-24 14:26 Lentes, Bernd
2015-04-27 11:47 ` Austin S Hemmelgarn
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=553E1198.9000705@automatix.de \
--to=juergen.sauer@automatix.de \
--cc=bernd.lentes@helmholtz-muenchen.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=service@automatix.de \
/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).