Same thing happened to me 2 days ago on a F740 filer. Last thing on LED was 28 ops/sec. Couldn't get to it whatsoever. Had to reboot by shutting down power supplies. Filer had been up over 320+ days. I called NetApp and they said they could do nothing since there was no core dump. There was only a "bounds" file with "0 0" in it. They told me if it happens next time to call them and do the LED reset for a coredump.
-----Original Message----- From: Maglinger, Paul [mailto:PMAGLINGER@scvl.com] Sent: Friday, August 24, 2001 6:30 AM To: 'Sam Rafter' Cc: 'NetApps list server' Subject: RE: Filer hung up tight
I checked with my boss, who got in before I did and he said that he tried filer view after trying the console. It came back as "Page not found".
-----Original Message----- From: Sam Rafter [mailto:rafter@netapp.com] Sent: Thursday, August 23, 2001 18:49 To: Maglinger, Paul Cc: 'NetApps list server' Subject: Re: Filer hung up tight
You do have one alternative in this situation. There's a synch button on the front of your filer. On the 700 series, it's the little hole under the LEDs. When you press that, the filer should drop to the ok prompt. From there, you can type 'sync'. There's a NOW article on doing just very thing:
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=3.0.620867.2715498&a... esource=
In the 'nothing was working' checklist, was NFS/CIFS and FilerView checked as well? 850 ops is a lot to do nothing at all. If the number never fluctuated, I'd have my suspicions that it wasn't getting updated. We have watchdog systems in place to catch such things, so I'm a bit mystified.
-Sam
* It was Thu, Aug 23, 2001 at 04:26:24PM -0500 when Maglinger, Paul wrote:
We have a 740 filer running 6.0.1R3. Last night I got a page that "nothing was working". I headed into work and found that:
I could not telnet into the filer.
I could not get in through console either.
The display on the front of the filer said 850 ops but the activity
led wasn't flashing at all.
I figured I had no choice, so I shut it down hard and brought it back up. Everything came up fine. The message file posted a time stamp at 11:00pm but nothing at midnight (this was 1:30am). The message file also said that the fiiler was down for 6057 secs. The crash folder had one file in it called "bounds" and just contained "-1 -1". Backups were being performed at the time using Veritas Backup Exec. The backup log said everything was going fine until it found a "corrupted file", then it started skipping files until the filer was rebooted and it started in backing up again. We're trying to figure out what went wrong but didn't have much to go on. Anyone have any thoughts where to look now (or if this happens again)?
"No matter where you go, there you are."
Paul Maglinger
System Administrator
Shoe Carnival, Inc.