Bug 431911
Summary: | Unable to mount ext4dev volume after update to kernel 2.6.24-23.fc9 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joachim Frieben <jfrieben> |
Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | esandeen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-07 21:07:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joachim Frieben
2008-02-07 19:46:07 UTC
When the volume is mounted without specifying the fs type, then one obtains: sh-3.2# mount /dev/mapper/VolGroup00-LogVol02 /home mount: unknown filesystem type 'ext4' This seems to imply that the fs is labeled or recognized as "ext4" whereas it used to be handled as "ext4dev". The issue it thus probably due to some inconsistent use of the fs identifier. There was a recent update to the ext4 code, so that may have changed something. blkid recently changed... as did the kernel... welcome to the bleeding edge :) In short, install e2fsprogs-1.40.5 from rawhide and run "tune2fs -E test_fs /dev/mapper/VolGroup00-LogVol02" and it should be happy. If not please reopen. 2 things here; the kernel code rejects the mount if test_fs isn't set, to try to be sure we don't accidentally claim ext3 filesystems, as well as to put a bit of an intentional barrier to premature use into place. :) If you look at "dmesg" after the failed mount (as the mount command suggests...) it will say: + printk(KERN_WARNING "EXT4-fs: %s: not marked " + "OK to use with test code.\n", sb->s_id); Perhaps that should give more instruction about the tune2fs command to use. Also, blkid now reports "ext4" instead of "ext4dev" if the test_fs feature isn't set, so it tries to mount as ext4 instead of ext4dev. That's what you saw with the bare "mount" command. Technically this is not a bug, but rather design, but it is unexpected. Sorry about that. I've updated http://fedoraproject.org/wiki/FedoraExt4 with this info. Ugh sorry tune2fs won't touch it. This works: [root@magnesium]# debugfs -w /dev/sda5 debugfs 1.40.5 (27-Jan-2008) debugfs: set_super_value s_flags 4 debugfs: quit I'll update the wiki again. |