toasters

toasters@lists.teaparty.net

13520 discussions

RE: Snapshot access from CIFS Windows XP SP2 Previous Versions.
by Adams, Tim 20 Apr '05

20 Apr '05

It has to do with how your permissions are setup on the xp machine. If you go to folder options and make sure that you check can not see hidden files or folders or hide protected system files you won't see the snapshot folder. Hope this helps. Tim Adams Technical Analyst - Server Desk Phone: 952-238-2546 iDen: 612-221-5946 DAP: 104*189*26 Fax: 952-238-7346 E-mail: Tim.Adams(a)nextelpartners.com From his neck down a man is worth a couple of dollars a day, from his neck up he is worth anything that his brain can produce. -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Holland, William L Sent: Wednesday, April 20, 2005 8:21 AM To: 'toasters(a)mathworks.com' Subject: RE: Snapshot access from CIFS Windows XP SP2 Previous Versions. My guess is that it is somehow related to the cifs.ms_snapshot_mode setting -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:r.stansfield@rri.sari.ac.uk] Sent: Wednesday, April 20, 2005 9:11 AM To: toasters(a)mathworks.com Subject: Snapshot access from CIFS Windows XP SP2 Previous Versions. A colleague has just told me that, with SP2 installed on Windows XP, File, Properties, Previous Versions displays snapshots. This has also come as a surprise to someone else: http://winxp.uwaterloo.ca/Documentation/WXP_SP2_ADSworkstation.htm#Snaps hot Is this documented somewhere? Any more information? Roger Stansfield This message, including any attachments, contains confidential information intended for a specific individual and purpose and is protected by law. If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this email. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

1 0

Snapshot access from CIFS Windows XP SP2 Previous Versions.
by Roger Stansfield 20 Apr '05

20 Apr '05

A colleague has just told me that, with SP2 installed on Windows XP, File, Properties, Previous Versions displays snapshots. This has also come as a surprise to someone else: http://winxp.uwaterloo.ca/Documentation/WXP_SP2_ADSworkstation.htm#Snapshot Is this documented somewhere? Any more information? Roger Stansfield

2 1

RE: Snapshot access from CIFS Windows XP SP2 Previous Versions.
by Cory.Wolf＠EmersonProcess.com 20 Apr '05

20 Apr '05

I just discovered the same thing. I did a search on Microsoft's site and read KB Article 888603, which describes some registry edits that can 1) Disable the "Restore" button on the Previous Version Tab 2) Disable the "Previous Versions" tab I tried disabling the "Previous Versions" tab, rebooted and still could see the "Previous Versions" tab. I am continuing to look for a solution, but am interested if anyone else has worked with this issue and has a work around. Thanks, Cory -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Roger Stansfield Sent: Wednesday, April 20, 2005 7:41 AM To: toasters(a)mathworks.com Subject: Snapshot access from CIFS Windows XP SP2 Previous Versions. A colleague has just told me that, with SP2 installed on Windows XP, File, Properties, Previous Versions displays snapshots. This has also come as a surprise to someone else: http://winxp.uwaterloo.ca/Documentation/WXP_SP2_ADSworkstation.htm#Snapshot Is this documented somewhere? Any more information? Roger Stansfield

1 0

Quota-related fixes in ONTAP 7.x
by Chris Thompson 19 Apr '05

19 Apr '05

The various quota-related problems in ONTAP 7.x that were being talked about on toasters last month have fixes according to NOW: 153377 quotas wrongly reverting to default on a "quota resize" supposed to be fixed in 7.0.0.1P4 154530 per-user/group quotas wrongly affecting the results of statvfs() supposed to be fixed in 7.0.0.1P5 Can anyone who has tried these ONTAP versions confirm the fixes? -- Chris Thompson Email: cet1(a)cam.ac.uk

1 0

RE: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ...
by Sphar, Mike 18 Apr '05

18 Apr '05

Hey, if you can build your own file locking mechanism into Microsoft Office, more power to you! ;) -- 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(a)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(a)netapp.com tmac-pager(a)netapp.com ====================== -----Original Message----- From: Sphar, Mike [mailto:Mike_Sphar@bmc.com] Sent: Monday, April 18, 2005 6:38 PM To: toasters(a)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(a)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(a)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(a)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 >> >> >> > > > >

1 0

RE: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ...
by McCarthy, Tim 18 Apr '05

18 Apr '05

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(a)netapp.com tmac-pager(a)netapp.com ====================== -----Original Message----- From: Sphar, Mike [mailto:Mike_Sphar@bmc.com] Sent: Monday, April 18, 2005 6:38 PM To: toasters(a)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(a)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(a)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(a)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 >> >> >> > > > >

1 0

RE: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ...
by Sphar, Mike 18 Apr '05

18 Apr '05

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(a)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(a)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(a)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 >> >> >> > > > >

1 0

RE: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ...
by McCarthy, Tim 18 Apr '05

18 Apr '05

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(a)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(a)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 >> >> >> > > > >

1 0

RE: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ...
by McCarthy, Tim 18 Apr '05

18 Apr '05

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(a)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 >

3 2

File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ...
by Doug Chomyn 18 Apr '05

18 Apr '05

Sorry if this a bit lame. Basically, I want to file share .xls documents stored on an NFS volume between Windows clients so that when one client with RW on the document has access, another Windows client can open the 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 with doing this kind of thing? Is it possible? tx doug

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters