Bug 183564
Summary: | mount problem with vfat with ANY iocharset.... | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michail V. <m.lalakisv> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | despairr, gajownik, kzak, redhat.com, shin1, triage, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | OldNeedsRetesting bzcl34nup | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-06 15:34:35 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
Michail V.
2006-03-02 00:33:09 UTC
I just installed kernel 2.6.15-1.2032_FC5smp and the problem remains.... Dont we have any news about it? michail A confirm this problem. When mounting vfat filesystem with ANY iocharset, all non-ascii symbols appears in UTF8, but not in character set specified in iocharset option. A confirm this problem. # uname -a Linux brenev.office 2.6.16-1.2078_FC5smp Problem still exist. Same on cifs shares, when non UTF8 locale used. This is still an issue, even with kernel-smp-2.6.16-1.2122_FC5 and util-linux-2.13-0.20.1. This occurs even with ISO-8859-1. Under Fedora Core 4, I used to use the command: mount /dev/sdb1 /media/H300 -o rw,shortname=winnt,iocharset=iso8859-1 on a vfat partition without problems. However this no longer works with Core 5. As described above, all non-ascii shows as two characters UTF8. To reproduce: 1. Use WindowsXP to put file with accented character in name onto a USB drive 2. mount as per above 3. ls mount-point Actual results: ls shows filename with accented character replaced with two other characters (the UTF8 representation of the character) Expected results: ls shows correct filename P.S. It's been three months now, and no response from anyone on the "Kernel Maintainer List". Suggest owner or reporter increases severity level. Apparently it was decided that all VFAT partitions SHALL be UTF8, unless explicitly told otherwise, via an undocumented option. For a work-around, mount your VFAT partitions with an additional, undocumented option: utf8=0 See bug 181963 Note that other distros, like Ubuntu, do not have this hard-coded kernel bug. (In reply to comment #5) > For a work-around, mount > your VFAT partitions with an additional, undocumented option: utf8=0 My post is a bit off-topic but this option is documented in /usr/share/doc/kernel-doc-2.6.17/Documentation/filesystems/vfat.txt (kernel-doc package) *** Bug 189459 has been marked as a duplicate of this bug. *** A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. The problem still exists. Please, change status of the bug from NEEDINFO. What locale are you using ? (ie LC_ALL = ?) ru_RU.koi8r Fedora Core 5 is no longer maintained. Is this bug still present in Fedora 7 or Fedora 8? Removing NeedsRetesting from whiteboard so we can repurpose it. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |