Suse 11.0 iscsi mount on boot & hotplug

English Install/Boot/Login
1

Hi,

We seem to have found an issue with suse 10.3-11.0 which does errors on mounting iscsi volumes with the hotplug flag is fstab. This, of course, does not stips us from starting certain services which use these volumes on boot. 10.1 does not have this issue.

So anyone know how this was broken or have a workaround?

Mount errors:

kernel: EXT3-fs: Unrecognized mount option “hotplug” or missing value

NOTE: This also will error with reiserfs.

2

Anyone? I really need to resolve this so that we can upgrade a large number of computers. This is the only problem we cannot solve so any help would be very much appreciated.

Thanks

3

anyone got any info about this?

4

anyone got any clues? How about any suggestion at all which may be to contact the devs or just use fedora or centos. anything is better than nothing. I guess this is what you get for not paying for Esuse.

5

hi,

Sorry, I can’t help you.
I’ve exactly the same issue. But using “hotplug” works in 10.3 as does in 11.0.
( so my machines don’t wait for manual repair ).
Furthermore I use LVM on external ISCSI-Devices. LVM is initializing early before boot procedure manages iscsi. So I have to do two jobs : mounting the iscsi-device and activating the LVM-volumeGroup - both manually.
Has anybody an idea, how to direct boot procedure doing things in the right way ?

thanks in advance
Wilko

6

I’m having this same issue. I guess this is a bump to see if we can get an answer.

Cheers,
CT

7

I don’t believe I’ve seen the hotplug option on mount lines before. What does it do? Is it something peculiar to Redhat?

8

The hotplug option is used to mount boot-time network file systems on suse. For some reasons, suse decided to go against the kernel and mount command supported NET_DEV way and use hotplug. Using hotplug, the driver used to deal with USB devices I think, on suse prior to 10.3 is the only way to mount iscsi volumes on boot via fstab and after 10.3, it appears, there is no way to do this other than using klug and custom scripts.

9

It has been my past experience to just forget about mounting your iSCSI-based LUNS in /etc/fstab. Just place your mount commands in /etc/init.d/boot.local. FC based LUNs are much more forgiving. Network based connections need more time.