From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Kleikamp Subject: Re: jfs, special characters Date: Sat, 26 Feb 2005 11:58:34 -0600 Message-ID: <1109440714.8463.19.camel@localhost> References: <20050226043439.GA16848@a5.repetae.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: fsdevel Received: from e32.co.us.ibm.com ([32.97.110.130]:48782 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S261245AbVBZR6g (ORCPT ); Sat, 26 Feb 2005 12:58:36 -0500 Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.195.12]) by e32.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j1QHwa5j542760 for ; Sat, 26 Feb 2005 12:58:36 -0500 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by westrelay03.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j1QHwaTk118768 for ; Sat, 26 Feb 2005 10:58:36 -0700 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j1QHwZP7019510 for ; Sat, 26 Feb 2005 10:58:35 -0700 To: frederik@ofb.net In-Reply-To: <20050226043439.GA16848@a5.repetae.net> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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