Re: jfs, special characters

[Dave Kleikamp <shaggy@austin.ibm.com>]

On Fri, 2005-02-25 at 20:34 -0800, Frederik Eaton wrote:
> Does JFS have problems with files with special characters in them?

Sometimes.  jfs attempts to store pathnames in 16-bit unicode, and uses
the mount option iocharset to determine what to convert to/from.

In the 2.4 kernel, the default value of iocharset is determined by the
kernel config option, CONFIG_NLS_DEFAULT.  If an existing pathname
exists that doesn't map to the iocharset, jfs has the problem you
describe.  Mounting with -o iocharset=utf8 should let you access any
existing files.

In the 2.6 kernel, the default was changed to store each byte of the
filename as a 16-bit value in the directory without using any
conversion.  There can still be a problem if an existing pathname has a
value with a non-zero high-order byte.  Again mounting with -o
iocharset=utf8 will let you access all files.

> $ ls
> ls: 04-The_Dark_Of_The_Matin?e.ogg: No such file or directory
> [1]$ rm 04-The_Dark_Of_The_Matin\?e.ogg
> rm: cannot lstat `04-The_Dark_Of_The_Matin?e.ogg': No such file or directory
> 
> Frederik

-- 
David Kleikamp
IBM Linux Technology Center