If "you have a specific [need] to do something else", for example,
you use iso8859 Extended ASCII or EUC to name files locally on the
system and you share those files over SMB, you may still need to
workaround the current situation.

Currently, we skip names containing non-UTF-8 characters in directory
listings.  Our current plan is to use name managling - the same
mechanism that we used to produce DOS compatible short names.  This
is on the to-do list but I don't have a date when it will be available.

Alan

On 11/30/09 17:16, Alan M Wright wrote:
We've seen a few problem reports recently with directory listings and
file names containing non-UTF-8 characters.  These problems are related
to character encoding not the characters you want to have in the file
name.  These encoding problems can be avoided without having to rename
files.

Unless you have a specific to do something else, create ZFS datasets
using:

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

This will restrict all object names in ZFS to UTF-8 encoding.  Since
this is a create-time option, you will never run into the situation in
which some names contain non-UTF-8 encoded characters, and you should
not run into the directory listing problems mentioned above on Windows
clients.

Notes:
1. UTF-8 is a superset of ASCII and setting utf8only will have no impact
   if you use ASCII characters.
2. utf8only does not restrict the characters you can use in file names,
   it only controls how they are stored in ZFS.

If you have NFS clients using non-UTF-8 characters, use charset=hostlist
(see sharemgr(1M)) to instruct the OpenSolaris NFS server to convert
between charset and UTF-8 for the NFS clients in hostlist.

  charset would be one of:
    euc-cn, euc-jp, euc-jpms,  euc-kr,  euc-tw, iso8859-1,
    iso8859-2, iso8859-5, iso8859-6, iso8859-7, iso8859-8,
    iso8859-9, iso8859-13, iso8859-15, koi8-r

  hostlist is a list of hostnames and/or IP addresses.

If you have non-UTF-8 file names in another local file system, have a
look at convmv(1).

Alan

_______________________________________________
cifs-discuss mailing list
cifs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss

Reply via email to