From: Frederik Eaton Subject: Re: jfs, special characters Date: Sun, 27 Feb 2005 15:00:12 -0800 Message-ID: <20050227230012.GA23340@a5.repetae.net> References: <20050226043439.GA16848@a5.repetae.net> <1109440714.8463.19.camel@localhost> Reply-To: frederik@ofb.net Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: fsdevel Received: from h34-aclarke.sv.meer.net ([205.217.153.34]:59537 "EHLO ofb3.ofb.net") by vger.kernel.org with ESMTP id S261507AbVB0XAi (ORCPT ); Sun, 27 Feb 2005 18:00:38 -0500 To: Dave Kleikamp Content-Disposition: inline In-Reply-To: <1109440714.8463.19.camel@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Feb 26, 2005 at 11:58:34AM -0600, Dave Kleikamp wrote: > On Fri, 2005-02-25 at 20:34 -0800, Frederik Eaton wrote: > > Does JFS have problems with files with special characters in them? >=20 > Sometimes. jfs attempts to store pathnames in 16-bit unicode, and us= es > the mount option iocharset to determine what to convert to/from. >=20 > In the 2.4 kernel, the default value of iocharset is determined by th= e > 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=3Dutf8 should let you access an= y > existing files. >=20 > 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=3Dutf8 will let you access all files. >=20 > > $ 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 Thanks, you were right that I recently upgraded to 2.6 (actually I transferred the hard drive between machines), and with a "mount /home -= o remount,iocharset=3Dutf8" at least I can access the files now. But the names aren't what they should be, for instance I see: 04-The_Dark_Of_The_Matin=CE=98e.ogg (that's a theta). Were they supposed to be correct?=20 As an aside, now, I just tried "mount /home -o remount,iocharset=3Diso8859-1", and got same problem ls: '/home/shared/frederik/Franz_Ferdinand/Franz_Ferdinand/04-The_Dark_= Of_The_Matin?e.ogg': No such file or directory But when I repeated the "mount /home -o remount,iocharset=3Dutf8" command, the listing didn't show the name with a theta character, but instead with two question marks: 04-The_Dark_Of_The_Matin??e.ogg Strange behavior. I.e., upon changing the mount options and then changing them back I get a different listing. =46rederik - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html