> ... for my particular case the way filenames appear on ZFS and > NFSv4 is not important.
That's okay. The scenario I described wasn't related to displaying the names locally on Solaris or on NFS clients. > The data has been duplicated to a ZFS filesystem on an X4500 using > rsync from an NFS share. This sounds like the scenario I described. If the names arrived on the X4500 via NFS (rsync) and they contained iso8859-1 characters, those will have been stored verbatim in ZFS, and that's not consistent with sharing file names across multiple protocols. Our common frame of reference is UTF8. The only way to deal with this is to convert the names in the file system from iso8859-1 to UTF8. The CIFS Service will interact with Windows clients using the appropriate charsets but it requires that names within the file system be UTF8. Alan -- On 07/24/09 18:37, Jay Anderson wrote:
Thank you for the information about character sets and NFSv4 and ZFS. That is useful information, and I will save it. However, for my particular case the way filenames appear on ZFS and NFSv4 is not important. It's the Windows clients that need to see the filenames correctly. The files were created originally by Windows clients, saved to a UFS filesystem shared using CIFS on a NetApp. The data has been duplicated to a ZFS filesystem on an X4500 using rsync from an NFS share. Is there a way to specify a character set for CIFS Server so the filenames will be served to Windows clients, and displayed correctly? Thanks Jay
_______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
