MadDog@fool.com (Tom "Mad Dog" Yergeau) writes:
Spinning up and down isn't the issue.
According to the warning displayed when you do a disk_fw_update, even upgrading a single disk,
"It involves... suspending all disk I/O to all disks while that is happening"
SUSPENDING ALL DISK I/O TO **ALL** (not ONE) DISKS.
That's a problem in my environment.
So I guess the question is, is the notice wrong and when you're only doing a disk_fw_update on a single disk that's allocated as a spare, it doesn't suspend I/O to ALL disks?
The last time I did this (last June, 5.3.5 => 5.3.6, FDF6 => NA26 on ST39102FC disks, on an F740) then there was definitely a period of non-responsiveness of the filer, even if only a single (and spare) disk was being updated, long enough to make NFS clients start logging "NFS server so-and-so not responding".
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.