RE: Filenames causing problems in JFS

oops...correction. I was able to copy from Windows to a Ext3 folder. If I'm pulling from Linux box to a Ext3 folder, it stores them with different characters. So, still the problem exists. I have to schedule a copy and it has to be from Linux box (I can't do it from windows box b'cos of various other constraints). How can I enable this character support in the filenames???



Sanjay.

http://www.TechiesAbode.com/



-----Original Message-----
From: plug-discuss-admin@lists.plug.phoenix.az.us on behalf of Sanjay Darisi
Sent: Wed 10/13/2004 5:51 PM
To: plug-discuss@lists.plug.phoenix.az.us
Subject: RE: Filenames causing problems in JFS


I've just checked with ext3 filesystem, I was able to copy. I've checked only with a few files though. The only option that I have now is to change filesystem is it?? I have to delete all the data taht I've copied so far, almost 550GB. Isn't it possible to enable this unicode conversion in JFS?? I've googled for this and looked into IBM's website but couldn't get any useful info. Any ideas??





Sanjay.

http://www.TechiesAbode.com/



-----Original Message-----
From: plug-discuss-admin@lists.plug.phoenix.az.us on behalf of Austin Godber
Sent: Wed 10/13/2004 3:48 PM
To: plug-discuss@lists.plug.phoenix.az.us
Subject: Re: Filenames causing problems in JFS

Hmmm maybe this is what the Native Language support kernel modules are for?

Austin

Sanjay Darisi wrote:
>
>
> I'm using rsync to copy a directory from a windows server. This
> directory is very big and has thousands of files. Some of the files have
> some non-common ASCII characters in their filenames. I'm copying these
> files to a JFS filesystem based external storage. Whenever kernel
> encounters such characters in the filenames, it throws up messages like
> this in /var/log/messages.
>
> jfs_strtoUCS: char2uni returned -22.
> charset = iso8859-1, char = 0x84
>
> So, there are thousands of such messages in the log file. Apparently,
> these files are written by Mac computers to the windows server. Anyways,
> Windows was able to recognize the characters and store them properly. I
> believe its filesystem limitation, am I not correct? Is it just a
> parameter tweak in JFS or is it an inherent limitation in JFS and can't
> be changed. Does this limitation exist in ext3 too? 'cos if doesn't then
> I will change the filesystem to ext3.
>
> Or am I in the wrong impression that this unicode conversion is a
> limitation of filesystem? Any ideas ???
>
> My last option is to rename these files on windows server. Any ideas how
> to write such a script that parses all the filenames in a directory
> (recursively) and substitute few characters with some other common
> characters? I'm sure it will be painful for me to find out all such
> characters (and thier hex codes) from the log file.
>
>
> Sanjay
>
> http://www.techiesabode.com/
>
>

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss