I've been getting entry's in my logs that look like this since I upgrade ONTAP from 6.1.2R3 to 6.3.1R1 and updated the system documentation on the filer.
Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\html\filer Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\html\netapp Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\html\ontap Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\pdfs\filer Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\pdfs\netapp Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\pdfs\ontap
Steve Evans SDSU Foundation (619) 594-0653
I've been getting entry's in my logs that look like this since I upgrade ONTAP from 6.1.2R3 to 6.3.1R1 and updated the system documentation on the filer.
Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\html\filer Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\html\netapp Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\html\ontap Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\pdfs\filer Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\pdfs\netapp Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: ~snapshot\nightly.0\etc\http\doc\pdfs\ontap
Steve Evans SDSU Foundation (619) 594-0653
When you create a new directory with NFS, it is not in CIFS unicode format unless you have
options wafl.create_ucode on
In the live filesystem, when an unconverted directory is first accessed via CIFS, the filer converts it automatically. But if CIFS tries to access an unconverted directory that is in a snapshot, then the filer cannot modify the directory and CIFS cannot access it, so you get the above errors.
There is also an option called wafl.convert_ucode that causes any unconverted directory to be converted to ucode whether accessed by NFS or CIFS.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
-
Steve Evans -
Steve Losen