toasters January 2001

toasters@lists.teaparty.net

135 participants
157 discussions

RE: Net Stats, where from?
by Bailey, Jourdan 10 Jan '01

10 Jan '01

A similar case I had a couple days ago it was necessary to get a pktt trace to see a client which was running a script against a volume which did not have permissions set. The nfsstat -l command was not very helpful in finding the "Bad" client. It was in the top few of the busy clients, but the filer had a several clients running builds. The pktt converted to a snoop trace showed one client with many permission denied errors. Using top on that client found the program killing the filer performance. Jourdan > -----Original Message----- > From: Mike Smith [mailto:mikesmit@netapp.com] > Sent: Tuesday, January 09, 2001 11:00 PM > To: Sims, Aaron; BrianH(a)dice.com; toasters(a)mathworks.com > Subject: Re: Net Stats, where from? > > > Or you could use the option > > options nfs.per_client_stats.enable on > > Wait a while (say 20 minutes during the time when > the system is being written to heavily - you should be > able to see if it is being written to heavily by running > sysstat 1 for a bit). > > After a period of time you can run the following commands > to see which client/ip is doing what: > > nfsstat -l shows output like the following: > tattoo> nfsstat -l > tattoo> nfsstat -l > 10.32.16.87 cousinit.hq.netapp.com NFSOPS = 172079 (94%) > 10.32.16.88 pugsley.hq.netapp.com NFSOPS = 10580 ( 6%) > > and nfsstat -h will show more detailed output for each > client that is hitting the filer. > > To turn the option off type: > options nfs.per_client_stats.enable off > > There is a small performance penalty for turning on per client > stats. > > Hope that helps. > ~~~~~~~~~~~~~~~ > Mike Smith > Network Appliance > Escalations Engineer > 408-822-4755 > mikesmit(a)netapp.com > Get your answers on > http://now.netapp.com > ~~~~~~~~~~~~~~~~~ > > > > ----- Original Message ----- > From: Sims, Aaron <Aaron.Sims(a)netapp.com> > To: <BrianH(a)dice.com>; <toasters(a)mathworks.com> > Sent: Tuesday, January 09, 2001 7:39 PM > Subject: RE: Net Stats, where from? > > > > Use 'pktt' on the filer to collect > > a packet trace. It's in tcpdump format. > > You can use ethereal (www.ethereal.org) to > > read the trace. From that you should > > be able to find the culprit. > > > > You can use pktt as such: (my comments are in {}) > > > > pktt start e0 { this starts tracing e0 } > > pktt dump { this causes a file to be created with > the content of > the > > dump} > > pktt stop e0 { stops capturing packets on e0 } > > > > THe interface name can be changed to 'all'. > > There are some other options to pktt. > > -d <dir> /* Specifies the directory to put trace in */ > > -b <buffersize> /* How big a buffer to use to capture packets... > > don't make this too large... never more than 1m */ > > -i <ipaddr> /* Self explanitory */ > > > > There are some other options. You can > > search for 'pktt' on NOW to get more info. > > > > Aaron > > > > > > > > > -----Original Message----- > > > From: BrianH(a)dice.com [mailto:BrianH@dice.com] > > > Sent: Tuesday, January 09, 2001 10:07 PM > > > To: toasters(a)mathworks.com > > > Subject: Net Stats, where from? > > > > > > > > > Does anyone know a nice easy way to tell where network > > > traffic is coming > > > from? Something like nfssat -l where you can see that x% of > > > your traffic > > > comes from xxx.xxx.xxx.xxx or something like that? I have > > > tons and tons of > > > writes happending on my 740, which is killing the CPU. The > > > problem is it > > > just started the other day and it is killing the overall > > > performance of the > > > filer. nfsstat -l shows me the number of NFS ops, and none > > > of them seem out > > > of line at all. > > > > > > Ideas? > > > > > > --Brian > > > > > >

1 0

RE: Net Stats, where from?
by Sims, Aaron 10 Jan '01

10 Jan '01

Use 'pktt' on the filer to collect a packet trace. It's in tcpdump format. You can use ethereal (www.ethereal.org) to read the trace. From that you should be able to find the culprit. You can use pktt as such: (my comments are in {}) pktt start e0 { this starts tracing e0 } pktt dump { this causes a file to be created with the content of the dump} pktt stop e0 { stops capturing packets on e0 } THe interface name can be changed to 'all'. There are some other options to pktt. -d <dir> /* Specifies the directory to put trace in */ -b <buffersize> /* How big a buffer to use to capture packets... don't make this too large... never more than 1m */ -i <ipaddr> /* Self explanitory */ There are some other options. You can search for 'pktt' on NOW to get more info. Aaron > -----Original Message----- > From: BrianH(a)dice.com [mailto:BrianH@dice.com] > Sent: Tuesday, January 09, 2001 10:07 PM > To: toasters(a)mathworks.com > Subject: Net Stats, where from? > > > Does anyone know a nice easy way to tell where network > traffic is coming > from? Something like nfssat -l where you can see that x% of > your traffic > comes from xxx.xxx.xxx.xxx or something like that? I have > tons and tons of > writes happending on my 740, which is killing the CPU. The > problem is it > just started the other day and it is killing the overall > performance of the > filer. nfsstat -l shows me the number of NFS ops, and none > of them seem out > of line at all. > > Ideas? > > --Brian >

2 1

following unix soft links
by Coder, James (STP) 09 Jan '01

09 Jan '01

I recently moved users from a Solaris home server to our 760 (6.0.1.r1). filer. The users had created soft links (ln -s) to directories (either within their home directory or to other points via the automounter). Previously the Unix home shares were shared via samba and Unix users in the Windows environment could follow a soft link to the directory. With the data moved to the NetApp, this is no longer available when using CIFS. I opened a case with NetApp and basically the answer was - that's right - the filer won't follow the link to a directory. I have toyed with the idea of using samba on a box and letting the user point to it, thus letting samba provide the share service. Have not tried this, but was wondering if anyone has? Does anyone know of a work-around for this? Thx in advance for any replies. JCC James C. Coder UNIX Administrator Guidant Corporation Phone: 651-582-4797 Email: james.coder(a)guidant.com <mailto:james.coder@guidant.com>

4 4

RE: following unix soft links
by Muhlestein, Mark 09 Jan '01

09 Jan '01

Thanks for posting the good comments, Steve. The name of the config file is /etc/symlink.translations, and it's used to map "rooted" symlinks (i.e. they start with "/"). This is all covered in the documentation. We are developing a solution to this that allows you to securely follow links that leave a share. We'll let folks know when that becomes available. Or watch for bug 15808 to be fixed :-) Mark Muhlestein -- mmm(a)netapp.com > -----Original Message----- > From: Steve Losen [mailto:scl@sasha.acc.virginia.edu] > Sent: Tuesday, January 09, 2001 8:33 AM > To: Coder, James (STP) > Cc: toasters(a)mathworks.com > Subject: Re: following unix soft links > > > > The filer does indeed understand and follow symlinks. Just be > sure the symlink "makes sense" from the filer's perspective. > > Note that under NFS, the filer simply sends the value of the > symlink to the client and the client actually follows it. > So under NFS the filer acts just like any other NFS server with > regard to symlinks. > > Under CIFS, however, the client does not know what a symlink is, > so the filer itself must follow it. So the symlink must "make sense" > to the filer. > > Check out these options in the man pages and Sys. Admin. Guide > > options cifs.home_dir > options cifs.symlinks.enable > options cifs.symlinks.cycleguard > > There is also a file you can create (forgot the name) that the > filer uses to translate symlinks so that they make sense to > the filer. > > To prevent users from circumventing security using symlink tricks, > the filer will not follow all symlinks. But it should follow > any symlink that refers back to the same share, provided the > user has permissions to follow it. And the symlink must make > sense to the filer, so relative symlinks are better than absolute > ones, eg, foo -> ../bar/baz > > Obviously, any symlink that triggers an automount is not going > to work unless the data is on the same filer and you can come up > with a translation that works. > > The cifs.home_dir option is very handy if you have a lot of users. > It allows you to automatically create a share for each user's > home directory. That way a user can attach to \\FILER\loginid > and get straight into their home directory. All the home > directories must have the same name as the loginid and must > be directly beneath the cifs.home_dir directory. You can get > around this restriction by using a directory of symlinks instead. > The symlinks can cross volumes, but not filers. For example, > set up the option like this: > > options cifs.home_dir /vol/vol0/shares > > Assume user bill's home directory is in /vol/vol0/h1/b/bi/bill > > Set up this symlink on the filer: > > /vol/vol0/shares/bill -> /vol/vol0/h1/b/bi/bill > > Now bill can simply attach to \\FILER\bill to get into his > home directory. > > > > I recently moved users from a Solaris home server to our > 760 (6.0.1.r1). > > filer. The users had created soft links (ln -s) to > directories (either > > within their home directory or to other points via the automounter). > > Previously the Unix home shares were shared via samba and > Unix users in the > > Windows environment could follow a soft link to the directory. > > > > With the data moved to the NetApp, this is no longer > available when using > > CIFS. I opened a case with NetApp and basically the answer > was - that's > > right - the filer won't follow the link to a directory. > > > > I have toyed with the idea of using samba on a box and > letting the user > > point to it, thus letting samba provide the share service. > Have not tried > > this, but was wondering if anyone has? Does anyone know of > a work-around > > for this? > > > > Thx in advance for any replies. > > > > JCC > > > > > > > > > > James C. Coder > > UNIX Administrator > > Guidant Corporation > > Phone: 651-582-4797 > > Email: james.coder(a)guidant.com <mailto:james.coder@guidant.com> > > > > Steve Losen scl(a)virginia.edu phone: 804-924-0640 > > University of Virginia ITC Unix Support >

1 0

RE: CIFS and win not res kit SU cmd
by Jankowski Ted-CTJ012 09 Jan '01

09 Jan '01

If you try connecting to the NetApp via IP address, you should be able to log in with a second set of credentials, while keeping your first connection (via name). -Ted -----Original Message----- From: Larry Nail [mailto:lnail@ti.com] Sent: Monday, January 08, 2001 7:40 PM To: neil lehrer; toasters Subject: Re: cifs and win nt res kit SU cmd You can only have 1 set of logon credentials for a file system connection (UNC or Mapped drive) to another CIFS system per logon session (Terminal Server handles logon sessions differently). If you're connected to \\filer\share as nlehrer with your regular account, your credentials will be domain\nlehrer until you disconnect from that system (closing a window doesn't necessarily disconnect you). To connect to the same filer with another logon account, you need to unmount all your connections. You can do this with Windows Explorer (Disconnect Mapped Drive) but that doesn't always show all the connections, so I recommend that you use NET USE to display your drive connections, then use " net use \\filer\<sharename> /d " for each connection to the filer (including ipc$). You can at that point use Windoze Explorer to map a network drive using other credentials (you can not do this from a 9x client) or use " net use \\filer\ipc$ /user:domainname\username password " (you can skip the password if you'd like & you should be prompted). ----- Original Message ----- From: "neil lehrer" <nlehrer(a)ibb.gov> To: "toasters" <toasters(a)mathworks.com> Sent: Wednesday, December 27, 2000 1:00 PM Subject: cifs and win nt res kit SU cmd : hi, : : i am just bringing up an f760 cluster with cifs and nfs. i had just configured : my shares and went to edit some of the files in \etc with wordpad and found that : i was getting access denied, but could edit them when going thru nfs and using : vi. : : after checking a bunch of things it turned out that something wasn't happy about : the way i was accessing the files - using the SU cmd in the nt 4 res kit. : normally i log into my nt machine locally and if i want to do any domain admin : stuff i just open a cmd window and SU to my domain admin acct. saves me from : rebooting or using another machine. in this case i can SU and use srvmgr : against the filer with no problem, but actually editing files that require : administrator privileges doesn't work. i do have the correct mappings in : usermap.cfg and editing does work properly if i do a "normal" domain admin : login. : : any ideas? anybody ever get this to work? : : i really like being able to use SU this way and [in the past] it made it easy to : test access against other ids without moving to another machine or rebooting? : thanks. : : -- : : : regards :

1 0

RE: following unix soft links
by Benn, Paul 09 Jan '01

09 Jan '01

James, Windows (CIFS) clients should indeed be able to follow UNIX symlinks as long as the symlinks do not point to a directory outside of the CIFS share point. This is done to maintain the security of other shares (like, say, c$). I haven't played with Samba in a while but it may operate in a similar way. Regards, Paul Benn Network Appliance -----Original Message----- From: Coder, James (STP) [mailto:james.coder@guidant.com] Sent: Tuesday, January 09, 2001 7:00 AM To: toasters(a)mathworks.com Subject: following unix soft links I recently moved users from a Solaris home server to our 760 (6.0.1.r1). filer. The users had created soft links (ln -s) to directories (either within their home directory or to other points via the automounter). Previously the Unix home shares were shared via samba and Unix users in the Windows environment could follow a soft link to the directory. With the data moved to the NetApp, this is no longer available when using CIFS. I opened a case with NetApp and basically the answer was - that's right - the filer won't follow the link to a directory. I have toyed with the idea of using samba on a box and letting the user point to it, thus letting samba provide the share service. Have not tried this, but was wondering if anyone has? Does anyone know of a work-around for this? Thx in advance for any replies. JCC James C. Coder UNIX Administrator Guidant Corporation Phone: 651-582-4797 Email: james.coder(a)guidant.com <mailto:james.coder@guidant.com>

1 0

Preposterous date/time stamp
by Thomas.L.White＠chase.com 09 Jan '01

09 Jan '01

Well - we have the honor of wearing the egg on our face. I found out from the NT group this a.m. that the files in question exist on the Novell server has these files with future dates already. thanks and sorry for the red herring. tw ---------------------- Forwarded by Thomas L. White/CHASE on 01/09/2001 11:13 AM --------------------------- Thomas.L.White@chase.com@mathworks.com on 01/08/2001 01:48:21 PM Sent by: owner-toasters(a)mathworks.com To: toasters(a)mathworks.com cc: Subject: Preposterous date/time stamp I seem to recall reading about this on the list - but could not find any related emails. Does anyone know of a bug and or fix for the date stamp on files/directories on the filer showing up as 20 to 30 years in the future ? The users are still being migrated to the filers from their old Novell or NT "homes" so this may even be due to "copy method" I'm not sure at this point We have not managed to replicate the error on "command". thanks tw

1 0

RE: following unix soft links
by Traitel, Eyal 09 Jan '01

09 Jan '01

James, 1. A Samba host is able to follow ALL symlinks, including those to automounter directories since it's a user level application, that uses the underline NFS client when needed. A filer is only an NFS server, thus it cannot follow symlinks like: /net/other_host 2. The filer has the /etc/symlink.translations feature, which lets you solve specific link needs. 3. You can use Samba as a workaround, but the better way to handle this is clean the past, and remove old links that are in no need when the data is centralized. As something that I've done in a real-life environment, you'll be amazed how many links-to-nowhere you currently have. By the way - this is a system-slower also, as many users often have long PATH variables that goes to many such non-existing non-existing directories. Hope it helps, Eyal. ---------------------------------------------------------------------- eTraitel - I'm the new eBuzzword around !!! ---------------------------------------------------------------------- Eyal Traitel - Filer Escalation Engineer CNA, MCSE, CSA, NetApp CA Network Appliance BV Holland Office Center Kruisweg 799b 2132 NG, Hoofddorp The Netherlands Office: +31 23 567 9685 Cellular: +31 6 5497 2568 Email: eyal(a)netapp.com ---------------------------------------------------------------------- Get answers NOW! - NetApp On the Web - http://now.netapp.com ---------------------------------------------------------------------- -----Original Message----- From: Coder, James (STP) [mailto:james.coder@guidant.com] Sent: Tuesday, January 09, 2001 4:00 PM To: toasters(a)mathworks.com Subject: following unix soft links I recently moved users from a Solaris home server to our 760 (6.0.1.r1). filer. The users had created soft links (ln -s) to directories (either within their home directory or to other points via the automounter). Previously the Unix home shares were shared via samba and Unix users in the Windows environment could follow a soft link to the directory. With the data moved to the NetApp, this is no longer available when using CIFS. I opened a case with NetApp and basically the answer was - that's right - the filer won't follow the link to a directory. I have toyed with the idea of using samba on a box and letting the user point to it, thus letting samba provide the share service. Have not tried this, but was wondering if anyone has? Does anyone know of a work-around for this? Thx in advance for any replies. JCC James C. Coder UNIX Administrator Guidant Corporation Phone: 651-582-4797 Email: james.coder(a)guidant.com <mailto:james.coder@guidant.com>

1 0

RE: disk_fw_update issue with 840-5.3.7R2
by Tom "Mad Dog" Yergeau 09 Jan '01

09 Jan '01

Spinning up and down isn't the issue. According to the warning displayed when you do a disk_fw_update, even upgrading a single disk, "It involves... suspending all disk I/O to all disks while that is happening" SUSPENDING ALL DISK I/O TO **ALL** (not ONE) DISKS. That's a problem in my environment. So I guess the question is, is the notice wrong and when you're only doing a disk_fw_update on a single disk that's allocated as a spare, it doesn't suspend I/O to ALL disks? ONTAP 6 will be very cool. I'm looking forward to being able to install it soon. I particularly appreciate the new logging features so I can see who did what when. Thanks, MD -----Original Message----- From: Krause, Oliver To: 'Tom "Mad Dog" Yergeau'; 'toasters(a)mathworks.com' Sent: 1/8/01 3:50 PM Subject: RE: disk_fw_update issue with 840-5.3.7R2 As i said you can upgrade a single disk with "disk_fw_update <disk>" without service disruption while this disk is a spare. Again, you have to specify the disk. Also does a disk firmware upgrade not take 2 minutes per disk if you use disk_fw_update. Oliver BTW: ONTAP 6.0 and higher is supposed to do a automatic update when you insert a disk with older firmware (have not tried it yet). Cool, isn't it?

3 2

RE: HSM
by Cormier, Darleen 09 Jan '01

09 Jan '01

Hi Steve, The reason that neither Veritas Storage Replicator or other HSM packages currently support HSM migration of data to and from NetApp filers is because DataONTAP does NOT support DMAPI protocol. DMAPI means Data Management Application Programming Interface and this along with the X/Open Data Storage Management (XDSM) standard allow HSM functionality across a wide range of operating environments without sacrificing system reliability. Without this, the HSM software has no idea of file attributes or location. This reason I'm giving you all this exciting info (YAWN) is that most, if not all, HSM packages use these protocols. Until NetApp is able to support these protocols, or the 3rd party companies are able to come up with some other way of doing HSM, we will not be able to offer an HSM solution to our customers. Now, Good news/ Bad News. The good news is we are receiving more and more requests for this functionality, and I do know that engineering is looking at possibly adding support for the DMAPI protocol. The bad news is that no date has been set for beginning to implement this. Sorry we can't tell you anything better. -----Original Message----- From: SteveRoche(a)datalink.com [mailto:SteveRoche@datalink.com] Sent: Monday, January 08, 2001 12:22 PM To: toasters(a)mathworks.com Subject: HSM Hello everyone! We are considering implementing an F840 with around 4TB into a mixed UNIX and Win2K environment. My question to this much respected community is can we implement an HSM solution like say Veritas Storage Replicator to extract stale files and put them out to tape with a Netapp? I have been told know but am hoping yes. Thanks in advance Steve Roche sroche(a)datalink.com

2 1

← Newer
1
...
9
10
11
12
13
14
15
16
Older →

Jump to page:

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 January 2001