http://bugzilla.novell.com/show_bug.cgi?id=630434
http://bugzilla.novell.com/show_bug.cgi?id=630434#c3
--- Comment #3 from Dennis Olsson 2010-08-12 21:05:07 CEST ---
Yes, this is exactly the case here.
Sorry that my bug reporting was not as clear as I thought.
The problem is:
(1) Doing as described in the SLES 11 SP1 documentation, i.e.
- Setting the "node.startup" to "automatic",
- Adding "nofail" option to the file system options in "/etc/fstab" for the
file system found on the iSCSI disk(s),
I end up with a system that boots, but is unusable, while the "/data" iSCSI
file system has not been mounted.
The iSCSI disk has been attached to the system (by "open-iscsi"), but the
"/data" file system has not been *checked* nor *mounted*.
I.e. using the "nofail" option on the "/data" file system in "/etc/fstab" only
prevents the system from not booting at all, but it does not ensure that the
system ends up in a usable state (in my case neither "nfsserver" nor "autofs"
works correctly -- not even if "/data" is being manually mount after having
booted up, except if "nfsserver" and "autofs" is stopped, "/data" mounted,
restarting "autofs" and "nfsserver").
This is *not* the way the usage of iSCSI disks should be used! .-)
(2) Doing as one would except the world to work (and as described above in
comment #0 under "The correct way of handling iSCSI attached devices are"),
i.e.
- Setting the "node.startup" to "onboot",
- Adding the "/data" file system as normal, just like when using a local
disk to the "/etc/fstab",
results in a non bootable system, while during the file system checking "fsck"
cannot find the "/data" file system disk at all, and thus ending up in the
"(repair filesystem)" shell prompt.
As I wrote in comment #0, iSCSI based systems that need file systems to be
mounted during the boot up sequence have to attached to the booting system
during the execution of "boot.open-iscsi" using "node.startup" set to "onboot",
allowing for these file systems to be checked and mounted by "boot.localfs".
Just think what would happen to a system, if you have a "/" on a local disk and
"/usr" on an iSCSI disk => Non bootable system.
Using "automatic" only ensures that an iSCSI target gets attached to the
system, but cannot be incorporated/used for normal mount points, simply because
the attachment of the iSCSI targets happens far too late the in the booting
sequence.
The "automatic" setting is useful for iSCSI disks that are used by e.g.
databases that are being started rather late in the boot sequence, but is
absolutely *not* usable for iSCSI disks holding normal mounted file systems.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.