On 08/11/97 14:37:07 you wrote:
On Mon, 11 Aug 1997, Kenneth Whittaker wrote:
Disk 9a.3 can only mean trouble in the future. I recommend getting disk 9a.3 out of your system, but before you pull a drive, call technical support.
That's odd... as I mentioned, the error appeared on two of our filers, both on the hour immediately following a spare disk replacement. Are you saying the new drives I plugged in both happen to be bad too? I've already got two sitting on my desk to be returned, and I sure hope I don't need two more going back.
I don't understand Ken's response either. He should be well aware that there is a bug on this, where most of the time a disk will report a Unit Attention error on the hourly check after being swapped in... I filed the bug myself a year or two ago.
Bruce
On Mon, 11 Aug 1997 sirbruce@ix.netcom.com wrote:
I don't understand Ken's response either. He should be well aware that there is a bug on this, where most of the time a disk will report a Unit Attention error on the hourly check after being swapped in... I filed the bug myself a year or two ago.
That's a relief! I recently added a new disk shelf full of new disks, and they all generated that message on the hour before I ran the 'raid add' command.
I'm curious about accounting for the disk space on our filer, which has 19 "4gb" data disks.
Naively multiplying 19 disks * 4000 mb/disk * 1024 kb/mb gives 77824000 kb.
Now subtract 10% for the FFS-ish reserve space; that leaves 70041600 kb.
df on the filer shows 69682640 kb for / and /.snapshot combined. That leaves 358960 kb -- what did I overlook? Inode space?
On Mon, 11 Aug 1997, Jim Davis wrote:
That's a relief! I recently added a new disk shelf full of new disks, and they all generated that message on the hour before I ran the 'raid add' command.
Ah, this is good to know. My confidence in Netapp was starting to waver for a moment there... ;-)
-
Brian Tao -
Jim Davis -
sirbruce＠ix.netcom.com