Orvar Korvar wrote:
Ok, it seems that strange character that looks like a question mark is causing
the problem again. When I try to list a directory which contains a file with
that strange character, I can not list the directory. If I remove the file,
everything works. Then I can list the directory.
I use wireshark from WinXP, installed inside VirtualBox, running on b125. When
I from WinXP Explorer try to enter a ZFS directory which contains a file, whose
filename contains that strange character - I can not. I click on that
directory, and there is a popup window saying something like:
"...\...\....\problematicDirectory is not available. Maybe you do not have the
right to to use this resource. Ask the server's administrator for help.
An unsuspected network error occured"
I see all directories, but I can not enter that directory. Every time I try to
click on that directory, I get this popup window.
I have used wireshark twice. First time when I try to enter this problematic directory, and get this popup window.
The second time is when I enter that same directory, but I have removed that file containing strange characters.
Is this second listing successful ?
Are both of these scenarios captured in the single wireshark file that
you attached?
The problem you are hitting has been addressed (in CR 6888836).
Track this CR to see when the fix is delivered.
So the solution seems to be that ZFS should handle strange characters, then this problem is solved.
A) If I create a zfs filesystem with utf8only, will files containing non utf8 be rejected when copying?
I believe so.
If you do not set utf9only, the files can be copied to zfs but will not
be visible via smb.
They will be omitted from directory listings (see CR 6888836).
That would be a less optimal solution in my opinion. I have to rename all those
files, by hand? Maybe there are lots of them?
B) So can someone please write down the entire syntax to create a zfs
filesystem? I always use mixedcasesensitivity, but I didnt know about nonutf8.
Now I have to move all my files to new zfs filesystems, and which arguments
should I use when creating a zfs filesystem? Which arguments tend to be good to
use when creating a new zfs filesystem? When I create new ZFS filesystems,
which arguments can be good to use?
You could post this question to the zfs-discuss list... but first check
zfs [1M]
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
