Description of problem:
Some /etc/fstab Btrfs lines contain subvolid=5. The subvolid and subvol mount options are mutually exclusive, so only one of them should be used. If subvolid is used, 5 is incorrect in all cases. This is a regression, it didn't happen with Fedora 21.
Version-Release number of selected component (if applicable):
Always for root and home, I don't know why the boot line doesn't have this option.
Steps to Reproduce:
1. Do a Btrfs install.
e.g. from fstab F22
UUID=<uuid> /home btrfs subvolid=5,subvol=home 0 0
e.g. from fstab F21
UUID=<uuid> /home btrfs subvol=home 0 0
a. Same as Fedora 21; OR
b. If using subvolid, then subvol needs to be omitted, and the number needs to be correct, the number 5 here is wrong (the subvolid for the home subvol on this volume is 297, subvolid 5 is the top level subvolume)
Created attachment 997751 [details]
Created attachment 997752 [details]
Created attachment 997753 [details]
Created attachment 997754 [details]
Created attachment 997755 [details]
Created attachment 997756 [details]
btrfs subvolume list
Proposed as a Freeze Exception for 22-beta by Fedora user chrismurphy using the blocker tracking app because:
This seems benign in that the 2nd (correct) subvolume does mount. But this is really an untested configuration so it could be pernicious. It's a regression, and also there's no mechanism to fix it after an installation - quite a few people do install beta and stick with that installation through final. But since I can't find an explicit criteria to make it a blocker, nominating it for FE.
Discussed at 2015-04-06 freeze exception review meeting: https://meetbot.fedoraproject.org/fedora-blocker-review/2015-04-06/f22-blocker-review.2015-04-06-16.00.log.txt . As this doesn't seem to cause any identifiable practical problems, we couldn't see a justification for breaking the freeze, and it is rejected as an FE issue.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
was this ever fixed, cmurf?