Bug 1018607
Summary: | Fails to mount btrfs that 3.10.14-100 mounts fine | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew Potter <agpotter> | ||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 20 | CC: | b1r63r, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa | ||||||
Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2014-03-17 18:45:26 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Andrew Potter
2013-10-13 19:00:27 UTC
This problem persists in 3.11.6-201. Created attachment 821331 [details]
journalctl with systemd.log_level=debug enforcing=0
fedup to Fedora 20 today. Kernel 3.11.9-300 is also unable to mount this btrfs volume. To reiterate, Fedora 18-era 3.10.14-100 continues to be able to mount the volume fine. Try doing a "btrfs device scan" and see if that enables you to mount the volume. Is this a dracut bug? Has it forgotten that for multi device btrfs volumes a btrfs device scan must be done before mounting? Created attachment 830400 [details]
dmesg from "btrfs device scan" attempt
"btrfs device scan" "btrfs device scan --all-devices" "btrfs device scan /dev/sdb /dev/sdc" do not help. mount still returns "No such file or directory" error. dmesg has this message when scanning: [ 168.122910] device label fedorahomebackup devid 1 transid 3124102 /dev/sdb [ 168.155961] device label fedorahomebackup devid 2 transid 3124102 /dev/sdc And mounting has this message: [ 109.724311] btrfs: disk space caching is enabled [ 109.794074] btrfs: bdev /dev/sdc errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 [ 109.794081] btrfs: bdev /dev/sdb errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 [ 114.927690] btrfs: open_ctree failed The full dmesg from this experiment is in comment 5 (which is still 3.11.9-300) *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested. |