HP StorageWorks XP Provisioning Manager User Guide (December 2005)

Working With OS-Based Constraints 67
4-5-1 Prerequisites for the Host
• Device Manager agent
You must install the Device Manager agent on a host managed by Provisioning Manager. If the Device
Manager agent is not installed, the values for some items may not be displayed.
If the Provisioning Manager support functionality for the Device Manager agent is not installed, the values
for some items may not be displayed. The Provisioning Manager support functionality for the Device
Manager agent is installed on a Device Manager agent 1.0 or later that is supported by Provisioning
Manager.
• When the host in use has not recognized any logical unit
When adding a device file, or adding or expanding a file system for a host that is not recognizing any LUs,
use Device Manager to register the port WWN of the HBA for the host in advance. If no WWN is
registered, no volume will become selectable in the wizard step for selecting a volume, and you will be
unable to continue operation.
4-5-2 About Host Management in Linux Environments
This section provides information about using Provisioning Manager to manipulate file systems and device
files.
4-5-2-1 Notes on Installing a Storage Subsystem
Make sure that you specify a unique port address for each port of storage devices in the same zone. If the
same port addresses exist in the same zone, the OS cannot recognize the ports and may not recognize the
device files. In such a state, if you add a device file, add a file system, or expand a file system from
Provisioning Manager, the device file cannot be recognized and an error occurs.
4-5-2-2 Notes on Adding File Systems
A file system cannot be added if Logical Volume Manager has not been installed.
Volumes to which one of the following conditions apply cannot be used for file system expansion:
• The volume manager is using a volume on a host where the Device Manager agent has been installed
• The volume is mounted on a host where the Device Manager agent has been installed
• The volume is being used as a command device
• The volume is being used as an S-VOL for Continuous Access XP
• The volume is being used as an S-VOL or SP-VOL for Business Copy XP
• The volume is being used as a V-VOL or POOL for Snapshot XP
• The volume is being used as an on-demand device
• The Read/Write permissions have not been set in the LUN Security XP Extension function
• The Auto Lun XP attribute has been set
• The volume emulation type is not one of the following: OPEN-3, OPEN-8, OPEN-9, OPEN-K, OPEN-E,
OPEN-L, OPEN-M, OPEN-V
• The volume size is less than 512 MB
• Multiple paths are assigned to the volume
Double-byte characters, such as Japanese characters, are not usable for the mount point name that is
specified when a file system is added.
4-5-2-3 Notes on Expanding File Systems
In the following cases, file systems cannot be expanded:
• The type of file system that is to be expanded is neither ext2 nor ext3
• Logical Volume Manager is not being used
• Other processing is using the file system to be expanded
• The logical volume that is mounted at the specified mount point is a snapshot volume
• There is more than one mount point for the file system to be expanded
• Multiple file systems have been mounted on the same directory
Volumes that satisfy one of the following conditions cannot be used for file system expansion:
• The volume manager is using a volume on a host where the Device Manager agent has been installed