Comments on: automatic open-iscsi volume mounting on debian etch

By: paul

paul — Tue, 10 Jun 2008 13:55:57 +0000

I see some errors in your configuration. The problem is that you are using readsector0 for path checking instead of RDAC and a wrong hwhandler. You have to setup multipath.conf with a working configuration. Have a look at http://www3.dslreports.com/shownews/Benchmarking-the-MD3000-powervault-under-linux-87401 for an example configuration. It worked in my situation.

By: btm

btm — Fri, 06 Jun 2008 16:55:42 +0000

@Jim

I did see I/O errors but they were from the nodes on the old path failing. I had no problems with accessing the data through the multipath device, but I haven’t tried running bonnie++ against the multipath device while failing over the controller. I assume that the device created by multipath will throw I/O errors if all the devices behind it go away.

By: Jim Coates

Jim Coates — Fri, 06 Jun 2008 14:53:32 +0000

When you changed the preferred path on the MD3000i do you observer I/O errors during the trespass? We are using this configuration to expose disks to oracle ASM in our test and qa environments and don’t want to see I/O errors should a controller fail. Is multipathd capable of handling the transition and basically holding the disk requests off until the transition has been made?

By: Scott Dodson

Scott Dodson — Sat, 31 May 2008 05:03:45 +0000

Other options are persistent udev rules. http://kbase.redhat.com/faq/FAQ_103_12118.shtm

Or labels, tune2fs -L then LABEL=foo in your fstab. GFS has labels, I imagine OCFS2 does as well.

If you’re going to be using multipath you can do it there too.

I think all of these should work on debian systems.