workaround below...
Richard Elling wrote:
Anton B. Rang wrote:
Is this because C would already have a devid? If I insert an unlabeled
disk, what happens? What if B takes five minutes to spin up? If it
never does?
N.B. You get different error messages from the disk. If a disk is not
ready
then it will return a not ready code and the sd driver will record this and
patiently retry. The reason I know this in some detail is scar #523, which
was inflicted when we realized that some/many/most RAID arrays don't do this.
The difference is that the JBOD disk electronics start very quickly, perhaps
a few seconds after power-on. A RAID array can take several minutes (or more)
to get to a state where it will reply to any request. So, if you do not
perform a full, simultaneous power-on test for your entire (cluster) system,
then you may not hit the problem that the slow storage start makes Solaris
think that the device doesn't exist -- which can be a bad thing for highly
available services. Yes, this is yet another systems engineering problem.
Sorry, it was rude of me not to include the workaround. We put a delay in
the SPARC OBP to slow down the power-on boot time of the servers to match
the attached storage. While this worked, it is butugly. You can do this with
GRUB, too.
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
