Ok, I've made the attempt to install all the necessary RHEL5.1 beta rpm's to get rdac working and unfortunately I had roll back. I had to install a bunch of gfs, cluster, and lvm rpm's, along with the new kernel and it seemed to work at first. I then fired up my cluster and it was very unstable. I've downloaded and compiled the latest multipath source (0.4.8). Now I need to compile the rdac hardware handler against my current kernel source. Can anyone provide me with the latest, patched source? Tore, I know you have it! After scanning through the posts, it looks like you've had the same problems I have and you're running the same hardware(Sun 6140). I could really use your help getting rdac working. Redhat totally gave me the cold shoulder when I opened a ticket with them. At this point, I need to keep the stock redhat kernel but am willing to build all the multipath stuff against it. I've got all the userland stuff compiled. Now I'm hoping I can get instructions on how to compile the rdac hw handler against my kernel. Thanks, --james -----Original Message----- From: dm-devel-bounces@xxxxxxxxxx [mailto:dm-devel-bounces@xxxxxxxxxx] On Behalf Of Tore Anderson Sent: Tuesday, September 18, 2007 12:40 AM To: device-mapper development Subject: Re: path priorities on Sun's 6140 * James Fillman > Ok. So I just realized that if I want to try the new RDAC support, > then I have to install the new beta kernel as well. It includes the > RDAC hardware handler. > > I'm under serious pressure to get my cluster up and running asap and > I don't think I want to be installing a bunch of beta packages onto > my production servers. Especially kernels. To me the benefit of RDAC mode would far outweigh the disadvantage of knowing you're running a beta kernel, but that's your call... With AVT mode you will have I/O interruptions and volume failovers when a node in your cluster boots. It's unavoidable. You'll probably want to test really well how the rest of the cluster behaves in such situations. > So this might mean not exploring the RDAC solution. Redhat's docs say > that they support a Sun OpenStorage D280 and our Sun rep says the > 6140 is essentially identical. If that's the case, what am I don't > wrong? The original hardware is called Engenio 3994 - you might be able to confirm that the D280 is the same by Googling some. (The IBM DS4700 model 72 is also the same, by the way). RH probably supports it in AVT mode. Your configuration looks okay to me, different path_grouping_policy then what I use but as long as the prio_callout works correctly the end result should be the same. My config looks like this on a RHEL4 box running in AVT mode: device { vendor SUN.* product CSM200_R.* path_grouping_policy group_by_serial path_checker tur prio_callout "/usr/local/sbin/mpath_prio_tpc /dev/%n" failback immediate no_path_retry queue } This gives me output from 'multipath -ll' like this in a dual fabric topology: nfs_ny (3600a0b80002625ae0000080745dbe5ca) [size=100 GB][features="1 queue_if_no_path"][hwhandler="0"] \_ round-robin 0 [prio=2][enabled] \_ 1:0:0:1 sdc 8:32 [active][ready] \_ 2:0:1:1 sdi 8:128 [active][ready] \_ round-robin 0 [prio=12][active] \_ 1:0:1:1 sde 8:64 [active][ready] \_ 2:0:0:1 sdg 8:96 [active][ready] SCSI targets 1:0:0 and 2:0:1 are to controller A, 1:0:1 and 2:0:0 are to controller B (the preferred one for LUN 1). I can verify that the prio_callout works correctly by testing one path: $ /usr/local/sbin/mpath_prio_tpc /dev/sde 6 Did you try host type AIX_FO, by the way? That was the one I found to work the best with AVT mode. Regards -- Tore Anderson -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
