On fimmtudagur, 3. september 2020 13:06:49 GMT Thorsten Kukuk wrote:
"btrfs property get / ro" indicates that it is not read-only but
Ok, so the btrfs subvolume is not read-only, which means you system has to break. Did you install the transactional-server with YaST, or did you add the packages later? Or did you play with btrfs property on the subvolume?
I chose the transactional server option during the installation. However this was originally a leap 15.0 server. But in february I updated it from 15.0 -> 15.1 -> Tumbleweed and there have been no problems until now. I've not been playing around with the btrfs properties.
"findmnt /" indicates that it is read-only. Should I run "btrfs property set / ro true"?
You can try it. But since you did run with a read-write btrfs subvolume, I'm not sure the system will recover from it.
Well I tried and got: ERROR: Could not set subvolume flags: Read-only file system Regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org