3-14 ensuring dynamic link manager operations, 3-15 deleting a mount point directory, 4 restrictions when the host os is aix – HP StorageWorks XP48 Disk Array User Manual

Page 62: 4-1 prerequisites for the host, 4-2 restrictions on expansion and deletion, Changing the file system check at startup setting, Ensuring dynamic link manager operations, Deleting a mount point directory, Restrictions when the host os is aix, Prerequisites for the host

Advertising
background image

Working With OS-Based Constraints 62

The default setting value of the log size for VERITAS™ File System is 16 MB. Change this value as necessary.
In UFS, the log size is automatically determined. The maximum log size is approximately 1 MB for each 1-GB
file system, and total size is up to 64 MB.

4-3-13 Changing the File System Check at Startup Setting

Provisioning Manager specifies that the file system is to be checked at system startup after a file system is
created. To change this setting, manually change the setting specified in the information file for the file system,
such as /etc/filesystems, /etc/vfstab.

Depending on the cluster management software, if a standby configuration is used and this setting is specified
so that the file system is checked at startup, it may take time to switch the server when an error occurs. To
avoid this, the setting must be changed so that the file system check is not performed at startup. For details,
see the documentation for the relevant cluster management software.

4-3-14 Ensuring Dynamic Link Manager Operations

In any of the following environments, if a Device Manager agent version 1.0 or later is installed on the host,
Provisioning Manager can display a list of volumes, including the unmanaged LUs, and can be used to specify
settings for the managed LUs:

When the LU is manually excluded from the Dynamic Link Manager management

When multi-path management software other than Dynamic Link Manager is also used

However, for an LU managed by a path manager other than Dynamic Link Manager, Provisioning Manager
cannot acquire the information managed by the path manager, such as the number of paths and data paths.

To specify LU settings in the above environment, check the following items:

That the version of the Device Manager agent installed on the host that manages the target LU is
version 1.0 or later

That the target LU is managed by Dynamic Link Manager

NOTE:

Provisioning Manager treats all LUs that are added when file systems or device files are added or

expanded as being under the management of Dynamic Link Manager.

4-3-15 Deleting a Mount Point Directory

Even if a file system is deleted, the mount point remains. Use the OS command to manually delete the folder
when you no longer need it.

4-4 Restrictions When the Host OS is AIX

®

For details about the maximum setting values for manual configuration, see

Table 4-1

in

4-7

.

4-4-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.

4-4-2 Restrictions on Expansion and Deletion

Notes on expanding a file system

Provisioning Manager cannot expand file systems in the following cases:

The volume manager used in the file system is other than Logical Volume Manager

A file system whose type is other than JFS

RAID software has been configured in the file system.

Notes on deleting a file system

Provisioning Manager cannot delete the following file systems:

A file system whose type is other than JFS

Advertising
This manual is related to the following products: