HP XP P9000 RAID Manager Reference Guide (T1610-96061, January 2014)

The logical and physical drives designated as the objects of the umount command are not opened
to any applications. For example, confirm that Explore is not pointed on the target drive. If it is,
then the target drive is opening.
Umount command does not ignore the detected error on the NT file system, so that umount is
successful in a normal case (NO ERROR case) only on NT file system. For example, confirm the
target drive has no failure on the system for Event Viewer. If so, you must reboot the system or
delete the partition and reconfigure the target drive.
Note: The umountd command has the following behavior as well.
Unmount the logical drive after waiting (30 sec) the delayed (paging) IO for dismount after flushed
the system buffer to a drive.
This avoids a problem (Windows 2003 only) that NTFS on PVOL is split on inconsistent state
because Windows 2003 (SP1) delays the IO for dismounting. This also avoids a problem that the
delayed (paging) IO for dismounting is written on SVOL_PAIR(Writing Disable) state by rescan,
and logged as Windows event (that is, ID51,57).
These problems do not occur on Windows 2008 systems.
Environment variable subcommands
If no environment variables are set in the execution environment, the following environment variable
subcommands set or cancel an environment variable within the RAID Manager command.
setenv: The setenv subcommand sets the specified environment variable(s).
usetenv: The usetenv subcommand deletes the specified environment variable(s).
env: The env subcommand displays the environment variable(s).
sleep: The sleep subcommand causes RAID Manager to wait for the specified time.
Syntax
-x setenv vaname value -x usetenv vaname -x env -x sleep time
Arguments
DescriptionArgument
Specifies the environment variable to be set or canceled.Vaname
Specifies the value or character string of the environment variable to be set.Value
Specifies the sleep time in seconds.Time
CAUTION: The environment variables must be set before connecting to HORCM. And it must be
specified during interactive mode (-z option). If specified with other than interactive mode, all
specified environment variables are not enable. Changing an environment variable after a RAID
Manager command execution error is invalid.
Example
The following examples show the setenv and usetenv subcommands used as an option of the
raidscan command. This example changes from 'HORC' to 'HOMRCF' an execution environment
of the raidscan command that makes a dialog mode, because of establishing 'HORCC_MRCF' as
an environment variable.
raidscan[HORC]: -x setenv HORCC_MRCF 1
raidscan[HOMRCF]:
raidscan[HOMRCF]: -x usetenv HORCC_MRCF
raidscan[HORC]:
Environment variable subcommands 113