toasters

toasters@lists.teaparty.net

13531 discussions

Root permissions failing.
by Chris Josephes 08 Oct '02

08 Oct '02

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 1

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

ndmpcopy question
by Premanshu Jain 04 Oct '02

04 Oct '02

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 ?

2 1

quota
by Lance R Bailey 04 Oct '02

04 Oct '02

hi, we hava a user who wants to know their user quota. the quota is set up with: * user@/vol/vol1/home 7G but they don't know it's 7G, and it's different from project to project, from home disk to home disk. if i cd into their home dir, and do a df, i see the tree quota not the user quota now, they could remsh into the filer, do a quota report and grep for their name, but we don't let users remsh into the filer :) are there any tools or approaches for this? -- email: lance_bailey(a)pmc-sierra.com box: Lance R. Bailey, unix Administrator vox: +1 604 415 6646 PMC-Sierra, Inc fax: +1 604 415 6151 105-8555 Baxter Place http://www.lydia.org/~zaphod Burnaby BC, V5A 4V7

3 4

Re: Finding who has files open (in use)
by Seth Moskowitz 04 Oct '02

04 Oct '02

I have used a product called Whohasnt.exe which has workied quite well. >From: "Maglinger, Paul" <PMAGLINGER(a)scvl.com> >To: "'NetApps list server'" <toasters(a)mathworks.com> >Subject: Finding who has files open (in use) >Date: Thu, 26 Sep 2002 15:24:02 -0500 > >Greetings toasters! > >Looking for a way to list files that are in use on the filer and who is >using them. I want an output similiar to what you would see if you went >into Windows Server Manager, selected the server and clicked on the "In >Use" >button, but I want something more user friendly than scrolling down looking >for the file name. Specifically, we are having problems with users leaving >files open, which prevents us from writing over them. I'm looking for a >way >to quickly track down who has this file open so they can be flogged, >keel-hauled, then drawn and quartered. Your thoughts, please? > >Remember, you are unique... just like everyone else! > > > >Paul Maglinger, A+, CA, CCA, CET, MCSE >Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx

2 1

Re: can't login at 6.2.1R1 ...
by Paul Caron 04 Oct '02

04 Oct '02

Are the hosts listed in your filer's /etc/hosts.equiv file and/or /etc/trusted.hosts file fully qualified? You might be experiencing a host name lookup failure. You could try just specifying IP addresses for the admin hosts as a temporary fix.

3 2

MRTG stats after upgrading to 6.2.1r1
by Clawson, Simon 04 Oct '02

04 Oct '02

Hi, We just noticed that after upgrading to the new GA our CPU usage as reported in MRTG jumped up quite a bit. We previously maxed out the CPU (well 91%) for a very short time previously, last night however the max out period lasted for a couple of hours..anyone else notice similar behaviour? I will keep a close eye on it.. Simon Simon Clawson TEL:- +44 (0)1635 811409 HDL Designer Series Team Systems Administrator FAX:- +44 (0)1635 810108 Mentor Graphics Ireland Ltd (UK Branch) MOB:- +44 (0)7788 716071 Rivergate London Road Newbury Berkshire RG14 2QB

1 0

RE: upgrading the ONTAP version
by Clawson, Simon 04 Oct '02

04 Oct '02

I upgraded last night, and see this message now. Any news from NetApp? Simon -----Original Message----- From: Paul Caron [mailto:caron@sig.com] Sent: 03 October 2002 17:10 To: DFinn(a)studentadvantage.com Cc: toasters(a)mathworks.com Subject: Re: upgrading the ONTAP version We were in a similar situation with a clustered pair of F740 filers running ONTAP 5.3.4R2. They are now running ONTAP 6.2.1D11. The steps I always follow are: 1) Upgrade filer firmware to latest rev. 2) Upgrade ONTAP version 3) Upgrade disk firmware to latest rev. Note that the disk firmware upgrades MAY have to come before the ONTAP version upgrade. There are a few field alerts about the types of disks that fall into this category on the NOW site. Also, the newer versions of ONTAP will handle the disk firmware upgrade automagically, unless you have clustered filers. The install is not very difficult. The best approach is to just follow the upgrade steps posted on the NOW site. So far, they have always been accurate. There is a set of upgrade steps posted with each version of ONTAP. Also, I have never had a problem with license carry-over. I believe that the latest system board firmware rev. you want is 2.8_a2 (also posted on the NOW site). The only weirdness I've seen since the upgrade is the following CIFS audit messages: [toaster: registry_control:notice]: Restarting CIFS auditing with new buffer size. [toaster: registry_control:warning]: option cifs.audit.membufsize: Value (4096) is out of range (10240 to 262144), using 65536 instead. I'm still trying to figure out what's causing this. The cifs.audit.membufsize option is actually set to 65536 on both of the filers. Also, I've turned CIFS auditing off. However, it mysteriously turns itself back on every hour. Strange, but it hasn't caused any problems that I've found yet. >From: Daniel Finn <DFinn(a)studentadvantage.com> >To: "'toasters(a)mathworks.com'" <toasters(a)mathworks.com> >Subject: upgrading the ONTAP version >Date: Thu, 3 Oct 2002 09:29:05 -0400 >MIME-Version: 1.0 > >we have a F740 running an older version of ONTAP, version 5.3.5R2. The rest >of our netapps run 6.1.3. What would I need to do in order to bring this >netapp up to date? I think I can get my hands on the floppy disks. How >hard is the install? Do all the licenses carry over? Also, the firmware >release below, 2.3._a2, can/should that be upgraded also? > > > NetApp Release 5.3.5R2: Tue Mar 28 15:48:22 PST 2000 > System ID: 0016791464 (na4m-be) > slot 0: System Board (NetApp System Board V N0) > Model Name: F740 > Serial Number: 221290 > Firmware release: 2.3_a2 > Memory Size: 512 MB > >Thanks >Dan

1 0

RE: ndmpcopy question
by Chitre, Amol 04 Oct '02

04 Oct '02

Hi Premanshu, Seems to me that the /etc/tmp directory on the filer were changed manually. Could you confirm that for me please? Dump/Restore create some temporary files and leave them in /etc/tmp. When a dump/restore is running, it actively refers to those files. If the files are deleted or resized from underneath it, the reference to the files will become stale. Which results in the error you are seeing. Hope that helps, Amol. *-----Original Message----- *From: Premanshu Jain [mailto:Premanshu.Jain@synopsys.com] *Sent: Thursday, October 03, 2002 12:35 PM *To: toasters(a)mathworks.com *Subject: ndmpcopy question * * *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

upgrading the ONTAP version
by Daniel Finn 03 Oct '02

03 Oct '02

we have a F740 running an older version of ONTAP, version 5.3.5R2. The rest of our netapps run 6.1.3. What would I need to do in order to bring this netapp up to date? I think I can get my hands on the floppy disks. How hard is the install? Do all the licenses carry over? Also, the firmware release below, 2.3._a2, can/should that be upgraded also? NetApp Release 5.3.5R2: Tue Mar 28 15:48:22 PST 2000 System ID: 0016791464 (na4m-be) slot 0: System Board (NetApp System Board V N0) Model Name: F740 Serial Number: 221290 Firmware release: 2.3_a2 Memory Size: 512 MB Thanks Dan

2 1

Restoring NetApp dumps with Solaris ufsrestore
by Chris Thompson 03 Oct '02

03 Oct '02

Following some very nasty experiences with Veritas (vxvm & vxfs) on one of our systems, we are currently in paranoia mode about our ability to restore from backups, and have been doing more than usually extensive tests. I have come across a serious problem with ONTAP restore, but I am in communication with NetApp about that and it's not the subject of this message. Maybe later on ... :-) NetApp have said on a number of occasions that it's a design feature of their dump format that it is a compatible extension of good old BSD dump format, so that if all else fails one can feed them to a BSD-type restore program (losing ACLs and such-like info, of course). Solaris "ufsrestore" is usually explicitly or implicitly mentioned. So I have been testing that, and have fallen over a problem that I knew about (at least since May 2000, as I see I mentioned it in passing on toasters then) but have been ignoring. Maybe it's time to do something about it! What happens is that ufsrestore says write error extracting inode NNNNN, name ./path/name/to/file write: Bad address and gives up. One can see that it has half-written the file involved. It seems to happen only on files that have holes (often many of them) at odd multiples of 4K: in our case they are usually *.pag files that are part of (n)dbm databases. Now I very strongly suspect that this is a bug in Solaris ufsrestore, not in the NetApp dump contents, and I would like to be able to report it to Sun and get it fixed. But it seems to be very difficult to reproduce with a small example: it's far from the case that every file with oddly-aligned holes causes a problem, or even that a file with exactly the same hole pattern will provoke the bug if it occurs at a different point in the dump. Even worse, it apparently depends on what sort of filing system ufsrestore is restoring into: I have never had it happen if it is a local ufs filing system, but often if it was an nfs one (usually on a NetApp filer, of course). If all these variables are reproduced, though, the effect is repeatable. It's possible that Sun would reject such a bug report unless one could show that it failed on a dump generated by Solaris ufsdump. Solaris ufs filing systems have always been blocked at 8K by default (so that hole boundaries must be on multiples of 8K). On UltraSPARC (sun4u) systems one can't even mount ones that are blocked at 4K any longer. I tried making a ufsdump of a filing system blocked at 4K on a SPARCstation 5 (sun4m) - sometimes it's useful to have such an out of date machine as one's personal workstation! - with a suitably holey file in it, but I couldn't get the ufsrestore bug to show up... :-( If anyone else has ever come across this problem, and/or has any suggestions on how to proceed with homing in on the bug, I would very much like to hear from them. The latest experiments were done with Solaris 8 ufsrestore as patched by 109091-05, but as I said above I believe the bug has been there for many years. Chris Thompson University of Cambridge Computing Service, Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QH, Phone: +44 1223 334715 United Kingdom.

1 1

Re: UNIX /var/mail on NetApp?
by Paul Caron 03 Oct '02

03 Oct '02

We've been using the following auto_direct entry for mounting /var/mail on Solaris 2.6, Solaris 8, and <cough> SunOS 4.1.3 clients for years without incident: /var/mail -rw,intr,hard,actimeo=0 toaster:/vol/fs0/mail_spool However, we don't use the standard Sun Sendmail configs. either.

1 0

Re: upgrading the ONTAP version
by Paul Caron 03 Oct '02

03 Oct '02

We were in a similar situation with a clustered pair of F740 filers running ONTAP 5.3.4R2. They are now running ONTAP 6.2.1D11. The steps I always follow are: 1) Upgrade filer firmware to latest rev. 2) Upgrade ONTAP version 3) Upgrade disk firmware to latest rev. Note that the disk firmware upgrades MAY have to come before the ONTAP version upgrade. There are a few field alerts about the types of disks that fall into this category on the NOW site. Also, the newer versions of ONTAP will handle the disk firmware upgrade automagically, unless you have clustered filers. The install is not very difficult. The best approach is to just follow the upgrade steps posted on the NOW site. So far, they have always been accurate. There is a set of upgrade steps posted with each version of ONTAP. Also, I have never had a problem with license carry-over. I believe that the latest system board firmware rev. you want is 2.8_a2 (also posted on the NOW site). The only weirdness I've seen since the upgrade is the following CIFS audit messages: [toaster: registry_control:notice]: Restarting CIFS auditing with new buffer size. [toaster: registry_control:warning]: option cifs.audit.membufsize: Value (4096) is out of range (10240 to 262144), using 65536 instead. I'm still trying to figure out what's causing this. The cifs.audit.membufsize option is actually set to 65536 on both of the filers. Also, I've turned CIFS auditing off. However, it mysteriously turns itself back on every hour. Strange, but it hasn't caused any problems that I've found yet. >From: Daniel Finn <DFinn(a)studentadvantage.com> >To: "'toasters(a)mathworks.com'" <toasters(a)mathworks.com> >Subject: upgrading the ONTAP version >Date: Thu, 3 Oct 2002 09:29:05 -0400 >MIME-Version: 1.0 > >we have a F740 running an older version of ONTAP, version 5.3.5R2. The rest >of our netapps run 6.1.3. What would I need to do in order to bring this >netapp up to date? I think I can get my hands on the floppy disks. How >hard is the install? Do all the licenses carry over? Also, the firmware >release below, 2.3._a2, can/should that be upgraded also? > > > NetApp Release 5.3.5R2: Tue Mar 28 15:48:22 PST 2000 > System ID: 0016791464 (na4m-be) > slot 0: System Board (NetApp System Board V N0) > Model Name: F740 > Serial Number: 221290 > Firmware release: 2.3_a2 > Memory Size: 512 MB > >Thanks >Dan

1 0

RE: UNIX /var/mail on NetApp?
by Andrew Richards 01 Oct '02

01 Oct '02

> ...snip... > If you can direct all your mail client accesses through IMAP or POP, > leaving no programs but the delivery agent and the imap/pop daemon > doing direct mailbox accesses, then you get the ability to > relatively painlessly change mailbox formats. That's worthwhile; > Maildir+NetApp is one of the sweetest spots in the whole mail server > design spectrum. Forget locking, forget recovery, everything Just > Works. > When I build a server, even if it's a single box for everything, I > go with maildrop delivering to virtual user Maildirs, with > Courier-IMAP (which offers pop, and the /ssl varients) providing > access for MUAs; this sets me up to grow as big as ever I could > want and never worry about mailbox correctness. I'd like to echo those sentiments: I build mail systems - the Maildir / NetApp combo means that my largest client currently has a system with 1.6 million Maildirs ( = users) and it's still growing nicely. I wrote to highlight qmail - "The original and best" mailserver to use Maildirs. Qmail is a particularly strong mailserver implementation and is very stable - I have some concerns with Courier mentioned by Bennett in that a new version seems to appear frequently. The other nice thing about Maildirs is that because of their (as Bennett says) "everything Just Works" design, you can have multiple machines writing entries (messages) to the same Maildir without their needing to be aware of one another's existence; that really helps systems to scale. More info on qmail at www.qmail.org and cr.yp.to/qmail.html cheers, Andrew.

4 3

can't login at 6.2.1R1 ...
by Frank Bonnet 01 Oct '02

01 Oct '02

Hi Since I've installed the 6.2.1R1 GA release NFS is working well BUT I am unable to login from the console or to perform a telnet/rsh session from authorized hosts . .. I haven't change anything in configuration files. Is there some special things to do to recover the login ability ? The machine is a F85 Thanks a lot. -- Frank Bonnet

1 0

Recital Database
by Matej Moskon 01 Oct '02

01 Oct '02

Is there anybody using Recital Database stored on NetApp? Has anybody tried to move datafiles on Filer yet? We done that, but we have noticed that there have been a huge performace impact from the application point of view, since copying the files under NFS has worked just fine. Any suggestions? Matej

1 0

Jump to page:

2026

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