Red Hat Bugzilla – Bug 1266720
btrfs-progs-4.2.0: btrfs check reports 'bad metadata [29474816, 29491200) crossing stripe boundary' on newly created filesystems
Last modified: 2016-12-20 09:46:41 EST
Created attachment 1077586 [details] btrfs creation and checking output Description of problem: Using the F23 Beta ISO I created a new btrfs filesystem, mounted it, then unmounted it and ran 'btrfs check' against it. 'btrfs check' reported: bad metadata [29474816, 29491200) crossing stripe boundary bad metadata [29540352, 29556736) crossing stripe boundary Errors found in extent allocation tree or chunk allocation This was using btrfs-progs 4.2.0 from the live environment, so this issue affects everyone using btrfs-progs 4.2.0, the F23 Beta ISO, and even the updated F22 ISOs. Version-Release number of selected component (if applicable): btrfs-progs 4.2 How reproducible: Always Steps to Reproduce: 1. Format a new partition with mkfs.btrfs 2. Mount the partition 3. Unmount the partition 4. Run 'btrfs check' on the partition Actual results: 'btrfs check' reports: bad metadata [29474816, 29491200) crossing stripe boundary bad metadata [29540352, 29556736) crossing stripe boundary Errors found in extent allocation tree or chunk allocation Expected results: 'btrfs check' returns no errors Additional info: This bug has actually been fixed in btrfs-progs v4.2.1. Patch that fixes it on the btrfs mailing list: http://www.spinics.net/lists/linux-btrfs/msg47029.html I'm reporting this bug because I'm not sure if this actually causes problems or not. From what I can tell, it looks like it's just a bug in the fsck code and doesn't harm any data but I can't guarantee that is actually true. If it does affect the on disk format, then this bug affects anyone who creates a partition using btrfs-progs 4.2.0 (especially F23 Beta ISO and updated F22 ISO users). I'll attach my terminal output that runs through everything, and for redundancy here it the fpaste: http://paste.fedoraproject.org/271863/30497614/
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.