From: Juergen Sauer <juergen.sauer@automatix.de>
To: linux-btrfs@vger.kernel.org
Subject: Bug Report Data Rescue: btrfs send ... btrfs set prop on linux 3.18-2 on Arch Linux
Date: Mon, 26 Jan 2015 13:16:33 +0100 [thread overview]
Message-ID: <54C63021.8000502@automatix.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Moin,
this weekend a ssd disk got an problem.
No Problem, I thought... but real word acts sometime other the you think :)
1. Szenario
I got an media Error on a ssd disk. So, I think trimming the whole
device may work.
Mounting the btrfs in rw is not possible anymore. Because the system is
going to write on damaged blocks.
Mounting ro is possible.
So I tried to
mount -o ro,subvol=/ /dev/sdl1 /mnt -> worked.
The Try to send the ro-mounted subvol "rootfs", which I want to recover
did not work:
btrfs send -f /srv/backup/rootfs.btrfs rootfs
ERROR: /mnt/rootfs is not read-only
The try to change the ro-flag
btrfs prop set rootfs ro true
ERROR: failed to set flags for rootfs. Read-only file system
was impossible.
I think this is an Bug in btrfs send, not to check if an btrfs
filesystem is mounted ro for refusing working.
It may be much more easier to recover damaged systems, if such annoying
thngs would not occour.
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
iEYEARECAAYFAlTGMCEACgkQW7UKI9EqarG8QwCgu80ihnBxKrnjy4rzzbrz6Riu
wS0AoIEiNicS/6Zz12ct7T4fZncW5xsP
=3PPi
-----END PGP SIGNATURE-----
next reply other threads:[~2015-01-26 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 12:16 Juergen Sauer [this message]
2015-01-26 13:38 ` Bug Report Data Rescue: btrfs send ... btrfs set prop on linux 3.18-2 on Arch Linux Duncan
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=54C63021.8000502@automatix.de \
--to=juergen.sauer@automatix.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).