The NLVM options can be used as needed with any command, except where it is otherwise noted. NLVM options must immediately follow nlvm in the command:
nlvm [nlvm_option] <command> [command_options]
This option causes a /var/opt/novell/log/nss/debug/nlvm_debug.log file to be created so that the operations can be reviewed. This is helpful in diagnosing problems in running the NLVM utility. Up to 10 debug files can be created; they are numbered automatically.
NOTE:The debug can be turned on always by using the /etc/opt/novell/nss/nlvm.conf file.
This option can be used with certain commands to force the command to complete. Support for this NLVM option is indicated in the individual commands.
This option forces the command to get the nlvm lock. The lock protects multiple users from modifying things at the same time.
Use with caution! This option is to be used only if the lock does not get released properly due to a segment fault or other operation aborts.
This option prevents pools that have been unmounted from being mounted.
Pools are by design auto mounted. Therefore, running the nssmu utility, or running most nlvm commands without the -m option can cause an unmounted pool to be remounted if underlying devices and partitions still exist. To execute an nlvm command without mounting the unmounted pools, you must include the -m option. The nlvm mount command internally sets the -m flag, so only the specified pool is mounted.
This option can be used with certain commands to prevent a confirmation message from being displayed, such as when you initialize a device or delete Linux POSIX volumes, pool moves, partitions, pools, RAIDs, RAID segments, snapshots, and NSS volumes. Support for this NLVM option is indicated in the individual commands.
This option forces a fresh rescan of the system before executing a command to update the device and partition objects. Use this if something changed the information outside the NSSMU, Novell iManager, or nlvm utility.
This option sets the shared override bit for the command being executed.
In a Novell Cluster Services cluster, NLVM uses the cluster’s SBD to detect if a node is a cluster member and to lock against concurrent changes to physically shared storage. Without an SBD, NLVM cannot detect whether a node is a member of the cluster and cannot acquire the locks it needs to execute tasks. In this state, you can use the -s option with NLVM commands to prepare a device and create an SBD partition. To minimize the risk of corruption, you must ensure that nobody else is changing any storage on any nodes at the same time.