Shell Commands › Volume Management › manage (Volume Management)--Manage a Volume

manage (Volume Management)--Manage a Volume

Manage a volume

Syntax

vol manage <name> [<name2>] [ --abort | ( [ --ro | --rw ] [ <prop>=<val> ]* [ --nossh ] [ --nomount ] [filer=<filer> ] ) ]

Parameters

name

Name of the volume to be manage.

name2

Name of secondary volume to be managed. If this argument is specified the volume represented by name is managed read-only and the volume represented by name2 is managed read/write.

--abort

Abort previous volume manage session.

--ro

access to volume is read-only.

--rw

access to volume is read/write.

--nossh

do not provide SSH access to the managed volume.

--nomount

do not mount file system of the managed volume.

filer=<filer>

Specifies the Filer to be used for the operation. Possible values are 'windows' or 'linux'. If this option is not specified, the filer will be selected based on the first partition that is not raw.

prop=val

Specifies settings to configure external network access for use with the volume manager GUI/shell. The following values are supported:

ip - Specifies the IP address.

netmask - Specifies the network mask. This must be specified if ip is specified.

gateway - Specifies the IP address of the default network gateway. It can be left blank only if the remote host is on the same subnet; must be specified otherwise.

dns1 - Specifies the IP address of the primary DNS server used to resolve domain names. This allows the user to specify hostnames when uploading/downloading files to/from a volume.

dns2 - Specifies the IP address of the secondary DNS server, which will be used if the primary DNS server does not respond.

Examples

volume manage sugarcrm:data --rw

manage application user volume

volume manage /system:NAS.boot --ro

manage global catalog class volume

volume manage /myapp:myvol --rw ip=192.168.1.100 netmask=255.255.255.0 gateway=192.168.1.254

manage application user volume and set up external network access from within the volume manager. This allows the user to upload/download files to/from the specified volume to/from a remote location, all from within the volume manager GUI/shell.

volume manage my-app:data my-app:data1

manage two application user volumes

vol manage my-app:data1 --abort

abort management of the previous volume management session

vol manage my-app:data --abort

abort management of application user volume

Notes:

• A specification of the naming convention for CA AppLogic for System z® entities can be found here.
• Only maintainers may manage a global read-only volume in read/write mode.
• By default, the user is SSH'd into the volume manager shell. The volume is accessible under /mnt/vol.
• If two volume are specified, the first volume is managed as read-only and the second volume is managed as read/write.
• If two volumes are specified, both volumes must be manageable by the same CA AppLogic for System z® filer application.
• If no additional arguments are specified, application user and global volumes are managed as read/write and all other volumes are managed as read-only. To override the defaults, specify --ro or --rw as is appropriate.
• When managing catalog class volumes, the user must have write access to the catalog class descriptor.
• The GUI does have a 10MB file upload limitation. To upload larger files to your volume, use the volume manager shell.
• To abort a management session where two volumes were specified, the destination volume (i.e., <name2>) must be specified for the abort management command.
• All partitions and logical volumes (if present) supported by the chosen Filer are mounted (unless --nomount is used). If any of them fail to mount the operation will still succeed, provided that at least one partition/lv was mounted. Information about the failed mounts will be included in the MOTD file so it is the first thing the user sees when he logs in over ssh.
• The --nomount option can be used to skip mounting of partitions (preventing the failure of the operation if none of the partitions are supported by the filer).