Just migrated some volumes to a 3250 8.1.2 cluster and as expected when the snapmirrors were broken, the 64-bit upgrades began.
How do I tell from the command line the progress and ETA of the 64-bit conversion status?
 I suspect they are causing IO issues -  what is the diagnostic value of the per disk (high) latency reports with ~40% disk util?  (are these bad disks??)

thanks


sysstat -x 1
 CPU    NFS   CIFS   HTTP   Total     Net   kB/s    Disk   kB/s    Tape   kB/s  Cache  Cache    CP  CP  Disk   OTHER    FCP  iSCSI     FCP   kB/s   iSCSI   kB/s
                                       in    out    read  write    read  write    age    hit  time  ty  util                            in    out      in    out
 85%   7570      0      0    7573  271319   2395    9399 211896       0      0    12     97%   55%  Ff   50%       3      0      0       0      0       0      0
 93%   8871      0      0    8871  312456   2810   14858 219002       0      0    12     99%  100%  :f  100%       0      0      0       0      0       0      0
 63%   5527      0      0    5786  185636   1748    7456 276940       0      0    12     99%  100%  Bn   88%     259      0      0       0      0       0      0
 38%   2632      0      0    2632  103944    871    1112 244232       0      0    12     98%  100%  :f  100%       0      0      0       0      0       0      0
 21%   1105      0      0    1105   55646    415    4996  53596       0      0    12     96%   42%  :    38%       0      0      0       0      0       0      0
  9%    643      0      0     646   33061    253      16     32       0      0    12     94%    0%  -     3%       3      0      0       0      0       0      0
 10%    759      0      0     759   34509    275      28      0       0      0    12     96%    0%  -     1%       0      0      0       0      0       0      0
 12%   1041      0      0    1041   38390    397      20      0       0      0    12     97%    0%  -     1%       0      0      0       0      0       0      0
Sun Apr 14 22:06:55 PDT [cci-na02:shm.threshold.ioLatency:debug]: Disk 6c.38 has exceeded the expected IO latency in the current window with average latency of 50 msecs and average utilization of 41 percent. Highest average IO latency: 6c.25: 52 msecs; next highest IO latency: 6c.38: 50 msecs  
Sun Apr 14 22:06:55 PDT [cci-na02:shm.threshold.ioLatency:debug]: Disk 6c.36 has exceeded the expected IO latency in the current window with average latency of 50 msecs and average utilization of 41 percent. Highest average IO latency: 6c.25: 52 msecs; next highest IO latency: 6c.38: 50 msecs  
Sun Apr 14 22:06:55 PDT [cci-na02:shm.threshold.ioLatency:debug]: Disk 6c.25 has exceeded the expected IO latency in the current window with average latency of 52 msecs and average utilization of 42 percent. Highest average IO latency: 6c.25: 52 msecs; next highest IO latency: 6c.38: 50 msecs  
 26%    658      0      0     670   30454    268   11576 202953       0      0    12     96%   46%  Ff   37%      12      0      0       0      0       0      0
Sun Apr 14 22:06:55 PDT [cci-na02:shm.threshold.ioLatency:debug]: Disk 6c.17 has exceeded the expected IO latency in the current window with average latency of 50 msecs and average utilization of 41 percent. Highest average IO latency: 6c.25: 52 msecs; next highest IO latency: 6c.38: 50 msecs  
 22%    810      0      0     819   33288    326   12672 199088       0      0    12     96%  100%  :f  100%       9      0      0       0      0       0      0
 21%    973      0      0     977   50499    402    3268 102076       0      0    12     96%   59%  :    57%       4      0      0       0      0       0      0
 14%   1059      0      0    1059   56867    433      48     24       0      0    12     96%    0%  -     3%       0      0      0       0      0       0      0