I'm running a RHEL 5.5 with multipath@HSV200 storage system.

The disk performance for write is VERY poor comparing to Windows-system counterparts (which are using the same storage and multipath).

Here are the results:

```
mpath17 (3600508b400105f9d0002100000780000) dm-12 HP,HSV200
[size=850G][features=0][hwhandler=0][rw]
\_ round-robin 0 [prio=100][active]
 \_ 2:0:1:30  sdaw       67:0   [active][ready]
 \_ 1:0:1:30  sdc        8:32   [active][ready]
\_ round-robin 0 [prio=20][enabled]
 \_ 2:0:0:30  sdau       66:224 [active][ready]
 \_ 1:0:0:30  sda        8:0    [active][ready]

`atop` result:

LVM |      mpath17  | busy     99% |  read    3077 | write      6  | KiB/r     90 |               | KiB/w      4 |  MBr/s  27.11 | MBw/s   0.00  | avq     2.41 |  avio 3.21 ms 

```

Note how the "busy" is 99% - and this happens most of the time.

The multipath.conf is using the recommended HP best-practices for this storage:

```
device {
                vendor                                   "HP"
                product                                  "HSV2[01]0|HSV3[046]0|HSV4[05]0"
                path_grouping_policy        group_by_prio
                getuid_callout                      "/sbin/scsi_id -g -u -s /block/%n"
                prio_callout                           "/sbin/mpath_prio_alua /dev/%n"
                path_selector                       "round-robin 0"
                path_checker                       tur
                hardware_handler              "0"
                failback                  immediate
                rr_weight                               uniform
                rr_min_io                              100
                no_path_retry                       18
}

```

Is there any way to diagnose this event?
I want to understand where's the bottleneck in this scenario...
Any suggestions where to start?

(This is my first post here, thank you very much)