> - I've got 4 inhouse and a 5th on the way.
>
> > EVA4000 , 6000, 8000 don't need no hardware handler (afaik).
>
> These are all active/active. I don't have any to play with yet -
> probably next year.
That isn't entirely true; although they are active/active, there is still
a preferred LUN for each controller. (see bad ascii art)
SAN FABRIC
| |
| |
Controller1<--Internal bus-->Controller2
|
|
LUN
Read IO to controller1 goes direct to the LUN. Read IOs to controller2
cross an internal bus to controller1, which can limit performance.
However, if IO is going consistently to the non-preffered controller, the
EVA will flip the lun over and make that controller the preffered
controller.
The upshot was we found we got better, more consistent, performance when
we used the group-by-serial rather than multibus path_grouping_policy for
the EVA8000.
Allegedly, there is a way to find out which controller is the preffered
one for each lun, but I don't know what it is.
Cheers,
Guy
--
Dr. Guy Coates, Informatics System Group
The Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1HH, UK
Tel: +44 (0)1223 834244 x 6925
Fax: +44 (0)1223 494919
--
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
