-- Michael W. Sphar - IS&T - Lead Systems Administrator SMBU Engineering Support Services, BMC Software -----Original Message----- From: McCarthy, Tim [mailto:timothy.mccarthy@netapp.com] Sent: Monday, April 18, 2005 6:05 PM To: Sphar, Mike; toasters@mathworks.com Subject: RE: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ... Which is why you write your own locking mechanism ;) --tmac ====================== Tim McCarthy Professional Services/Systems Engineer NetApp Federal Systems, Inc. 410-551-3970 (o) 443-363-0208 (f) tmac@netapp.com tmac-pager@netapp.com ====================== -----Original Message----- From: Sphar, Mike [mailto:Mike_Sphar@bmc.com] Sent: Monday, April 18, 2005 6:38 PM To: toasters@mathworks.com Subject: RE: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ... A lot of file-locking is dependent on the client, of course. Assuming that an NFS file-lock was put in place, it's still up to the client to decide "Okay, that file is locked for writing; I will just open it up in read-only mode instead." That's my understanding anyway...I've never found nfs-based file locking to be terribly reliable. -- Michael W. Sphar - IS&T - Lead Systems Administrator SMBU Engineering Support Services, BMC Software -----Original Message----- From: McCarthy, Tim [mailto:timothy.mccarthy@netapp.com] Sent: Monday, April 18, 2005 4:27 PM To: Doug Chomyn; toasters@mathworks.com Subject: RE: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ... How about writing a wrapper around the file calls that does very proper file locking? I know....more work...just an idea. --tmac -----Original Message----- From: Doug Chomyn [mailto:chomyn@corefa.com] Sent: Monday, April 18, 2005 3:55 PM To: toasters@mathworks.com Subject: Re: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ... Um, I'm looking at dynamic sharing, where if host 1 has rw, hosts 2, 3, 4 have r only. when host 1 relinquishes w, the hosts 2, 3, 4 have the possibility of opening the file for w since they too have the privilege. McCarthy, Tim wrote: >Why not: >(6.5.1 or higher) >exportfs -p ro=host1:host2:host3,rw=host4:netgroup1:subnet/24 >/vol/vol1/path > >--tmac > >-----Original Message----- >From: Doug Chomyn [mailto:chomyn@corefa.com] >Sent: Monday, April 18, 2005 2:24 PM >To: toasters@mathworks.com >Subject: Re: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ... > >Yes, we have SFU installed on the Windows clients and can easily access >the NFS volumes, but I need the "file share" as if the shared document >was on a Windows NT volume, permissions-wise that is ... > >emilio brambilla wrote: > > > >>hello, >> >>Doug Chomyn wrote: >> >> >> >>>document R only, etc, etc. Ordinarily we would do a re-share via >>>Samba, or perhaps make a CIFS volume share, but I'm trying to reduce >>>complexity (and we're not going to buy a CIFS license) ... anyone >>>have experience >>> >>> >>if you have only a few workstations accesing the storage with windows >>sharing you can try installing on each workstation the "microsoft nfs >>client" you can download from http://www.microsoft.com/windows/sfu/ >> >>we did use this workaround 6 month ago to allow a few windows box to >>access a nfs-only fas270C (the customer has 300 unix boxes and only 2 >>windows clients so he did not agree to buy the cifs license) >> >>it's still working and the customer is habby about it, but we had to >>force the workstation to use nfs over tcp in order to have a stable >>connection >> >>if you need it, this is the registry key you have to set to force tcp >>connection: >>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Client for >>NFS\CurrentVersion\Default] "PreferTCP"=dword:00000001 >> >> >> > > > >