toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

Clearcase VOB Installation
by bhaskar.g＠philips.com 26 Jun '00

26 Jun '00

Hi All, Has any one tried to mount the vobs( of clearcase) on the Filer. If so let us know the way to mount the vobs. kind regards Bhaskar G Philips Semiconductors, #3, Sterling Square,Madras Bank Road, Off St Mark's Road,BANGALORE-560 001. Voice : +91 80 222 9200 Ext 5060 Fax: +91 80 2229700

1 0

Default quota tree quota ?
by Steve Losen 25 Jun '00

25 Jun '00

We recently upgraded to 5.3.5R2P2. In the release notes in the section "New features of Data ONTAP 5.3.4" I saw this under "Quota Features": You can now create a default tree quota that applies to any qtree that does not have an entry in /etc/quotas or any qtree that is created after the default tree quota goes into effect. I couldn't find this documented anywhere in the man pages or the Sys Admin Guide. So I went ahead and put this entry in /etc/quotas, just guessing the syntax: * tree 99M 99K I ran "quota off h2" and "quota on h2" and got no complaints. We recently created a new qtree and added this entry for it in /etc/quotas /vol/h2/t15 tree 1000M 1000K When I ran "quota resize h2" it complained about this new entry. So then I tried this, figuring the default quota might be a per volume thing: /vol/h2/* tree 99M 99K But the quota command didn't accept it, saying "/vol/h2/*: no such file or directory". So I guess this feature isn't there yet. If I'm just not doing it right, could someone tell me how? Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

3 2

Legato & Veritas questions
by Jay Orr 23 Jun '00

23 Jun '00

Since we're looking at different backup solutions, wondering if I could pick the group's respective brains... First, for non NDMP backup, is there special client packs required for either (and is netapp dump supported)? I'm going through Sun since they sell both and they were unaware of any. Second, any thing to be aware/careful about with either backup solution? Third, any problems with ClearCase and either package? Much thanks! ----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO

2 1

Veritas SANPoint (tm) Storage Appliance
by Riasat_Amin＠notes.amdahl.com 22 Jun '00

22 Jun '00

Does anybody have any experience of this product who would like to share thier knowledge in how it compares with the Filers ? According to Veritas this product turns a SPARC based computer system into high performance NT and UNIX storage server. At the moment it is only available for Sparc based systems. Thx and Regards Riasat

2 1

Re: Filer (F740) with CIFS and NT Terminal Server Edition (Metafr ame)
by Moshe Linzer 22 Jun '00

22 Jun '00

>From owner-toasters(a)mathworks.com Thu Jun 22 00:16:31 2000 >To: toasters(a)mathworks.com >Subject: Re: Filer (F740) with CIFS and NT Terminal Server Edition (Metafr ame) >Date: Wed, 21 Jun 2000 15:14:48 -0400 >From: Steve Losen <scl(a)sasha.acc.virginia.edu> >Precedence: bulk > > >> If you make absolute links (beginning with a leading slash) you need to consider >> how the filer is going to resolve those since the UNIX exports and CIFS shares >> may be coming from different paths. The /etc/symlink.translations file is used >> to help the filer interpret absolute symbolic links. >> >> If pchome is full of links to another directory on the filer and you use >> relative links you should be fine. You also need to enable symlinks with the >> cifs.symlinks.enable option >> >> /vol/vol0/pchome >> bob -> ../home_systems/bob >> jim -> ../home_software/jim >> >> /vol/vol0/home_systems >> bob >> >> /vol/vol0/home_software >> jim >> >> Dennis Haag >> > >The cifs.symlinks.enable option and the /etc/symlink.translations file >aren't necessary here. > >When you use the cifs.home_dir directory, you are implicitly defining a >bunch of user shares. Essentially the cifs.home_dir directory and its >contents is configuration data that is internal to the filer, and the >filer understands symlinks. > >The cifs.symlinks.enable option and the /etc/symlink.translations file are >for handling the situation where a CIFS client tries to access a symlink. >CIFS clients don't understand symlinks, so you must configure the filer to >either 1) follow the symlink and return what the symlink refers to, or 2) >deny access to the symlink. > >Note that this is not an issue with NFS because the client follows the >symlink, not the server. So when a NFS client accesses a symlink, the >filer simply returns it. This is not possible with CIFS where the >client does not understand what a symlink is. > Exactly as Steve describes. This does not involve the whole issue of cifs symlinks, so links can be made to home dirs even across qtrees or shares. The links are absolute, not relative, because they are examined by the filer only, not the client. Moshe ----------------------------------------------------------------------------- Moshe Linzer | On the Internet, Unix Systems Manager | National Semiconductor, Israel | nobody knows you're a moron. Phone: 972-9-970-2247 | Fax: 972-9-970-2001 | - Network Magazine Email: moshel(a)nsc.com | -----------------------------------------------------------------------------

1 0

RE: Filer (F740) with CIFS and NT Terminal Server Edition (Metafr ame)
by Dennis.Haag＠netapp.com 21 Jun '00

21 Jun '00

If you make absolute links (beginning with a leading slash) you need to consider how the filer is going to resolve those since the UNIX exports and CIFS shares may be coming from different paths. The /etc/symlink.translations file is used to help the filer interpret absolute symbolic links. If pchome is full of links to another directory on the filer and you use relative links you should be fine. You also need to enable symlinks with the cifs.symlinks.enable option. /vol/vol0/pchome bob -> ../home_systems/bob jim -> ../home_software/jim /vol/vol0/home_systems bob /vol/vol0/home_software jim Dennis Haag -----Original Message----- From: Moshe Linzer [mailto:moshel@taux01.nsc.com] Sent: Wednesday, June 21, 2000 8:09 AM To: toasters(a)mathworks.com Cc: David.Lockwood(a)benettonformula.com Subject: Re: Filer (F740) with CIFS and NT Terminal Server Edition (Metaframe) We are actually doing this slightly differently. The filer started out as pure Unix, so everything is using Unix security. When we added the Winframe servers (soon to move to TSE or Win2000), I found that I was able to make a CIFS Home directory on the filer: options cifs.home_dir /pchomes Then from the /pchomes directory, make symbolic links to the users actual (unix) home directory on the filer: bob -> /homes_systems/bob jim -> /homes_software/jim Now the user's home dir will be visible under TSE as \\filer\userid (assuming the same userids on NT and Unix). You can setup the user's profile on TSE to mount this path automatically upon login. The beauty is that no unix home dirs have to be changed, and no additional mounts or automounts are needed. Moshe >From owner-toasters(a)mathworks.com Wed Jun 21 14:52:50 2000 >Date: Wed, 21 Jun 2000 10:57:00 +0100 >From: "David Lockwood" <David.Lockwood(a)benettonformula.com> >To: <toasters(a)mathworks.com> >Subject: Filer (F740) with CIFS and NT Terminal Server Edition > (Metaframe) >Mime-Version: 1.0 >Content-Disposition: inline >Content-Transfer-Encoding: 8bit >X-MIME-Autoconverted: from quoted-printable to 8bit by smtp.mathworks.com id FAA02894 >Precedence: bulk > >Has anybody had any experience using a filer with NT Terminal Server Edition and Metaframe. I want to be able to have users UNIX (HP-UX 10.20) home directories on the filer and for the user to also be able to access that data from their Terminal Server (Metaframe 1.8) session. > > > >---------------------------------------------------------------------- > >For further information on Benetton Formula 1 visit our web site at www.benettonf1.com. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please destroy and notify Benetton Formula on +44 1608678000. > >---------------------------------------------------------------------- > ----------------------------------------------------------------------------- Moshe Linzer | On the Internet, Unix Systems Manager | National Semiconductor, Israel | nobody knows you're a moron. Phone: 972-9-970-2247 | Fax: 972-9-970-2001 | - Network Magazine Email: moshel(a)nsc.com | -----------------------------------------------------------------------------

2 1

RE: CIFS file locking problem
by mark.muhlestein＠netapp.com 21 Jun '00

21 Jun '00

The way it works is that if a CIFS client has open files but no command has been received at the filer for 10 minutes, we send a keep-alive NETBIOS message. That then goes through the normal TCP timeout logic, which will normally take 520 sec or so. That means the total elapsed time for a non-responsive connection to timeout is just under 20 minutes. If you can verify that the locks are still present after more than 20 minutes, please let us know. We'll have to take a packet trace to see what is going on. Mark > -----Original Message----- > From: Dave Atkin [mailto:dla1@york.ac.uk] > Sent: Wednesday, June 21, 2000 12:41 AM > To: Muhlestein, Mark > Cc: toasters(a)mathworks.com > Subject: RE: CIFS file locking problem > > > On Mon, 19 Jun 2000 mark.muhlestein(a)netapp.com wrote: > > <cut> > > > As to the protocol issues, as Bruce said, we're more or > less stuck with them > > because of Microsoft compatibility. If a session goes away > when there is no > > request pending (i.e. we don't owe the client a response), > the filer delays 10 > > minutes before terminating the session. This is to keep the > session alive in the > > face of temporary network partitions, which we can't > distinguish from just > > losing a client. Currently that 10 minute interval is not > configurable on the > > filer, but it sounds like we might want to make it so. > > > > This 10 minute timeout doesn't seem to be working. I tried > this with my PC > yesterday. It had approx 13 locks, I turned the power off, > and after an > hour the filer still thought the locks were active. However > they have gone > this morning, after around 16 hours. We're running 5.3.5. > > -- > Dave Atkin, Head of Technical Services > Computing Service, University of York, YORK YO10 5DD > Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 > Email: D.Atkin(a)york.ac.uk >

1 0

NFS connection from Novell Netware 5
by David Lockwood 21 Jun '00

21 Jun '00

Does anyone have experience of using a filer and NFS mounting a directory from a Novell NetWare 5 server ? Is it as simple as adding the NFS client to Netware 5 and following the normal NFS mount process ---------------------------------------------------------------------- For further information on Benetton Formula 1 visit our web site at www.benettonf1.com. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please destroy and notify Benetton Formula on +44 1608678000. ----------------------------------------------------------------------

1 0

Re: Filer (F740) with CIFS and NT Terminal Server Edition (Metaframe)
by Moshe Linzer 21 Jun '00

21 Jun '00

We are actually doing this slightly differently. The filer started out as pure Unix, so everything is using Unix security. When we added the Winframe servers (soon to move to TSE or Win2000), I found that I was able to make a CIFS Home directory on the filer: options cifs.home_dir /pchomes Then from the /pchomes directory, make symbolic links to the users actual (unix) home directory on the filer: bob -> /homes_systems/bob jim -> /homes_software/jim Now the user's home dir will be visible under TSE as \\filer\userid (assuming the same userids on NT and Unix). You can setup the user's profile on TSE to mount this path automatically upon login. The beauty is that no unix home dirs have to be changed, and no additional mounts or automounts are needed. Moshe >From owner-toasters(a)mathworks.com Wed Jun 21 14:52:50 2000 >Date: Wed, 21 Jun 2000 10:57:00 +0100 >From: "David Lockwood" <David.Lockwood(a)benettonformula.com> >To: <toasters(a)mathworks.com> >Subject: Filer (F740) with CIFS and NT Terminal Server Edition > (Metaframe) >Mime-Version: 1.0 >Content-Disposition: inline >Content-Transfer-Encoding: 8bit >X-MIME-Autoconverted: from quoted-printable to 8bit by smtp.mathworks.com id FAA02894 >Precedence: bulk > >Has anybody had any experience using a filer with NT Terminal Server Edition and Metaframe. I want to be able to have users UNIX (HP-UX 10.20) home directories on the filer and for the user to also be able to access that data from their Terminal Server (Metaframe 1.8) session. > > > >---------------------------------------------------------------------- > >For further information on Benetton Formula 1 visit our web site at www.benettonf1.com. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please destroy and notify Benetton Formula on +44 1608678000. > >---------------------------------------------------------------------- > ----------------------------------------------------------------------------- Moshe Linzer | On the Internet, Unix Systems Manager | National Semiconductor, Israel | nobody knows you're a moron. Phone: 972-9-970-2247 | Fax: 972-9-970-2001 | - Network Magazine Email: moshel(a)nsc.com | -----------------------------------------------------------------------------

1 0

Backup Technology
by Derek Kelly 21 Jun '00

21 Jun '00

Has anyone on the list had experience (good or bad) using Overland Data SANPiper (a SCSI-to-Fibre Channel bridge technology) or Vixel switches in thier backup strategy? If so, please let me know. We are looking at implementing one of these solutions and are interested in any opinions or possible caveats we might hit. Thanks, Derek Kelly Genomecorp [dkelly(a)genomecorp.com - CSSG] If you can't beat your computer at chess, try kickboxing.

1 0

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