154 Posts

January 8th, 2010 06:00

That is correct.  From the perspective of PowerPath, we are managing the device as a whole no matter how it is carved up.

154 Posts

January 7th, 2010 11:00

Hello.  It is not PowerPath that is picking a device and listing g, c, a slices etc.  It is the 'format' utility of the OS that did like that. PowerPath always displays the name with slice 'a' like "Pseudo name=emcpower0a" irrespective of the size of the slice. Even if the 'a' slice has been made to be zero and slice 'g' is equal to the full disk 'c' slice, "powermt display dev=0" will still show the name of the device as "emcpower0a"

It doesn't matter when it comes to the failover functionality. Failover protection is not provided for the individual slices, it is provided rather to the full device (lun) depending on the policy set for the device / storage class.

I can't say why your format utility is picking and giving different slice names. However, this display by format utility has no impact on the functionality.

Thanks.

1 Rookie

 • 

100 Posts

January 7th, 2010 14:00

Thanks Brion. So it does not matter what letter comes after the disk number? I can do either of these;

# newfs /dev/rdsk/emcpower0g or # newfs /dev/rdsk/emcpower0a

and it will still see the same for powerpath? I know I can do that on ...0c and will be able to mount it as such but am still confused about the rest.

Primus emc136049 deals with this issue but does not clarify it further..just says "not our fault.." ..~:)

1 Rookie

 • 

100 Posts

January 11th, 2010 09:00

Thanks Brion!
No Events found!

Top