HP File System Extender (FSE) LAM, LAM, WORM, fse –, fse –, fse –, fse –, fse –, fse –, –mount, Regular, –umount, –umount, Unknown, Unknown, 2.1 NAME, No–Config, Inactive, LAM–No–HSM

2.1 NAME 7

•Regular ...... the volume is mounted using HSM file system and operates as a regular FSE partition.

•WORM ......... the volume is mounted using HSM file system and operates as a WORM FSE partition.

•LAM .......... the volume is mounted using HSM file system and operates in

the Limited Access Mode. The operation of HSM FS filter for that volume was manually switched to LAM using the fse – –limit–accesscommand. Use the fse – –full–accesscommand to switch the HSM FS filter operation for the volume back to the Full Access Mode.

• LAM–No–HSM ... this status is the same as LAM with the only difference that the fse–hsm process is not running. There are various causes of this

condition. If you have run the fse – –umount	command on this volume
recently, you can start fse–hsm by running the	fse – –mount command. If

the command reports an error "HSM already started. Unmount first.", run fse – –umountagain and examine the FSE error log to determine the cause of the fse–hsm failure.

•Unattached ... this status is the same as Unknown with the only difference that the HSM FS filter once had control over the volume.

•	No–Config .... this status is the same as LAM–No–HSMbut the cause is
	different. Possible reasons are a disabled or removed FSE partition. To re-
	sume using the volume as HSM file system, enable or add the corresponding
	FSE partition again. To use the volume natively (through NTFS), run the
	command fse – –dismount–ntfs .
•	Inactive ..... the volume is prepared to be mounted using HSM file system
	but the HSM FS filter is not attached to it yet. Either the volume was format-
	ted and the corresponding FSE partition has not been configured yet, or the
	volume has not been accessed yet. Run the command fse – –mounton the
	volume. If the volume status does not change, run fse – –dismount–ntfs .

•Unknown ...... the volume is not under the FSE control or the fse–fsevtmgr process is not running. In the latter case, most probably the FileSystemID variable in the FSE partition configuration has wrong contents that must be corrected.

HP StorageWorks File System Extender Software CLI reference