[Jeffrey Scott]
| I'm trying to simulate a drive failure by either powering down a single
| drive or physically removing it from it's enclosure so as not to
| interrupt the scsi bus, however each time I do this and then attempt to
| access my zfs pool the system hangs and i get flooded with errors :
| Jan 23 14:49:13 foo scsi: WARNING: /[EMAIL PROTECTED],0/[EMAIL
PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (sd24):
| Jan 23 14:49:13 foo disk not responding to selection
|
| eventually the system will freeze and i will have to go down to the
| eeprom level and issue a boot command to restart the host.
|
| Is this type of failure something it should be able to handle or am I
| doing something wrong and my expectations are too high here?
|
| Is this an issue with ZFS or more with the host system not being able
| to cope with a device being removed in this fashion.
I've seen similar problems with a T2000. If I create a mirror of the
internal SAS-disks with zpool create mirror foo c0t2d0 c0t3d0 and
physically remove one of those disks, the system will hang completely after
a short while, and I have to break the system from ALOM and reboot. If I do
a zpool offline of the disk first, there are no problems when removing
the disk.
If I create a DiskSuite mirror, or a HW-raid mirror, on the disks instead,
and then create a single-disk zpool on top of this mirror, there are no
problems with the system or ZFS when I physically remove one of the disks in
the mirror.
I opened a support-case with Sun about this, and after a while I received
a test-patch (IDR125057-01) which so far seems to have solved all my
problems with this issue. If you have a support-contract with Sun, you
could probably ask for this test-patch. I've not been told when it will
make it into an official patch.
Regards,
-Anders.
--
Anders Odberg, [EMAIL PROTECTED]
Center for Information Technology Services
University of Oslo, Norway
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
