2010-10-01 04:27 PM
On our Data ONTap 7.3.3 box we're having issues.
|FlexClone ?||-||Containing Aggregate:||aggr0|
|Used Capacity:||42.6 GB||Space Guarantee||volume|
|Total Capacity:||120 GB||Total Size:||150 GB|
|Number of Files:||98.3 k||Max Directory Size:||8.96 MB|
|Max Files:||4.67 m|
|SNAP Mirror?||-||SNAP Directory?|
|SNAP?||Resync SNAP Time:||60|
|SVO Enable?||-||SVO Checksum?||-|
|Allow SVO RMAN?||-||SVO Reject Errors?||-|
|Create Unicode?||Convert Unicode?|
|Minimal Read Ahead?||-||NV Fail?||-|
|Fractional Reserve :||100||Extent?||-|
|FS Size Fixed?||-||Update Access time?|
Solved! SEE THE SOLUTION
2010-10-01 04:53 PM
Try to turn these options ON for that specific volume, where the files have been created from the Linux client. CIFS would freak out, if these options are not turned on.
2010-10-04 09:45 PM
That was it. Apparently there are three unicode controls on a NetApp filer, only two of which can be changed from the web interface on an existing volume. And you have to reboot the filer after changing the language!
The C.utf8 language worked to keep both our CIFS and NFS clients happily in Unicode filenames. Thanks.
|Protocols in use||Volume language|
|NFS Classic (v2 or v3) only||Language setting does not matter|
|NFS Classic (v2 or v3) and CIFS||Language of the clients|
|NFS v4, with or without CIFS||cl_lang.UTF-8, where cl_lang is the language of the clients.|