Bug 189459

Summary:	VFAT charset options have no effect
Product:	[Fedora] Fedora	Reporter:	TOYAMA Shin-ichi <shin1>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	medium
Version:	5	CC:	wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-07-13 12:37:29 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 TOYAMA Shin-ichi 2006-04-20 06:25:58 UTC

Description of problem:
Charset options for VFAT have no effect and filename always appears in UTF-8.

Version-Release number of selected component (if applicable):
2.6.16-1.2080

How reproducible:
Always

Steps to Reproduce:
1. # mount -t vfat -o codepage=932,iocharset=euc-jp /dev/xxx /mount/point
2. # ls /mount/point
  
Actual results:
Filenames in /mount/point appears in UTF-8

Expected results:
Filenames in /mount/point appears in euc-jp

Additional info:
There is no problem with vanilla kernel(2.6.16.9) from kernel.org

Comment 1 Kurt Swanson 2006-07-07 01:03:33 UTC

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.

Comment 2 TOYAMA Shin-ichi 2006-07-08 03:56:36 UTC

Adding option utf8=0 worked well, thank you!
But I feel it incorrect that kerel ignores iocharset option without this
work-around.

Comment 3 Dawid Gajownik 2006-07-13 12:37:29 UTC


*** This bug has been marked as a duplicate of 183564 ***