On Mon, Feb 18, 2019 at 2:01 AM Stefan K <shado...@gmx.net> wrote: > > Hello, > > I've played a little bit with raid1: > my steps was: > 1. create a raid1 with btrfs (add device; balance start -mconvert=raid1 > -dconvert=raid1 /) > 2. after finishing, i shutdown the server and remove a device and start it > again, > 3. it works (i used degraded options in fstab) > 4. I shutdown the server, add the 'old' device, start it and run a btrfs > balance
What exact command? There's a very good chance there are newly created single profile block groups that must be converted, so it requires another -mconvert and maybe also a -dconvert, depending on what block groups have been created during the degraded mount. > 5. until here everything is fine > 6. I shutdown the server, remove the other harddisk, and start it, > 7. it works > 8. I shutdown the server, add the 'old' device, start it and try a btrfs > balance > 9. but now the FS is mounted as read only > > I got the following messages in dmesg: > [ 6.401740] BTRFS: device fsid b997e926-ab95-46d0-a9be-da52aa09203d devid > 1 transid 3570 /dev/sda1 > [ 6.403079] BTRFS info (device sda1): allowing degraded mounts > [ 6.403084] BTRFS info (device sda1): disk space caching is enabled > [ 6.403086] BTRFS info (device sda1): has skinny extents > [ 6.405878] BTRFS warning (device sda1): devid 2 uuid > 09a7c9f6-9a13-4852-bca6-2d9120f388d4 missing > [ 6.409108] BTRFS info (device sda1): detected SSD devices, enabling SSD > mode > > [ 6.652411] BTRFS info (device sda1): allowing degraded mounts > [ 6.652414] BTRFS info (device sda1): disk space caching is enabled > [ 6.652416] BTRFS warning (device sda1): too many missing devices, > writeable remount is not allowed Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux Kernel is too old, it doesn't have the patches that permit mounting rw degraded more than one time before fully converting everything. You'll need a newer kernel to permit the mount of this file system, and then you'll need to make sure there are only raid1 block groups. I know this is not obvious. Not related to your problem but btrfs-progs 4.7 is really old too. It's a common issue on the very stable distros like Debian and RHEL, but strictly speaking if you have problems with such tools and kernels, you need to get support from the distro. One upstream mailing lists, no matter what file system, it's very development oriented with focus on fixing bugs in the mainline and development kernels. Anyway it should be safe to get a recent LiveOS. Unfortunately I'm not certain what kernel this behavior changed in, I know for sure kernel 5.0.0 rc's have it, and I'm almost positive 4.20 has it. I'm not sure if 4.18 has it. -- Chris Murphy
