Description of problem: I had a hardware problem - the disk got disconnected and reconnected on the bus. Afterwards, kernel reported some oops and remounted the filesystem read-only. Everything worked, I could read any file without problem. Unfortunately, after the reboot, I'm no longer able to mount the filesystem. Trying to run btrfsck on it with various options, it is unable to repair the filesystem, although it pretends it did - repair ends without error, yet on subsequent run I get nonzero exit code (and bunch of errors on the console). Version-Release number of selected component (if applicable): btrfs-progs-3.12-1.fc19.x86_64 How reproducible: always Steps to Reproduce: 1. btrfsck --repair /the/path 2. btrfsck /the/path Actual results: 1. although some problems are reported during the run, it ends with success 2. it reports errors and the filesystem is not mountable Expected results: everything gets fixed, no further errors Additional info: I got an image of the filesystem in question, but it is about 4 GB compressed / from 600 GB (almost empty) disk uncompressed ... Unfortunately, as I haven't expected such issues, I did the copy only after messing with btrfsck --init-extent-tree and --init-csum-tree. Is there any place I can upload it to for examination?
btrfs-progs-3.14.1 has been pushed to Fedora 19 and 20 for testing. I frankly have no idea if this will resolve your bug or not, but if you test it and find that it does, please take the opportunity to close this bug. :) Thanks, -Eric
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
well, things are getting better :-) with btrfs-progs-3.18.1-1.fc21 and kernel 3.17.8-300, I got to a state where I can mount the filesystem but even after --init-csum-tree, on subsequent check it still reports many broken checksums ... however it mounts without any complaints (before the last --init* attempt mounting hadn't worked with "open_ctree failed" error) and browsing the contents hasn't led to any problems so far alternatively, instead of providing the image, I can set up ssh access to the virtual machine that has it mounted - if interested, please ping me in person, not via bugzilla comment
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.