Hello, we set our ZFS filesystems to casesensitivity=mixed when we created them. However, CIFS access to these files is still case sensitive. Here is the configuration: # zfs get casesensitivity pool003/arch NAME PROPERTY VALUE SOURCE pool003/arch casesensitivity mixed - # At the pool level it''s set as follows: # zfs get casesensitivity pool003 NAME PROPERTY VALUE SOURCE pool003 casesensitivity sensitive - #>From a Windows client, accessing \\filer\arch\MYFOLDER\myfile.txt fails, while accessing \\filer\arch\myfolder\myfile.txt works.Any ideas? We are running snv_130. -- This message posted from opensolaris.org
was b130 also the version that created the data set? -Tonmaus -- This message posted from opensolaris.org
No the filesystem was created with b103 or earlier. Just to add more details, the issue only occurred for the first direct access to the file.>From a windows client that has never access the file, you can issue:dir \\filer\arch\myfolder\myfile.TXT and you will get file not found, if the file is named myfile.txt on the filesystem. If you browse to the folder using Windows explorer, everything works. Subsequent direct access to the file (using ''dir'') will work as well, as the windows client may be caching the folder information.> was b130 also the version that created the data set? > > -Tonmaus-- This message posted from opensolaris.org
On 14/04/2010 16:04, John wrote:> Hello, > we set our ZFS filesystems to casesensitivity=mixed when we created them. However, CIFS access to these files is still case sensitive. > > Here is the configuration: > # zfs get casesensitivity pool003/arch > NAME PROPERTY VALUE SOURCE > pool003/arch casesensitivity mixed - > # > > At the pool level it''s set as follows: > # zfs get casesensitivity pool003 > NAME PROPERTY VALUE SOURCE > pool003 casesensitivity sensitive - > # > > > From a Windows client, accessing \\filer\arch\MYFOLDER\myfile.txt fails, while accessing \\filer\arch\myfolder\myfile.txt works. > > Any ideas? > > We are running snv_130. >you are not using Samba daemon, are you? -- Robert Milkowski http://milek.blogspot.com
> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- > bounces at opensolaris.org] On Behalf Of John > > Just to add more details, the issue only occurred for the first direct > access to the file. > From a windows client that has never access the file, you can issue: > dir \\filer\arch\myfolder\myfile.TXT and you will get file not found, > if the file is named myfile.txt on the filesystem. > > If you browse to the folder using Windows explorer, everything works. > Subsequent direct access to the file (using ''dir'') will work as well, > as the windows client may be caching the folder information.In that case, I have a hunch the problem is not caused by opensolaris, but a windows bug. Try the following, and see what you get: (a) If you can access file.txt (because you accessed it first) but cannot access file.TXT (because you attempted it second), try rebooting and see if afterward, maybe you can access file.TXT first and then cannot access file.txt (b) Create a share on another windows machine. Browse to the second windows machine from the first windows machine. See if the behavior is the same, going from windows to windows ... without even having opensolaris in the mix. (c) Install wireshark or MS Network Monitor. Sniff the network interface for CIFS traffic while you make these requests. I bet you''ll see that Windows doesn''t even send the request to the server, upon failure. As evidenced by test (a) above, the server will respond just fine even with mixed case.
Just to clarify, there is only one file on the opensolaris cifs server called myfile.txt. myfile.TXT does not exist really, but the cifs server should be case insensitive and return myfile.txt. I did sniff the traffic and opensolaris return ''file not found'' when accessing myfile.TXT. To answer the other question, we are not using Samba :)> > From: zfs-discuss-bounces at opensolaris.org > [mailto:zfs-discuss- > > bounces at opensolaris.org] On Behalf Of John > > > > Just to add more details, the issue only occurred > for the first direct > > access to the file. > > From a windows client that has never access the > file, you can issue: > > dir \\filer\arch\myfolder\myfile.TXT and you will > get file not found, > > if the file is named myfile.txt on the filesystem. > > > > If you browse to the folder using Windows explorer, > everything works. > > Subsequent direct access to the file (using ''dir'') > will work as well, > > as the windows client may be caching the folder > information. > > In that case, I have a hunch the problem is not > caused by opensolaris, but a > windows bug. Try the following, and see what you > get: > > (a) If you can access file.txt (because you accessed > it first) but cannot > access file.TXT (because you attempted it second), > try rebooting and see if > afterward, maybe you can access file.TXT first and > then cannot access > file.txt > > (b) Create a share on another windows machine. > Browse to the second windows > achine from the first windows machine. See if the > behavior is the same, > going from windows to windows ... without even having > opensolaris in the > mix. > > (c) Install wireshark or MS Network Monitor. Sniff > the network interface > for CIFS traffic while you make these requests. I > bet you''ll see that > Windows doesn''t even send the request to the server, > upon failure. As > evidenced by test (a) above, the server will respond > just fine even with > mixed case. > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discu > ss >-- This message posted from opensolaris.org