Created attachment 1240812 [details]
Description of problem:
Shortly after startup, file system is forced readonly.
Version-Release number of selected component (if applicable):
100% with a 4.9 or 4.10 kernel and certain subvolumes used as rootfs. I haven't figured out why some subvolumes are affected and others aren't.
Steps to Reproduce:
1. Boot system
Forced readonly during startup or shortly after logging in (time to forced readonly varies a bit)
Should remain writable.
It's definitely a regression, using git bisect the problematic commit is 6c6ef9f26e598fb977f60935e109cd5b266c941a. Filed an upstream bug and reported on the Btrfs list, filing this bug to track on Fedora.
Should make it into stable.
This has been closed, but is there any indication when this will get fixed in Fedora? As far as I can see this does not seem to have hit any upstream 4.9 release yet.
I have a number of machines that are affected by it that cannot be upgraded to 4.9. Reading the discussion on the mailing list this seems to be caused by snapshot dirs having the wrong xattr handlers (/var/lib/machines being a candidate as this gets created by default by the Fedora installer).
All machines I have that are affected used to have a subvolume for /var/lib/machines, but don't any more, I removed it long ago as I don't need it. Is there still some magic marker on the mount point directory that indicates it used to be a subvolume mount point? If so, is there a way to clean this?