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)? My thought would be that perhaps zpool import is confused seeing the same zpool information on all three devices, but I concede this is a relatively uneducated guess. -- Sean -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, July 13, 2007 4:11 PM To: Manoj Joseph Cc: [EMAIL PROTECTED]; zfs-discuss@opensolaris.org Subject: Re: [zfs-discuss] ZFS and powerpath [EMAIL PROTECTED] wrote on 07/13/2007 02:21:52 PM: > Peter Tribble wrote: > > > I've not got that far. During an import, ZFS just pokes around - > > there doesn't seem to be an explicit way to tell it which particular > > devices or SAN paths to use. > > You can't tell it which devices to use in a straightforward manner. > But you can tell it which directories to scan. > > zpool import [-d dir] > > By default, it scans /dev/dsk. > > Does truss of zfs import show the powerrpath devices being opened and > read from? AFAIK powerpath does not really need to use the powerpath pseudo devices -- they are just there for convenience. I would expect the drives to be readable from either the c1xxxxxxxx devices or emc*. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
