Hi! I have a problem with the charset in the following scenario: - OSOL Server with zfs pool und NFS/CIFS shares enabled - OSX Client with CIFS mounts - OSX Client with NFSv3 mounts If one of the clients saves a file with a special character in the filename like ''????'', the other client can not access that file. The characters a displayed correctly on both clients as well as on the server. What is the reason of this incompatibility of CIFS and NFS invoked filenames and how can I get around it? Achim -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 299 bytes Desc: OpenPGP digital signature URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20110115/4299e4f7/attachment.bin>
On 15 Jan 2011, at 13:44, Achim Wolpers wrote:> Hi! > > I have a problem with the charset in the following scenario: > > - OSOL Server with zfs pool und NFS/CIFS shares enabled > - OSX Client with CIFS mounts > - OSX Client with NFSv3 mounts > > If one of the clients saves a file with a special character in the > filename like ''????'', the other client can not access that file. The > characters a displayed correctly on both clients as well as on the > server. What is the reason of this incompatibility of CIFS and NFS > invoked filenames and how can I get around it?What are the normalization properties of these filesystems? The zfs man page says they''re used when comparing filenames: --- normalization = none | formC | formD | formKC | formKD Indicates whether the file system should perform a uni- code normalization of file names whenever two file names are compared, and which normalization algorithm should be used. File names are always stored unmodified, names are normalized as part of any comparison process. If this property is set to a legal value other than none, and the utf8only property was left unspecified, the utf8only property is automatically set to on. The default value of the normalization property is none. This property cannot be changed after the file system is created. --- Cheers, Chris
Am 15.01.11 14:52, schrieb Chris Ridd:> What are the normalization properties of these filesystems? The zfs man page says they''re used when comparing filenames:The normalization properties are set to none. Is this the key to my solution? Achim -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 299 bytes Desc: OpenPGP digital signature URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20110115/3795ca7c/attachment.bin>
On 15 Jan 2011, at 13:57, Achim Wolpers wrote:> Am 15.01.11 14:52, schrieb Chris Ridd: >> What are the normalization properties of these filesystems? The zfs man page says they''re used when comparing filenames: > The normalization properties are set to none. Is this the key to my > solution?Judging from some discussion of normalization on this list in 2009 <http://opensolaris.org/jive/thread.jspa?threadID=110207> I would say so. But I am not really certain of the practical implications of the other settings. It feels like anything apart from "none" would be OK, but maybe one is better than the others? Cheers, Chris
The different methods should be chosen based on the types of clients you expect. Mac and Linux work better with one, and windows works best with another. Searching for "formkc", etc. should yield some information on which is best for your purposes. -B Sent from my Nexus One. On Jan 15, 2011 6:17 AM, "Chris Ridd" <chrisridd at mac.com> wrote:> > On 15 Jan 2011, at 13:57, Achim Wolpers wrote: > >> Am 15.01.11 14:52, schrieb Chris Ridd: >>> What are the normalization properties of these filesystems? The zfs manpage says they''re used when comparing filenames:>> The normalization properties are set to none. Is this the key to my >> solution? > > Judging from some discussion of normalization on this list in 2009 <http://opensolaris.org/jive/thread.jspa?threadID=110207> I would say so.> > But I am not really certain of the practical implications of the othersettings. It feels like anything apart from "none" would be OK, but maybe one is better than the others?> > Cheers, > > Chris > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20110115/09d9cf99/attachment.html>