Were these file (with the degree symbol in their names) originally
created on OpenSolaris via NFS?

If so, you may need to set the charset property on your NFS shares.
Doug has a post about this on his blog: http://blogs.sun.com/dougm/

The syntax is:
        charset=<access-list>

which in your case would be:
        iso8859-1=<hostnames or IP addresses of clients using iso8859-1>

Note that NFSv4 clients "should" convert iso8859-1 to UTF-8 before
transmitting file names over-the-wire.

When creating ZFS datasets, you may also want to consider setting
utf8only=on to ensure that you don't end up with a mixture of character
encodings on disk.  This may also help you track down NFS clients that
are attempting to save non-UTF8 charsets because ZFS will return EILSEQ,
which may appear on the client as access denied (because NFS doesn't
know about EILSEQ).

        zfs create -o casesensitivity=mixed -o utf8only=on tank/dataset

Note that you can only set casesensitivity and/or utf8only at dataset
creation time because, once you've started creating objects, there's
no mechanism to ensure that the on-disk names are UTF8 and/or will be
handled correctly during case conflicts.

Alan
--

On 07/24/09 15:46, Jay Anderson wrote:
The data currently resides on a NetApp so I don't know how to determine the 
locale/character set in use.

When a filename with the degree symbol is listed from a Unix box the share 
NFS-mounted the symbol appears as a ? character. If the listing is captured to 
a file, the character appears as \260 (octal for 176). From all our Windows 
servers and workstations the degree symbol is displayed. All of our Windows 
installations (XP SP3, Server 2003 SP2) are standard english, no addtional 
languages, and the CHCP command reports 437.

One additional note is that to make the filenames show up correctly in Windows using 
Samba on a non-global zone on the same OpenSolaris server I had to add the parameter 
"unix charset = iso8859-1" to the smb.conf file.

Thanks for taking a look at this.

Jay

_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss

Reply via email to