On Sat, Apr 05, 2014 at 11:03:46PM +0100, Hugo Mills wrote: > As far as I recall, -orecovery is read-write. -oro,recovery is > read-only.
Yes, we both corrected my Email at the same time :) Actually it's better/worse than that. From my notes at http://marc.merlins.org/perso/btrfs/2014-03.html#Btrfs-Tips_-Btrfs-Scrub-and-Btrfs-Filesystem-Repair mount -o recovery,ro (for when regular mount isn't working). Note, you have to use ro or it will give you a misleading error: root@polgara:~# mount -o recovery /dev/mapper/crypt /mnt/mnt8 mount: /dev/mapper/crypt already mounted or /mnt/mnt8 busy root@polgara:~# mount -o recovery,ro /dev/mapper/crypt /mnt/mnt8 root@polgara:~# In other words, for me -o recovery has never worked unless I added ,ro. I'm not saying -o recovery cannot work, but when I needed it, it didn't work because likely it failed to replay the log as you say, and adding ro fixed that problem. That said, returning mount: /dev/mapper/crypt already mounted or /mnt/mnt8 busy is not ideal :) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/
signature.asc
Description: Digital signature
