Bug 137174
| Summary: | Lack of fsck.hfsplus + hfsplus driver pickiness = read only mount | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | W. Michael Petullo <redhat> |
| Component: | hfsutils | Assignee: | David Woodhouse <dwmw2> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | barryn, carenas, karsten, kr, pcfe, wtogami |
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened |
| Target Release: | --- | ||
| Hardware: | powerpc | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 3.2.6-6 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-28 10:51:34 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 121179 | ||
hfsutils-3.2.6-6 includes hfsck. Has anyone tried hfsck? It seems to like to eat filesystems more than fix them. On my system, running hfsck rendered an HFS+ filesystem unmountable. Also, there is no fsck.hfsplus link, so "fsck /dev/hdaX" says: fsck 1.35 (28-Feb-2004) fsck: fsck.hfsplus: not found fsck: Error 2 while executing fsck.hfsplus for /dev/hda7 hfsck isn't for hfs+ That explains a lot. Well, since hfs+ is what I am looking for, I changed the bug summary. I think most people use hfs+ these days, right? We should put hfsplusutils into Fedora Extras. http://david.woodhou.se/hfsplusutils-1.0.4-2.src.rpm the current hfsplusutils code needs lots of cleaning first to compile cleanly with gcc3.4 (default on fc3) and later. the spec is also not good for Fedora Extra, eventhough only needed minor tweaks. In addition, I tried every combination of hpfsck after building it with the above package. Didn't seem to make any difference at all. However mounting the fs with "./hpmount /dev/sda3" and then unmounting with "./hpumount" fixes the problem. Just fyi. fsck.hfsplus from the hfsplusutils-1.0.4-6 package seems to corrupt HFS+ filesystems. REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred. we have fsck.hfsplus in the latest Fedora for PPC, closing |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.8 Description of problem: Within its hfs code, the kernel contains the following code fragment: if ((attrib & cpu_tobe16(HFS_SB_ATTRIB_UNMNT)) || (attrib & cpu_to_be16(HFS_SB_ATTRIB_INCNSTNT))) { hfs_warn("HFS-fs warning: Filesystem was not cleanly unmounted, "running fsck.hfs is recommended. mounting read-only.\n"); sb->s_flags |= MS_RDONLY; } Because fsck.hfs is not provided, this causes a filesystem that was not properly unmounted to mount read only forever. The only fix seems to be to boot into something like Mac OS X to repair the filesystem. Either fsck.hfs should be implemented or this paranoia should be removed from the kernel filesystem code. Of course, option two may not be safe. Note that hfsutils' TODO does make mention of hfsck. Version-Release number of selected component (if applicable): kernel-2.6.9-1.643 How reproducible: Always Steps to Reproduce: 1. Improperly remove an HFS drive from the system (do not properly unmount it). 2. Try to mount the drive. Actual Results: The kernel mounts it read only. Additional info: