toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

RE: Solaris 7 & NFS2/NFS3/TCP/UDP....
by Rainchik, Aleksandr (MED, Non GE) 08 May '00

08 May '00

Thank you, That really helped (boosted TPS from 38 to 83 :). Is this option documented or not? I can't find it in the manual... P.S. Still a big problem with NFS2 performance. We have (besides of Solaris) lots of IRIX boxes, and (surprise) if you use automount on IRIX all mounts are NFS2 only... -----Original Message----- From: Keith Brown [mailto:keith@netapp.com] Sent: Wednesday, March 22, 2000 4:23 PM To: Rainchik, Aleksandr (MED, Non GE) Subject: Re: Solaris 7 & NFS2/NFS3/TCP/UDP.... > b) There is no way to use w/rsize=32768 with > NetApp with NFS3 over UDP. Why? I can do it > when mounting from Solaris. Did you set the nfs.udp.xfersize set to 32768? Like so.... filer> options nfs.udp.xfersize 32768 Keith

5 5

RE: autosupport retries (was Re: Apology and Request)
by Hackworth, Brian 08 May '00

08 May '00

: From: dnb(a)ccs.neu.edu [mailto:dnb@ccs.neu.edu] : Quick question: once upon a time, machine-gone-kablooey autosupport : mail was only sent when a filer booted. It was the Yoda scenario : ("there is no retry, only do!"). If something went awry in that : sending, the message was just dropped on the floor, no queuing, no : retrying. Beginning in ONTAP 5.3.4, autosupport that can't be sent is queued and retried periodically, with messages written to /etc/messages describing what's going on. The autosupport mail eventually gets dropped if the net or NIS (or whatever) situation isn't fixed, and it's dropped if the filer reboots before the mail goes out, but when the filer eventually comes up, we can patch together much of what happened from the message log. The retry window is 15 minutes in 5.3.4, lengthened to an hour in the "next major release". - Brian -- Brian Hackworth hackwort(a)netapp.com Network Appliance 408.822.6654 Sunnyvale, CA USA

3 2

RE: 18GB drive performance versus 36BG
by Mohler, Jeff 08 May '00

08 May '00

The new 9G drive is a 10K RPM drive from the same family as the Hi-Po 18 and 36G drive, and can only be used in the new FC9 storage shelves. ONTAP, firmware, and head/model limitaion apply. See now.netapp.com or your salesdude for more info. -----Original Message----- From: Brian Tao [mailto:taob@risc.org] Sent: Friday, May 05, 2000 12:10 AM To: Mohler, Jeff Cc: toasters(a)mathworks.com Subject: RE: 18GB drive performance versus 36BG On Thu, 4 May 2000, Mohler, Jeff wrote: > > There is also a new high-performance (spindle rate/seek rate) 9G > drive now as well for those special environments. Which drive is this? -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

1 0

Budtool
by Jay Orr 08 May '00

08 May '00

Humm.. I was visiting PDC's web site to see if there was any new info about the migration of Budtool (will be EOL'd Jan 2001), and noticed the one year mark for the beginning of their migration program has passed : http://www.pdc.com/BTMigration.html Still am unable to find out anything - has anyone else? Wondering if they're ignoring everyone or just us... ----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO

2 2

Error from filer; bad RAM?
by Jamie Lawrence 06 May '00

06 May '00

Hi - Once again, Netapp tech support seems to be taking their sweet time about responding to my support email, so I'm going to folks that actually respond... Got this in the logs of one of my 720s. Is this telling me I've got bad RAM? It hasn't recurred since that date, but still worries me. Sun Apr 30 12:01:28 PDT [de1]: 11 CORR SYS ERR 201 eia:6cfce0058930000 fs:1ee0015 eis:0 isr:80000001 Sun Apr 30 12:01:28 PDT [de1]: ...SYS ECC error: address=0x6cfce00, bit=19, DIMM=J28 Sun Apr 30 12:02:43 PDT [de3]: 12 CORR SYS ERR 201 eia:3ced0058930000 fs:1ee0015 eis:0 isr:80000001 Sun Apr 30 12:02:43 PDT [de3]: ...SYS ECC error: address=0x3ced00, bit=19, DIMM=J28 Sun Apr 30 12:02:50 PDT [de3]: 13 CORR SYS ERR 201 eia:47634058930000 fs:1ee0015 eis:0 isr:80000001 Sun Apr 30 12:02:50 PDT [de3]: ...SYS ECC error: address=0x476340, bit=19, DIMM=J28 Sun Apr 30 12:03:09 PDT [de2]: 14 CORR SYS ERR 201 eia:6cfce0058930000 fs:1ee0015 eis:0 isr:80000001 Sun Apr 30 12:03:09 PDT [de2]: ...SYS ECC error: address=0x6cfce00, bit=19, DIMM=J28 Sun Apr 30 12:03:37 PDT [de3]: 15 CORR SYS ERR 201 eia:6cfce0058930000 fs:1ee0015 eis:0 isr:80000001 Sun Apr 30 12:03:37 PDT [de3]: ...SYS ECC error: address=0x6cfce00, bit=19, DIMM=J28 -j

2 1

Re: raid failure
by G D Geen 06 May '00

06 May '00

I have lived through this harrowing experience. Yes there were warning signs but as I was busy performing other tasks I did not see them. The moral of my story is to read your weekly message logs and have good back ups. I also file every weekly autosupport message. I have message logs from everyone of my filers, we currently have twenty-one, dating back to 1996 when I started this position. It began with a phone call in the middle of the night. On the other end was a co-worker confused as to why the filer was no longer serving data. She had made the determination that there was a failed disk, but little did she know what the next fifteen hours would bring. The reported disk failure was being reconstructed but would never complete. That is when I got the phone call. By this time it was just after 10:00 PM and I rushed into work. I immediately got the run down on the problem she was seeing and what actions were taken. From that point I made a few stabs at getting the RAID to reconstruct. My attempts also failed, now we had to call NetApp support. I made the priority one call and was soon contacted by a NetApp engineer. After a couple of hours poking around on the filer, we were able to determine the sequence of events leading up to the nights exercises in futility. Approximately two weeks prior, the filer had reported in the messages logs that a disk in RAID group zero on volume zero, the root volume, had an unrecoverable read error but did not fail the disk. This night, now closer to morning, the system failed a different disk in RAID group zero on volume zero. See the connection? The net result was the filer could not reconstruct the data because of the unrecoverable read error on the earlier disk. The filer could not make any sense of the data coming off the corrupted sector of the disk. By this time our local support people were awaken by the central support team and had joined us. We were starting to draw a crowd. It was closing in on 2:00 AM when we tried to reconstruct the disk with the bad read sector manually but after a couple of failed attempts even the NetApp engineer was beginning to sound depressed. Then came the question. The one that all data managers hate to hear. How good are your backups? To this question I replied, "we are about to find out." Since our root volume failed, the first step was to make a new root volume. I made /vol/vol1 our new root volume. Next we destroyed /vol/vol0 and removed all the troubled disk drives. Since all of these disks are now spares, we may create a new RAID group and a new /vol/vol0. Here it is important to note that there must be a /etc on the volume *before* Veritas can begin its data restore. Once the volume was recreated, we began our restore of approximately 150 Gigabytes of data which took us well into the morning. The NetApp engineer in California and I had a long conversation over the phone while the data restores were beginning. He was certain that there should have been some sort of sign that this was about to happen. I assured him that I would look and would forward my results to our local support people, who are copied on the autosupport messages too. As I went back through the autosupport logs that are e-mailed to me each week, I found that the problem began approximately two weeks earlier. Every time a the disk tried to read a particular sector of the disk, an error messages would appear the messages log indicating such an event had occurred. Had I not been busily working other issues, to the detriment of my filers, I would have failed this disk at lease a week prior. -gdg Mark D Fowle wrote: > I have heard a few horror stories lately about netapps and multi-disk raid > failures. Has anyone out there experienced this > and what did you do for recovery ? Where there any warnings? I have not had > this happen and would like to do as much > as possible to prevent it. > > Thanks, > =============================================================================== > ======= > Mark Fowle > Caterpillar/BCP > Cary North Carolina > =============================================================================== > ======= -- --------------------------------------------------------------- G D Geen mailto:geen@ti.com Texas Instruments Phone : (214)480.7896 System Administrator FAX : (214)480.7676 --------------------------------------------------------------- Life is what happens while you're busy making other plans. -J. Lennon

7 7

Re: raid failure
by Richard L. Rhodes 06 May '00

06 May '00

On 3 May 2000, at 18:29, owner-toasters(a)mathworks.com wrote: > Unfortunately, this only works if we get the autosupport in the first > place. Apparently there are a number of customers who think we don't > want to be bothered. We do! If your filer or NetCache doesn't list > 'autosupport(a)netapp.com' in the 'autosupport.to' option, please add > it if your policies allow this. > I'm a new netapp customer (less than a year). I've found autosupport a little frustrating. For myself, the problem is the lack of feedback. I set up autosupport to send messages to several internal addresses and NetApp. I get the email just fine, but I have no way of knowing if NetApp got the email. I'd use the "options autosupport.doit just testing" command to send a test. I'd get the email, but I had no way to know if NetApp got the email. I almost called support to ask if anyone could tell me whether they got the emails! I'd like to see several things: 1) an auto reply message sent back from NetApp acknowledging that they got the autosupport email. 2) If you run it through some tool for analysis, I'd like to have the output emailed back to me. Here's another example. Since upgrading DataOntap, the autosupport email says that my gigabit ethernet cards are in the wrong slots. These cards are in the slots that the factory put them in. NetApp support has said nothing and the filers are working fine - so I've done nothing. Am I wrong? Rick

4 3

Raid groups
by Sateesh Mucharla 06 May '00

06 May '00

I am buying a F760 with 35 drives (all 36GB). As there is limitation of 28 drives per raid group ( i read it NetApp Sysadmin manual), i am thinking of having two raid groups one with 26 and the other with 7 drives. Rest two will be hot spares. But i am open for better configuration. I would like to know whether i can configure all 33 drives into one raid group - Is that possible? If so what are the disadvantages. (With 33 drives in one raid group, i loose only one drive as a parity drive - this is an advantage). Can somebody suggest a better configuration ? Thanks Sateesh Mucharla National Semiconductors

3 2

autosupport RE: Apology and Request (was Re: raid failure)
by Klinkner, Steve 05 May '00

05 May '00

> -----Original Message----- > From: dnb(a)ccs.neu.edu [mailto:dnb@ccs.neu.edu] > Dave Hitz <hitz(a)netapp.com> writes: > > > I also have a request. Please turn on autosupport. That's > > extremely important to us for two reasons: > > Quick question: once upon a time, machine-gone-kablooey autosupport > mail was only sent when a filer booted. It was the Yoda scenario > ("there is no retry, only do!"). If something went awry in that > sending, the message was just dropped on the floor, no queuing, no > retrying. > > We had a situation where our filer bounced twice, but on the first > return to service it didn't have good net (or NIS, or name resolution, > can't recall which). This meant that the first "here's the problem" > mail never got to the mothership, but the "just booted, everything is > peachy" mail did. Does the crash autosupport facility do anything more > sophisticated these days? (he asks, because his filer hasn't > crashed in > many moons...). ONTAP 5.3.4 got a change which has autosupport retry delivery for about 15 minutes. This should help with transient failures such as the mailhost rebooting, temporary loss of DNS, et cetera. In the "next major release" the retry interval has been boosted to an hour. In addition, autosupport will wait until boot is fully complete before trying to do *anything*. This will prevent autosupport from issuing silly syslog messages saying it can't deliver mail because the network isn't up (prior to 5.3.4, that behavior could cause loss of a message, in 5.3.4 it is annoying/silly, and in the "next major release" it will go away completely). ---------------------------------------------------------------------- steve klinkner klink(a)netapp.com

1 0

Re: Apology and Request (was Re: raid failure)
by dnb＠ccs.neu.edu 05 May '00

05 May '00

Cool, that's great to hear. Thanks for the response. Respectfully, David N. Blank-Edelman Director of Technology College of Computer Science Northeastern University John Denholm <johnd(a)ThePLAnet.net> writes: > Yeah, that's better now. We used to get that a lot - part of the > problem can be the interaction of Cisco switches and Netapps - the > Cisco can take a short while to figure out that the link is back up > to a Netapp and the mail falls on the floor while waiting for that. > > Some time ago, presumably at the insistence of ourselves and others, > Netapp inserted a 30 second wait and retry loop into bootup, and now > I think it gives autosupport 4 or 5 tries over a couple of minutes. > We always get autosupport off them now. Not that, I admit, we've > had a crash message in a while, but we never used to get them on > reboots either :< > > As for dealing with network or DNS or whatever not coming back, one thing you > can do is specify your mailhost wholely by IP - while fractionally more work to > maintain if the boxes on your network change frequently, it requires a little > less to go right. > > If you are worried about missing a crash, use snmp monitoring and grab > system.sysUptime.0, which is the uptime in hundredths of seconds. I run a > large number of netapps of different breeds, and I just run a perl script which > grabs the uptime off every one every 10 minutes. Any crashes are immediately > apparent. It could also write to file and compare current uptime to previous > uptime - if uptime drops, it can sms you, mail you, sound sires, flash lights, > whatever :> > > > Now I just wish they'd get it right with the caches. They still only try > mailing autosupport once :p > > J > > --------------------------------------------------------------------------- > # John Denholm johnd(a)theplanet.net # > # Webcache & Filer Administrator, Planet Online +44 113 207 6357 # > --------------------------------------------------------------------------- > > Error 404: There is no spoon

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters