> Doesn't that then create dependence on the cxtxdxsx device name to be > available? > > /dev/dsk/c2t500601601020813Ed0s0 = path1 > /dev/dsk/c2t500601681020813Ed0s0 = path2 > /dev/dsk/emcpower0a = pseudo device pointing to both paths. > > So if you've got a zpool on /dev/dsk/c2t500601601020813Ed0s0 and that > path becomes unavailable (perhaps due to device renumber or failure), > won't the zpool be unavailable? Whereas a zpool on /dev/dsk/emcpower0a > will automagically handle the situation (assuming the 2nd path is > available)?
How would the path become unavailable? While it looks like a raw path, it's still being managed by powerpath. So during a boot, it should not suddenly disappear, even if the path goes away. If it were to go away between boots, then I see it as the same situation for a disk being renumbered/repathed on "normal" single-pathed storage. ZFS needs to be able to scan all paths until it finds the disk again. The pool should not be tied to the path. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
