Bug 515149 - man mount(8) doesn't describe all necessary options for mounting vfat filesystems in case of working in non-UTF8 locale
Summary: man mount(8) doesn't describe all necessary options for mounting vfat filesys...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: util-linux
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-02 18:52 UTC by Michael
Modified: 2011-01-13 23:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-13 23:45:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0085 0 normal SHIPPED_LIVE util-linux bug fix update 2011-01-12 17:29:18 UTC

Description Michael 2009-08-02 18:52:19 UTC
Description of problem:

While working in non-UTF8 locale I found that the kernel always mounts vfat filesystems with 'utf8' option enabled regardless of absence of it among command line mount options. And thereby the 'iocharset' option is virtually ignored so non-ascii file and directory names are dispalyed messed up.

After referring to the kernel sources I find that it is caused by the patch on bug https://bugzilla.redhat.com/show_bug.cgi?id=181963

Man page says about the 'utf8' option that UTF-8 encoding 'can be enabled for the filesystem whith this option'.
Perhaps after this patch it should be written that 'it is enabled by default' and be told that it can be disabled by setting 'utf8=0' or 'utf8=no' or 'utf8=false' as it follows from fs/fat/inode.c 

Today these options are undocumented and though there are practically no users that work in non-UTF8 locale, but nonetheless nor any information about this case too and not many of the users will go to look at the kernel sources.

Comment 1 Karel Zak 2010-04-09 13:22:20 UTC
Sorry for the delay and thanks for your bug report. Fixed upstream by commit e8abdb315028d2bb7d1ced187169c8026af656cb. 

(Man page update --- propose for the next RHEL update.)

Comment 6 errata-xmlrpc 2011-01-13 23:45:12 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0085.html


Note You need to log in before you can comment on or make changes to this bug.