toasters March 1998

toasters@lists.teaparty.net

48 participants
57 discussions

splitting the load
by Tom Yates 23 Mar '98

23 Mar '98

i'm planning to migrate about one-third of an existing F330's filespace to another F330. what i want to do is move the most frequently accessed third, so it has its own dedicated toaster. there are currently three file trees, each separately listed in exports, each with its own CIFS share. is there any kind of monitoring tool i can use to give me some idea of which of these three is the most heavily used? Tom Yates - Unix Chap - The Mathworks, Inc. - +1 (508) 647 7561 MAG#65061 DoD#0135 AMA#461546 1024/CFDFDE39 0C E7 46 60 BB 96 87 05 04 BD FB F8 BB 20 C1 8C

1 0

Re: NIS Binding Problem
by Jason D. Kelleher 23 Mar '98

23 Mar '98

In message <35119FA5.91C737AD(a)lucent.com>, Dave Heiland writes: >This annoys me since I reported last year when I first set up my Netapp tha >t NIS >wasn't working right. Performance was awful, and it was rebinding to a >different NIS slave every couple of seconds. I never heard much back, and >because I immediately switched to using local netgroups I didn't have the >problem again. At least there will finally be a fix. > >Dave I wouldn't get your hopes up. I was sent that message over 5 months ago... jason >> When we first turned on NIS, everything went to hell. The filer >> started denying mounts to all the clients. Unfortunately, it didn't do >> this right away, took several hours. Seems the filer wasn't getting >> netgroup info. Anyway, here's what NetApp told me: >> >> > Hi Jason, >> > >> > I had one of our escalation engineers look over this >> > call with me. >> > >> > We believe that what you saw when upgrading to 4.1d >> > is the result of an inefficient method we use to >> > "lookup" the YP information. Instead of doing 3 or 4 >> > lookups to get the netgroup info when the mount is >> > checked we would do one for *every* line in the netgroup >> > file. >> > >> > This behavior has been logged as bug#4088 in our database >> > and engineering is working to modify the NIS client to >> > correct this problem. >> > >> > For now the recommendation would be to continue using >> > the local file method which hasn't caused you any >> > problems. When a fix is available for #4088 then you >> > could upgrade and begin using the NIS client for >> > netgroup which should be much faster. One of the >> > benefits of NIS client is that these lookups should >> > be faster but with our first release of this NIS >> > client they simply are not. >> > >> > I have flagged this call record as bug#4088 with all >> > the info you sent to me. The escalation engineer I >> > spoke with is actually the one that will fix the NIS >> > code and by flagging your call record as this bug >> > he can review it during the time he makes the patch. >> > >> > This would first be available as a patch release >> > (a release with a capital D in it such as you >> > were running prior to upgrading to 4.1d). The >> > best way to find out when it is available would be >> > to call back and reference the bug#4088 and ask >> > if Eirik has a patch for the NIS client yet. I >> > would think that you might want to wait 30 days or >> > so -- there is no schedule for a fix date for this >> > right now. >> > >> > Regards, >> > Gil >> >> I never bothered to check back. NOW lists bug #4088 as unfixed. >> Here's our nsswitch.conf which "solved" our problems: >> >> # >> # nfssrv1:/etc/nsswitch.conf >> # >> >> passwd: files nis >> group: files nis >> >> hosts: files nis dns >> netgroup: files nis >> >> Good Luck. >> >> --- >> Jason D. Kelleher kelleher(a)susq.com >> Susquehanna Investment Group 610.617.2721 (voice) >> 401 City Line Ave, Suite 220 610.617.2916 (fax) >> Bala Cynwyd, PA 19004-1122

7 10

Re: netapp-top - display current top NFS clients for a NetApp
by sirbruce＠ix.netcom.com 23 Mar '98

23 Mar '98

On 03/23/98 09:36:38 you wrote: > >Nice little script. Now, the question is, what sort of performance hit will >I take if I turn on nfs.per_client_stats.enable ? I am assuming that on a >moderately loaded f630 it shouldn't be much of a problem. Very little. I know it was measured at one point but it was nothing very important. Probably less than the impact of quotas. And more than worth the tradeoff. For an F630 I doubt it would even register a 1% difference. Bruce

1 0

Re: NetApp Support
by Andrew Hobson 23 Mar '98

23 Mar '98

On Mon, 23 Mar 1998 09:23:00 -0500, Gerard Hickey <Gerard.Hickey(a)nsc.com> said: > Does anyone else out there have problems with NetApp support? Or is it > just me? We've had some serious support issues as well which we vented in a conference call with NetApp. They acknowledged problems and are working to come up with solutions. We'll see. :-) Drew -- "I must obey the inscrutable exhortations of my soul. My mandate also includes weird bugs." -- Calvin

1 0

netapp-top - display current top NFS clients for a NetApp
by Daniel Quinlan 23 Mar '98

23 Mar '98

Here's a useful little script, especially if you ever need to determine which hosts are banging the hardest on an overloaded NetApp. Example output: NFS/s total NFS/s = 2217 | interval = 60 ------ ---------------------------------------- 439 sodium.transmeta.com 437 iridium.transmeta.com 264 tee.transmeta.com 102 manganese.transmeta.com 49 hammer.transmeta.com 43 iron.transmeta.com 41 blighty.transmeta.com 39 curie.transmeta.com ... Before writing this, I usually ended up zeroing the per-client stats or using "diff" between two "nfsstat -l" commands to determine the current top NFS clients. If you make any significant improvements, please send them back to me. Also, please do not post this to Usenet or on a public web site with my email address (spam paranoia). Thanks. - Dan ------- start of cut text -------------- #!/usr/local/bin/perl # netapp-top - display current top NFS clients for a NetApp # Copyright (C) 1998 Daniel Quinlan # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. $default_interval = 60; $prog = $0; $prog =~ s@.*/@@; require "getopts.pl"; &Getopts("hi:"); if (defined $ENV{"LINES"} && $ENV{"LINES"} ne "") { $lines = $ENV{"LINES"}; } else { $lines = 24; } if ($opt_h) { &usage; exit 0; } if ($opt_i && $opt_i > 0) { $interval = $opt_i; } else { $interval = $default_interval; } if ($ARGV[0]) { $host = $ARGV[0]; } else { &usage; exit 1; } sub usage { print <<EOF; usage: $prog [options] filer -h print this help -i n report filer statistics every n seconds ($default_interval is default) The NetApp must have the "nfs.per_client_stats.enable" option "on" for this to work at all. This program must be run this from an admin host as root. EOF } sub print_top { my $total = 0; my $diff; my %recent; foreach $key (keys %nfs_ops_last) { $diff = $nfs_ops{$key} - $nfs_ops_last{$key}; $recent{$key} = $diff; $total += $diff; } $total = int ($total / $interval); system("clear"); printf "%6s\t%s\n", "NFS/s", "total NFS/s = $total | interval = $interval"; printf "%6s\t%s\n", "------", "----------------------------------------"; $i = 0; foreach $key (sort {$recent{$b} <=> $recent{$a} } keys %recent) { printf "%6d\t%s\n", int ($recent{$key} / $interval + 0.5), $ip_name{$key}; last if ($i++ > ($lines - 5)); } } $first = 1; for (;;) { $time_0 = time(); open(NFSSTAT, "rsh $host nfsstat -l|"); while (<NFSSTAT>) { @tmp = split; # ip_address = tmp[0] # ip_name = tmp[1] # nfs_ops = tmp[4] $ip_name{$tmp[0]} = $tmp[1]; $nfs_ops{$tmp[0]} = $tmp[4]; } close(NFSSTAT); if (! $first) { &print_top; } else { $first = 0; } %nfs_ops_last = %nfs_ops; $time_1 = time(); sleep ($interval - ($time_1 - $time_0)); } ------- end ----------------------------

2 1

inn and 630
by David Power 21 Mar '98

21 Mar '98

Has anybody had any success using a 630 as a back end for inn? We are experiencing some horrible thruput issues with large files. The Inn machine is a multi processor sparc 20s w 512 meg ram running 2.6. Nettapp is a 630 8meg nvram 256meg system ram 100bt full duplex connection between the sparc and the netapp. System load is around 10% Systat 1 shows writes are flushed at around 10 sec intervels, cache age is sitting between 11 and 20. To quote my sys admin. "When INN writes an article, it opens it (O_WRONLY|O_CREAT|O_TRUNC), fills the buffer, then writev's to write out the buffer. This works great on small files, but large files are making the writev just hang for a second or so (not coincidentally at the same time that the dnewslink process sleeps in diablo). I tried changing the open to O_WRONLY|O_NONBLOCK|O_CREAT|O_TRUNC, but apparently non-blocking writes don't happen over NFS. Anyway, the key to solving this is getting the Netapps to write big files faster. Any ideas?" David Power V-P Operations Insync Internet Services Inc.

3 2

None
by Mark D Simmons 20 Mar '98

20 Mar '98

Sorry, didn't cc this properly: --- Forwarded mail from "Mark D Simmons" <mds(a)gbnet.net> >From mds(a)gbnet.net Fri Mar 20 22:02:23 1998 Return-Path: <mds(a)gbnet.net> Delivered-To: mds(a)gbnet.net Received: (qmail 7924 invoked by uid 130); 20 Mar 1998 22:02:23 -0000 Date: 20 Mar 1998 22:02:23 -0000 Message-ID: <19980320220223.7922.qmail(a)ns.gbnet.net> From: "Mark D Simmons" <mds(a)gbnet.net> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: tonylai <tonylai(a)ms7.mitac.com.tw> Subject: Re: Disk drives prices Cc: mds(a)gbnet.net Because the NetApp complexity and cost is actually superior to all the vendors I mention as my fall-back choices. For many specific tasks, including other file and database servers, we do in fact use Sun and SGI. NetApp boxes provide vast, easily managed pools of disk that I rarely need to intervene with to keep running so their cost- effectiveness wrt my time is very high. Ditto the availability of the data we keep on them. --- End of forwarded message from "Mark D Simmons" <mds(a)gbnet.net>

1 0

RE: ontap 5.0?
by Cheryl Herfurth 20 Mar '98

20 Mar '98

Hi Dave, I'm very interested in your comments about the 5.0 readme file. We will put it in .html format; that's the easy part. What I'm really interested in is what kind of information you thought was worthless, and more importantly, what kind of information you were looking for. For the 4.3 release, the Read Me First was much longer (some 40 pages) and covered a lot more material. We received several comments that it was too long, and that the Read Me First should be very short and only point to where other information resides. We're in the process of re-designing the entire documentation set and are very interested in customers' expectations about what information goes where. If you have any feedback on this wider issue, please let me know. Thank you for your interest in helping us improve the documentation. If I can be of any further assisntance, please don't hesitate to contact me. Cheryl Herfurth Tech Pubs Manager Network Appliance phone: (408) 367-3522 fax: (408) 367-3451 -----Original Message----- From: Dave Cole [SMTP:dacole@netcom.ca] Sent: Wednesday, March 18, 1998 7:52 AM To: toasters(a)mathworks.com Subject: ontap 5.0? Well, I heard it is out. I went to the now.netapp.com site. I see the announcement, I go to the software library. ONTAP 3.1.6 is the latest recommended release? What happened to 4.3.1? I think something is broken. Either that, or NetApp is celebrating April 1st a little early. I noticed in the 5.0 announcement that they say the Exabyte Mammoth is only supported on the F630. Why would such a limitation be made? And while I'm here, I might mention that the PDF file format is quite possibly the second most annoying thing found on the internet, surpassed only by spam. I blew off far too much time trying to get a reader for the 5.0 readme file, only to find 1.25 pages of almost-completely-useless text. ------------------------------------------------------------- Dave Cole (DC1110) | dacole(a)netcom.ca Systems Administrator | dacole(a)vex.net | office/~dacole/ Netcom Canada | www.vex.net/~dacole/ 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725

1 0

Re: NIS Binding Problem
by Paul Albers 20 Mar '98

20 Mar '98

Hello Tony, There currently is a "D" patch release with the fix for bug #4088 and bug #5086. This patch is available at http://now.netapp.com/ 4.3.1D7 is the release. If you have any questions, please call our Tech Support at 888.463.8277. Regards, -paul At 09:23 AM 3/20/98 +0800, you wrote: >Dave, > > Don't waste your time on NetApp, threw it away and get a new one >from Auspex. > > If you chose Auspex from the first beginning, you won't have any >problem. > Every things has its price, you got lower price, so they gave >you cheaper service. > Auspex's price may be a liitle bit higher, but you get much >more than you pay. > Auspex's URL : www.auspex.com > > > Good Luck ! > > >Tony Lai >---------------------- >Chief Product Manager >Mitac Inc. > >> This annoys me since I reported last year when I first set up my >> Netapp that NIS >> wasn't working right. Performance was awful, and it was rebinding to >> a >> different NIS slave every couple of seconds. I never heard much back, >> and >> because I immediately switched to using local netgroups I didn't have >> the >> problem again. At least there will finally be a fix. >> >> Dave >> >> > When we first turned on NIS, everything went to hell. The filer >> >> > started denying mounts to all the clients. Unfortunately, it didn't >> do >> > this right away, took several hours. Seems the filer wasn't getting >> >> > netgroup info. Anyway, here's what NetApp told me: >> > >> > > Hi Jason, >> > > >> > > I had one of our escalation engineers look over this >> > > call with me. >> > > >> > > We believe that what you saw when upgrading to 4.1d >> > > is the result of an inefficient method we use to >> > > "lookup" the YP information. Instead of doing 3 or 4 >> > > lookups to get the netgroup info when the mount is >> > > checked we would do one for *every* line in the netgroup >> > > file. >> > > >> > > This behavior has been logged as bug#4088 in our database >> > > and engineering is working to modify the NIS client to >> > > correct this problem. >> > > >> > > For now the recommendation would be to continue using >> > > the local file method which hasn't caused you any >> > > problems. When a fix is available for #4088 then you >> > > could upgrade and begin using the NIS client for >> > > netgroup which should be much faster. One of the >> > > benefits of NIS client is that these lookups should >> > > be faster but with our first release of this NIS >> > > client they simply are not. >> > > >> > > I have flagged this call record as bug#4088 with all >> > > the info you sent to me. The escalation engineer I >> > > spoke with is actually the one that will fix the NIS >> > > code and by flagging your call record as this bug >> > > he can review it during the time he makes the patch. >> > > >> > > This would first be available as a patch release >> > > (a release with a capital D in it such as you >> > > were running prior to upgrading to 4.1d). The >> > > best way to find out when it is available would be >> > > to call back and reference the bug#4088 and ask >> > > if Eirik has a patch for the NIS client yet. I >> > > would think that you might want to wait 30 days or >> > > so -- there is no schedule for a fix date for this >> > > right now. >> > > >> > > Regards, >> > > Gil >> > >> > I never bothered to check back. NOW lists bug #4088 as unfixed. >> >> > Here's our nsswitch.conf which "solved" our problems: >> > >> > # >> > # nfssrv1:/etc/nsswitch.conf >> > # >> > >> > passwd: files nis >> > group: files nis >> > >> > hosts: files nis dns >> > netgroup: files nis >> > >> > Good Luck. >> > >> > --- >> > Jason D. Kelleher kelleher(a)susq.com >> > Susquehanna Investment Group 610.617.2721 (voice) >> > 401 City Line Ave, Suite 220 610.617.2916 (fax) >> > Bala Cynwyd, PA 19004-1122 > > > > >

1 0

Re: NIS Binding Problem
by Jason D. Kelleher 20 Mar '98

20 Mar '98

In message <3510F4A6.701C13F2(a)mitre.org>, "John F. Kane" writes: >I have not located any reported bugs in the NOW Bugs Online >database that resemble this problem. Is NetApp aware of this >problem and working a solution? Turning off NIS may stop >the problem from reoccurring but is not a solution to the problem. >The NetApp NIS implementation is a relatively new addition to >ONTAP and may need some attention. > >John Kane > >geen wrote: > >> John, >> >> I saw the same thing with 4.3.1. My solution was to turn off NIS. >> >> -g d geen >> >> geen(a)ti.com >> >> John F. Kane wrote: >> >> > Has anyone experienced NIS binding problems on their filers? >> > We have four filers (3 F330s & 1 F230) running Ontap 4.3R3 >> > that have been locking out users on a few occasions this past week >> > The UNIX servers and user workstations trying to access the >> > filers are reporting "server not responding: RPC: Timed out" errors. >> > There is not much helpful in the filer logs. In order to unhang the >> > filer, we must manually rebind it to a different NIS slave server. >> > >> > -- >> > John F. Kane When we first turned on NIS, everything went to hell. The filer started denying mounts to all the clients. Unfortunately, it didn't do this right away, took several hours. Seems the filer wasn't getting netgroup info. Anyway, here's what NetApp told me: > Hi Jason, > > I had one of our escalation engineers look over this > call with me. > > We believe that what you saw when upgrading to 4.1d > is the result of an inefficient method we use to > "lookup" the YP information. Instead of doing 3 or 4 > lookups to get the netgroup info when the mount is > checked we would do one for *every* line in the netgroup > file. > > This behavior has been logged as bug#4088 in our database > and engineering is working to modify the NIS client to > correct this problem. > > For now the recommendation would be to continue using > the local file method which hasn't caused you any > problems. When a fix is available for #4088 then you > could upgrade and begin using the NIS client for > netgroup which should be much faster. One of the > benefits of NIS client is that these lookups should > be faster but with our first release of this NIS > client they simply are not. > > I have flagged this call record as bug#4088 with all > the info you sent to me. The escalation engineer I > spoke with is actually the one that will fix the NIS > code and by flagging your call record as this bug > he can review it during the time he makes the patch. > > This would first be available as a patch release > (a release with a capital D in it such as you > were running prior to upgrading to 4.1d). The > best way to find out when it is available would be > to call back and reference the bug#4088 and ask > if Eirik has a patch for the NIS client yet. I > would think that you might want to wait 30 days or > so -- there is no schedule for a fix date for this > right now. > > Regards, > Gil I never bothered to check back. NOW lists bug #4088 as unfixed. Here's our nsswitch.conf which "solved" our problems: # # nfssrv1:/etc/nsswitch.conf # passwd: files nis group: files nis hosts: files nis dns netgroup: files nis Good Luck. --- Jason D. Kelleher kelleher(a)susq.com Susquehanna Investment Group 610.617.2721 (voice) 401 City Line Ave, Suite 220 610.617.2916 (fax) Bala Cynwyd, PA 19004-1122

4 3

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 March 1998