How To Configure - Novell LINUX ENTERPRISE SERVER 10 SP2 - INSTALLATION AND ADMINISTRATION Installation Manual

The newly generated devices show up in the output of lsscsi and can now be accessed
by mount.
12.2.3 Configuring LVM Autoassembly on
iSCSI Devices
LVM startup is supported by udev, so that any LVM volume groups will be activated
automatically via udev once all required physical volumes have been detected.
LVM autoassembly in udev makes use of the udev helper program collect. This
program takes as the first argument an abstract ID to be checked, followed by a list of
component IDs. Once this program has been called with each of the component IDs as
the first argument it'll return 0.
So for autoassembly the physical volume UUIDs for the given volume group is registered
as argument list for collect. udev (or rather vol_id) is capable of detecting the
physical volume UUID on a device and hence it can be passed as the first argument to
collect.
Once collect has been called with all physical volume UUIDs (i.e. udev has received
events for all component devices) the next rule triggers which just calls vgchange
-a y <vgname> and the volume group will be activated.

How to configure

Use the script /usr/share/doc/packages/lvm2/lvm-vg-to-udev-rules
.sh. It takes as argument the volume group you want to start automatically. This script
will generate the required udev rules. Now restart iSCSI to activate the volume groups.
If you want to have the array started automatically on boot you have to switch the
iSCSI component devices to automatic, so that the initiator will log into the target
automatically on boot.
12.2.4 The iSCSI Client Databases
All information that was discovered by the iSCSI initiator is stored in two database
files that reside in /var/lib/open-iscsi. There is one database for the discovery
Mass Storage over IP Networks—iSCSI 279