toasters October 2002

toasters@lists.teaparty.net

69 participants
84 discussions

RE: Root permissions failing.
by Toal, Dave 08 Oct '02

08 Oct '02

Chris, To allow world read-write access, try exportfs with 'exportfs -i -o anon=0 /vol/volname'? -----Original Message----- From: Chris Josephes To: toasters(a)mathworks.com Sent: 10/7/02 10:03 PM Subject: Root permissions failing. I have one Solaris host using a NetApp for home directories. I want to transition the content over to a newer NetApp, and take the other system out of commision. However, when I tried to rsync the files, it complained about permissions errors. I tried a manual chown, which failed, and I discovered that chmod fails as well. So, it would look like the Solaris client does not have root permissions on the NetApp. But, the export configs on both NetApps are identical, and I did specify root access in the exports file (and tried a couple of variations using "exportfs -i", including specifying the whole class C the Solaris host was in). Hostname resolution is going through the local files table, and then DNS. The new NetApp and the Solaris client both have host table entries for the IP of the other host. The new NetApp is a 720, running 5.3.6r1. Any ideas? -- _______________ Chris Josephes __/ MRNet/Onvoy \ chrisj(a)mr.net __/ www.onvoy.com / \________________/

1 0

RE: upgrading the ONTAP version
by Paul Caron 07 Oct '02

07 Oct '02

That fixed it. >From: "Potakamuri, Sreenivasa" <Sreenivasa.Potakamuri(a)netapp.com> >To: "'Paul Caron'" <caron(a)sig.com> >Subject: RE: upgrading the ONTAP version >Date: Fri, 4 Oct 2002 11:43:58 -0700 >MIME-Version: 1.0 > >Please remove the following line from /etc/registry.local file manually. > > options.cifs.access_logging.buffer_size=4096 > >That should fix your problem. We have filed a bug (number: 60595) for this. >We will make it online soon. > > >Please let me know the result after removing the line. > > >Thanks, >Sreeni

1 0

Summary: Gig Enet and Filer NFS problems
by Darragh, Stephen J 07 Oct '02

07 Oct '02

> Problem: > Clients using nfs (Sun and HP unix workstations) were taking much > longer to open files. > Home, Tools, and Project data was moved to the filer and it was > running GigE > To open a drawing, it took 2hrs vs 20min on a older Sun server > running 100mb ethernet. > Data OnTap v6.1.2R1 > > Once we made changes, it now takes 18min to open the same drawing (this is > a > normal time for the types of schmetics they are working on). > > Solution (so far): > Use options nfs.udp.xfersize 8192 (instead of the default 32768) > Also, set the filer to match the cisco switch for flow control > (cisco has send flow, filer now has receive) > > ToDo: > Investigation to see if full flow control will improve performance > even more. > Try enabling TCP over nfs > Make sure that the xfersize does not serously affect the few > machines we have on GigE that mount from the filer > > Thanks to the following for all the help and email (hope I didn't forget > anyone). > > Philip Meidell > John F. Detke > Paul Jones > Neil Stichbury > Mike Ball > Adam Fox > Neil Stichbury > devnull(a)adc.idt.com (whoever your are :-) > > ----------------- Details from some of the responses > > The major known issue is with NFS over UDP and packet drops causing the > UDP cascading error problem. If you are running NFS over UDP I'd strongly > suggest switching to NFS over TCP. > > I believe this is a buffering issue, where the Gig interface is > "overloading" a buffer somewhere on its way to a 100M interface, and > packets gets dropped. When that happens the entire UDP datagram gets > resent. Also check rsize/wsize on the client, it may work better set to > 8k, rather than the (default?) 32KB. > > This problem is related to network hardware, I've seen in most often on > Cisco gear but it happens with others too. A quick nfsstat on client(s) > can show the problem, look for retrans stats. > --------- > We had a similar problem and solved it by changing the UDP transfer size. > Have a look at bug ID 29146 which includes the following :- > > "In Data ONTAP 5.3.4 and earlier releases the default UDP transfer size > is > > 8192. In 5.3.5 and later releases the default is 32768. This larger value > improves performance in some situations, but may cause problems in others. > > Problem 1 - 100-Mbit client is reading from Gigabit interface With the > larger > default, problems may result when the Gigabit interface on the filer is > sending > to a 100-Mbit client. Switches can drop packets on the outbound 100-Mbit > port > because too many packets become queued due to the difference in line > speeds > and > the larger transfer size. Few complete 32K UDP datagrams are received by > the > > client, and the client assumes the filer has gone away and increases its > delay > between retries. Poor performance may be seen. If a client does not > specify > the > rsize and wsize parameters in the mount command, the filer's default UDP > transfer size is used. If a client does specify rsize and wsize, and the > values > are larger than the default, then the default is used. This means that you > may > see problems after you upgrade from 5.3.4 (or earlier release) to 5.3.5 > (or > later release) if the resulting transfer size is 32768. Problem 2 - > Multiple > > clients are reading from 100-Mbit interface When the UDP transfer size is > 32768 > and multiple clients are reading from a 100-Mbit interface, the driver > transmit > queue on the filer can overflow more readily and packets may be discarded. > This > can lead to erratic or poor performance on the clients." > > --- > First thing to check in GigE is typically flow control settings on the > switch, filer, and client side. Typically it's best to have both > transmit and receive flow control turned on. On the filer, it's > called full flowcontrol. That isn't the default for some switch > vendors and OS NICs. > > It's at least a start. Like most performance issues, you may > have to work several rounds of stuff to find the culprit. Before > you open a case with NTAP, which I strongly suggest, you may need > to quantify your performance in some way. MB/sec is a good one. > By putting a value on your performance it's easier to figure out > what areas could be wrong and also easier to figure out when > you can't get anymore based on your environment. That's the thing > with Gigabit, most clients can't max it out so you will hit a ceiling > for a single client that is less than the capacity of the wire. > Slower forms of Ethernet were easier in this way because you knew > pretty much where the ceiling was. > > --- > now that you have mentioned running Sun boxes try this > in the /etc/system file of one of them and see if you perceive > a performance improvement. > > set sq_max_size=2048 > set nstrpush = 90 > set nfs:nfs3_max_threads = 24 > set nfs:nfs3_nra = 10 > set nfs:nfs_max_threads = 24 > set nfs:nfs_nra = 10 > --- > > When you're using NFS over UDP with disparate speeds, i.e. gigabit to the > switch, then fast ethernet to clients, you can address performance > problems > in > one of two ways: > > 1) If all of your client machines are on fast ethernet (yep, that means NO > > gigabit clients) the simple approach is to set the filer option > > options nfs.udp.xfersize 8192 > > If you do have gigabit clients, doing the above will impact performance to > them, > in which case you have to do the more management intensive step two... > > 2) If you have some gigabit client machines, add the following options to > the > mount command on each 100 Mbit client machine: > wsize=8192,rsize=8192 > > >

1 0

Samba server as PDC ?
by Frank Bonnet 07 Oct '02

07 Oct '02

Hi Does anybody has already used a samba server as PDC for a filer ? We actually use samba servers with LDAP (openldap) authentication and I wonder if it would be possible to use a filer in such configuration ? Actually PCs use samba servers as PDC, the samba servers use NFS to store user's data thru NFS mounts. I know it is far to be the best configuration and I would like to let PC users use SMB directly to the filer using samba servers as PDC only. infos welcome. Thanks a lot -- Frank Bonnet

3 3

is it bad that disk scrubs don't finish
by Daniel Finn 07 Oct '02

07 Oct '02

More often than not the disk scrubbing on the netapps that I have don't finish. I assume this is because most of them see pretty high I/O and the netapp puts that I/O in higher order than the disk scrub. The disk scrub can be though of as a parity check correct?

2 1

Summary: Gig Enet and Filer NFS problems
by Darragh, Stephen J 05 Oct '02

05 Oct '02

> Problem: > Clients using nfs (Sun and HP unix workstations) were taking much > longer to open files. > Home, Tools, and Project data was moved to the filer and it was > running GigE > To open a drawing, it took 2hrs vs 20min on a older Sun server > running 100mb ethernet. > Data OnTap v6.1.2R1 > > Once we made changes, it now takes 18min to open the same drawing > (this is anormal time for the types of schmetics they are working on). > > Solution (so far): > Use options nfs.udp.xfersize 8192 (instead of the default 32768) > Also, set the filer to match the cisco switch for flow control > (cisco has send flow, filer now has receive) > > ToDo: > Investigation to see if full flow control will improve performance > Try enabling TCP over nfs > Make sure that the xfersize does not serously affect the few > machines we have on GigE that mount from the filer > > Thanks to the following for all the help and email (hope I didn't forget > anyone). > > Philip Meidell > John F. Detke > Paul Jones > Neil Stichbury > Mike Ball > Adam Fox > devnull(a)adc.idt.com (whoever your are :-) > > ----------------- Details from some of the responses > > The major known issue is with NFS over UDP and packet drops causing the > UDP cascading error problem. If you are running NFS over UDP I'd strongly > suggest switching to NFS over TCP. > > I believe this is a buffering issue, where the Gig interface is > "overloading" a buffer somewhere on its way to a 100M interface, and > packets gets dropped. When that happens the entire UDP datagram gets > resent. Also check rsize/wsize on the client, it may work better set to > 8k, rather than the (default?) 32KB. > > This problem is related to network hardware, I've seen in most often on > Cisco gear but it happens with others too. A quick nfsstat on client(s) > can show the problem, look for retrans stats. > --------- > We had a similar problem and solved it by changing the UDP transfer size. > Have a look at bug ID 29146 which includes the following :- > > "In Data ONTAP 5.3.4 and earlier releases the default UDP transfer size > is > > 8192. In 5.3.5 and later releases the default is 32768. This larger value > improves performance in some situations, but may cause problems in others. > > Problem 1 - 100-Mbit client is reading from Gigabit interface With the > larger > default, problems may result when the Gigabit interface on the filer is > sending > to a 100-Mbit client. Switches can drop packets on the outbound 100-Mbit > port because too many packets become queued due to the difference in line > speeds > and the larger transfer size. Few complete 32K UDP datagrams are received > by the client, and the client assumes the filer has gone away and > increases its delay between retries. Poor performance may be seen. If a > client does not specify > the rsize and wsize parameters in the mount command, the filer's default > UDP > transfer size is used. If a client does specify rsize and wsize, and the > values are larger than the default, then the default is used. This means > that you > may see problems after you upgrade from 5.3.4 (or earlier release) to > 5.3.5 (or > later release) if the resulting transfer size is 32768. Problem 2 - > Multiple > clients are reading from 100-Mbit interface When the UDP transfer size is > 32768 and multiple clients are reading from a 100-Mbit interface, the > driver > transmit queue on the filer can overflow more readily and packets may be > discarded. > This can lead to erratic or poor performance on the clients." > > --- > First thing to check in GigE is typically flow control settings on the > switch, filer, and client side. Typically it's best to have both > transmit and receive flow control turned on. On the filer, it's > called full flowcontrol. That isn't the default for some switch > vendors and OS NICs. > > It's at least a start. Like most performance issues, you may > have to work several rounds of stuff to find the culprit. Before > you open a case with NTAP, which I strongly suggest, you may need > to quantify your performance in some way. MB/sec is a good one. > By putting a value on your performance it's easier to figure out > what areas could be wrong and also easier to figure out when > you can't get anymore based on your environment. That's the thing > with Gigabit, most clients can't max it out so you will hit a ceiling > for a single client that is less than the capacity of the wire. > Slower forms of Ethernet were easier in this way because you knew > pretty much where the ceiling was. > > --- > > When you're using NFS over UDP with disparate speeds, i.e. gigabit to the > switch, then fast ethernet to clients, you can address performance > problems > in > one of two ways: > > 1) If all of your client machines are on fast ethernet (yep, that means NO > > gigabit clients) the simple approach is to set the filer option > > options nfs.udp.xfersize 8192 > > If you do have gigabit clients, doing the above will impact performance to > them, > in which case you have to do the more management intensive step two... > > 2) If you have some gigabit client machines, add the following options to > the > mount command on each 100 Mbit client machine: > wsize=8192,rsize=8192 > > >

1 0

RE: getting MRTG stats
by Manny Ortega 04 Oct '02

04 Oct '02

http://redhook.univ-wea.com/mrtg/ The name of my filer is pike... The only thing I've changed is the snmp password, everything else (mistakes, comments, et al) is unchanged... Hope this helps... -MannyO #------------------------------------------------------ ### Interface CPU for pike Utilization --MannyO Target[cpu]: 1.3.6.1.4.1.789.1.2.1.3.0&1.3.6.1.4.1.789.1.2.1.3.0:SMNP_PWD@12.31.213.6 RouterUptime[cpu]: public(a)12.31.213.6 MaxBytes[cpu]: 100 Title[cpu]: Pike Cpu utilization PageTop[cpu]: <H1>Pike Cpu utilization</H1> <TABLE> <TR><TD>System:</TD> <TD>pike.univ-wea.com in Universal Weather & Aviation - 8787 Tallyho - Houston, TX</TD></TR> <TR><TD>Maintainer:</TD> <TD>Steve Johnston - <A HREF="mailto:stevej@univ-wea.com">stevej(a)univ-wea.com</a> - 713.944.1622 x3650</TD></TR> </TABLE> ShortLegend[cpu]: % YLegend[cpu]: CPU Utilization Legend1[cpu]: CPU Utilization in % (Load) Legend2[cpu]: Legend3[cpu]:. Legend4[cpu]:. LegendI[cpu]:  Load:  LegendO[cpu]: Options[cpu]: gauge, integer, nopercent #--------------------------------------------------------------- ##### Pike CIFS Sessions Target[pikecifssessions]: .1.3.6.1.4.1.789.1.7.2.12.0&.1.3.6.1.4.1.789.1.7.2.12.0:SMNP_PWD@12.31.213.6 RouterUptime[pikecifssessions]: public(a)12.31.213.6 MaxBytes[pikecifssessions]: 9999999 Title[pikecifssessions]: Pike CIFS sessions PageTop[pikecifssessions]: <H1>Pike CIFS sessions</H1> <TABLE> <TR><TD>System:</TD><TD>Pike CIFS sessions</TD></TR> <TR><TD>Maintainer:</TD><TD>Manny Ortega</TD></TR> <TR><TD>Pike CIFS sessions</TD><TD>1.3.6.1.4.1.789.1.7.2.12.0</TD></TR> </TABLE> ShortLegend[pikecifssessions]: users #WithPeak[pikecifssessions]: ym YLegend[pikecifssessions]: # Sessions Legend1[pikecifssessions]: Number of users Legend2[pikecifssessions]: Legend3[pikecifssessions]:. Legend4[pikecifssessions]:. LegendI[pikecifssessions]:  Sessions:  LegendO[pikecifssessions]: Options[pikecifssessions]: gauge, nopercent, integer #### Pike c$ current usage Target[pikec$]: .1.3.6.1.4.1.789.1.5.4.1.3.3&.1.3.6.1.4.1.789.1.5.4.1.4.3:SMNP_PWD@12.31.213 .6 RouterUptime[pikec$]: public(a)12.31.213.6 MaxBytes[pikec$]: 28183960 Title[pikec$]: Pike c$ current usage Vol0 PageTop[pikec$]: <H1>Pike c$ current usage Vol0</H1> <TABLE> <TR><TD>System:</TD><TD>Pike c$ current usage Vol0</TD></TR> <TR><TD>Maintainer:</TD><TD>Manny Ortega</TD></TR> <TR><TD>Pike c$ kbytes total:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.3.3</TD></TR> <TR><TD>Pike c$ kbytes used:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.4.3</TD></TR> </TABLE> ShortLegend[pikec$]: B #WithPeak[pikec$]: dwmy kMG[pikec$]: k,M,G,T,P kilo[pikec$]: 1024 Unscaled[pikec$]: dwmy YLegend[pikec$]: Disk Utilization Legend1[pikec$]: Volume size Legend2[pikec$]: Volume usage Legend3[pikec$]: . Legend4[pikec$]: . LegendI[pikec$]: Max size:  LegendO[pikec$]: usage:  Options[pikec$]: gauge # ThreshMinI[pikec$]: $THRESHOLDMIN # ThreshMaxI[pikec$]: 21137970 # ThreshProgI[pikec$]: c$.bat # ThreshProgOKI[pikec$]: BATCHLOCthreshold_oki.bat # ThreshMinO[pikec$]: $THRESHOLDMIN ThreshMaxO[pikec$]: 21137970 ThreshProgO[pikec$]: c$.bat #ThreshProgOKO[pikec$]: c$ok.bat # 75% 21137970 #### Pike User_Data current usage Target[pike.user.data]: .1.3.6.1.4.1.789.1.5.4.1.3.1&.1.3.6.1.4.1.789.1.5.4.1.4.1:SMNP_PWD@12.31.213 .6 RouterUptime[pike.user.data]: public(a)12.31.213.6 MaxBytes[pike.user.data]: 175366844 Title[pike.user.data]: Pike User_Data current usage PageTop[pike.user.data]: <H1>Pike User_Data current usage</H1> <TABLE> <TR><TD>System:</TD><TD>Pike User_Data current usage</TD></TR> <TR><TD>Maintainer:</TD><TD>Manny Ortega</TD></TR> <TR><TD>Pike User_Data kbytes total:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.3.1</TD></TR> <TR><TD>Pike User_Data kbytes used:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.4.1</TD></TR> </TABLE> ShortLegend[pike.user.data]: B #WithPeak[pike.user.data]: dwmy kMG[pike.user.data]: k,M,G,T,P kilo[pike.user.data]: 1024 Unscaled[pike.user.data]: dwmy YLegend[pike.user.data]: Disk Utilization Legend1[pike.user.data]: Volume size Legend2[pike.user.data]: Volume usage Legend3[pike.user.data]:. Legend4[pike.user.data]:. LegendI[pike.user.data]: Total size:  LegendO[pike.user.data]: usage:  Options[pike.user.data]: gauge # ThreshMinI[pike.user.data]: $THRESHOLDMIN # ThreshMaxI[pike.user.data]: 21137970 # ThreshProgI[pike.user.data]: c$.bat # ThreshProgOKI[pike.user.data]: BATCHLOCthreshold_oki.bat # ThreshMinO[pike.user.data]: $THRESHOLDMIN ThreshMaxO[pike.user.data]: 131525133 ThreshProgO[pike.user.data]: usrdta.bat #ThreshProgOKO[pike.user.data]: usrdtaok.bat # 75% 131525133 #### Pike Homes current usage Target[pike.homes]: .1.3.6.1.4.1.789.1.5.4.1.3.5&.1.3.6.1.4.1.789.1.5.4.1.4.5:SMNP_PWD@12.31.213 .6 RouterUptime[pike.homes]: public(a)12.31.213.6 MaxBytes[pike.homes]: 75157220 Title[pike.homes]: Pike Homes current usage PageTop[pike.homes]: <H1>Pike Homes current usage</H1> <TABLE> <TR><TD>System:</TD><TD>Pike Homes current usage</TD></TR> <TR><TD>Maintainer:</TD><TD>Manny Ortega</TD></TR> <TR><TD>Pike Homes kbytes total:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.3.5</TD></TR> <TR><TD>Pike Homes kbytes used:</TD><TD>1.3.6.1.4.1.789.1.5.4.1.4.5</TD></TR> </TABLE> ShortLegend[pike.homes]: B #WithPeak[pike.homes]: dwmy kMG[pike.homes]: k,M,G,T,P kilo[pike.homes]: 1024 Unscaled[pike.homes]: dwmy YLegend[pike.homes]: Disk Utilization Legend1[pike.homes]: Volume size Legend2[pike.homes]: Volume usage Legend3[pike.homes]:. Legend4[pike.homes]:. LegendI[pike.homes]: Total size:  LegendO[pike.homes]: usage:  Options[pike.homes]: gauge #ThreshMinI[pike.homes]: $THRESHOLDMIN #ThreshMaxI[pike.homes]: 21137970 #ThreshProgI[pike.homes]: c$.bat #ThreshProgOKI[pike.homes]: BATCHLOCthreshold_oki.bat #ThreshMinO[pike.homes]: $THRESHOLDMIN #ThreshMaxO[pike.homes]: 131525133 #ThreshProgO[pike.homes]: usrdta.bat #ThreshProgOKO[pike.homes]: usrdtaok.bat # 75% 56367915 -----Original Message----- From: Daniel Finn [mailto:DFinn@studentadvantage.com] Sent: Friday, October 04, 2002 4:30 PM To: 'toasters(a)mathworks.com' Subject: getting MRTG stats Could someone send me sample config files for getting mrtg stats from my netapp F760s and F740. Thanks Dan

1 0

getting MRTG stats
by Daniel Finn 04 Oct '02

04 Oct '02

Could someone send me sample config files for getting mrtg stats from my netapp F760s and F740. Thanks Dan

1 0

RE: ndmpcopy question
by Francett, Robert D (SAIC) 04 Oct '02

04 Oct '02

If nothing's changed, I believe it is: email to: majordomo(a)mathworks.com subject: unsubscribe toasters -----Original Message----- From: Dawn Lovell [mailto:dlovell@centurytel.net] Sent: Friday, October 04, 2002 10:30 AM To: Premanshu Jain Cc: toasters(a)mathworks.com Subject: Re: ndmpcopy question I encountered this same message when doing an incremental while migrating to a new filer. The NetApp support person with whom I spoke contacted one of the developers about it. The developer said that the error means that a directory being restored (to the target of the ndmpcopy) referred to an inode which wasn't in the dumpmap. The process assumes that the directory is correct and that the dumpmap is wrong, so it goes with the directory data instead of the dumpmap. I'm not clear on how that works if the affected file is not in the dump (how is it restored to the target machine?), but I'm undoubtedly missing part of the picture. :-) He mentioned that the message might be changed to only appear in debug output, since it should not signal anything that would cause data loss. I had started over with a new level 0 and was on a new incremental by the time I found out that info, so I can't comment as to whether the affected files were actually copied by the incremental that generated the message. Dawn Lovell dlovell(a)centurytel.net On Thu, 3 Oct 2002, Premanshu Jain wrote: > While doing level 1 ndmpcopy, i encounter the following error message in the > log: > > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819691. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819692. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819693. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819694. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > 1819695. > nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on inode > > WHAT DOES THIS MEAN ? > >

1 0

the list
by Paul J. Bell 04 Oct '02

04 Oct '02

my apologies for addressing this to the list. i have attempted, on several occasions, to remove myself from this list, in the approved fashion, all to no avail. on sunday, we will drop the domain of which my current e-mail address is a part, and consequently, all mail to me at that address will be returned to sender. what i have been trying to do is to unsubscribe so that i might re-subscribe under the new address. sounds simple, right. if anyone knows how i can accomplish this i would be most appreciative if you would share such knowledge with me. -paul

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 October 2002