https://bugzilla.novell.com/show_bug.cgi?id=826700
https://bugzilla.novell.com/show_bug.cgi?id=826700#c6
Lee Duncan changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P3 - Medium
Status|ASSIGNED |NEEDINFO
InfoProvider| |kl@httgmbh.net
--- Comment #6 from Lee Duncan 2013-09-10 14:12:34 PDT ---
I have found the source of your issue, or at least the heart of it.
The fix for bnc#834256 updated the initrd iscsi scripts to handle boot-time
iSCSI volumes. These are volumes that the user wants at boot time, even though
they are not considered system directories (such as "/" or "/usr").
The problem is that you have a boot-time iSCSI volume listed in /etc/fstab. I
believe you were counting on the fact that if you put "nofail" as an fstab
option, that the failure to mount this volume at boot time could be ignored,
and the volume would get mounted (by somebody) later, when iSCSI was working.
It is difficult to support both those that want boot-time iSCSI volumes to
really be present at boot time, as indicted by their entry in fstab, and those
who do not, even though the filesystems are listed in fstab.
I suggest that we update the initrd scripts for iSCSI such that they would not
add iSCSI to the boot process if your fstab iSCSI volume includes the "noauto"
option.
In other words, with my suggested fix, if you put "noauto" in the fstab options
for an iSCSI volume, then "mkinitrd" would not include iSCSI.
I have tested such an update to the script, and it works, so please let me know
if such a solution wold be sufficient for you.
All the other "solutions" I can think of are really workarounds, such as
commenting out your iSCSI mount at mkinitrd time ...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.