mmremotefs command

Manages information needed for mounting remote GPFS file systems.

Synopsis

mmremotefs add Device -f RemoteDevice -C RemoteClusterName
             [-T MountPoint] [-t DriveLetter]
             [-A {yes | no | automount}] [-o MountOptions] [--mount-priority Priority]

or

mmremotefs delete {Device | all | -C RemoteClusterName} [--force]

or

mmremotefs show [Device | all | -C RemoteClusterName] [-Y]

or

mmremotefs update Device [-f RemoteDevice] [-C RemoteClusterName]
             [-T MountPoint] [-t DriveLetter]
             [-A {yes | no | automount}] [-o MountOptions] [--mount-priority Priority]

Availability

Available on all IBM Spectrum Scale editions.

Description

The mmremotefs command is used to make GPFS file systems that belong to other GPFS clusters known to the nodes in this cluster, and to maintain the attributes associated with these file systems. The keyword appearing after mmremotefs determines which action is performed:
add
Define a new remote GPFS file system.
delete
Delete the information for a remote GPFS file system.
show
Display the information associated with a remote GPFS file system.
update
Update the information associated with a remote GPFS file system.

Use the mmremotefs command to make the nodes in this cluster aware of file systems that belong to other GPFS clusters. The cluster that owns the given file system must have already been defined with the mmremotecluster command. The mmremotefs command is used to assign a local name under which the remote file system will be known in this cluster, the mount point where the file system is to be mounted in this cluster, and any local mount options that you may want.

Once a remote file system has been successfully defined and a local device name associated with it, you can issue normal commands using that local name, the same way you would issue them for file systems that are owned by this cluster.

When running the mmremotefs command delete and update options, the file system must be unmounted on the local cluster. However, it can be mounted elsewhere.

Parameters

Device
Specifies the name by which the remote GPFS file system will be known in the cluster.
-C RemoteClusterName
Specifies the name of the GPFS cluster that owns the remote GPFS file system.
-f RemoteDevice
Specifies the actual name of the remote GPFS file system. This is the device name of the file system as known to the remote cluster that owns the file system.
-Y
Displays the command output in a parseable format with a colon (:) as a field delimiter. Each column is described by a header.
Note: Fields that have a colon (:) are encoded to prevent confusion. For the set of characters that might be encoded, see the command documentation of mmclidecode. Use the mmclidecode command to decode the field.

Options

-A {yes | no | automount}
Indicates when the file system is to be mounted:
yes
When the GPFS daemon starts.
no
Manual mount. This is the default.
automount
When the file system is first accessed.
-o MountOptions
Specifies the mount options to pass to the mount command when mounting the file system. For a detailed description of the available mount options, see Mount options specific to IBM Spectrum Scale.
-T MountPoint
The local mount point directory of the remote GPFS file system. If it is not specified, the mount point will be set to DefaultMountDir/Device. The default value for DefaultMountDir is /gpfs, but it can be changed with the mmchconfig command.
-t DriveLetter
Specifies the drive letter to use when the file system is mounted on Windows.
--mount-priority Priority
Controls the order in which the individual file systems are mounted at daemon startup or when one of the all keywords is specified on the mmmount command.

File systems with higher Priority numbers are mounted after file systems with lower numbers. File systems that do not have mount priorities are mounted last. A value of zero indicates no priority.

--force
The --force flag can only be used with the delete option. It will override an error that can occur when trying to delete a remote mount where the remote cluster was already removed. If the original delete attempt returns an error stating it cannot check to see if the mount is in use, then this is the condition to use. The --force flag overrides and allows the deletion to complete.

Exit status

0
Successful completion. After successful completion of the mmremotefs command, the new configuration information is propagated to all nodes in the cluster.
nonzero
A failure has occurred.

Security

You must have root authority to run the mmremotefs command.

The node on which the command is issued must be able to execute remote shell commands on any other node in the cluster without the use of a password and without producing any extraneous messages. For more information, see Requirements for administering a GPFS file system.

Examples

This command adds remote file system gpfsn, owned by remote cluster k164.kgn.ibm.com, to the local cluster, assigning rgpfsn as the local name for the file system, and /gpfs/rgpfsn as the local mount point.
mmremotefs add rgpfsn -f gpfsn -C k164.kgn.ibm.com -T /gpfs/rgpfsn
The output is similar to this:
mmremotefs: 6027-1371 Propagating the cluster configuration data to all
  affected nodes.  This is an asynchronous process.
The mmremotefs show command can be used to see the changes.
mmremotefs show rgpfsn
The output is similar to this:
Local Name  Remote Name  Cluster name               Mount Point      Mount Options    Automount  Drive
rgpfs1      gpfs1        gpfs-n60-win.fvtdomain.net /rgpfs1          rw               no         K

See also

See also the topic about accessing GPFS file systems from other GPFS clusters in the IBM Spectrum Scale: Administration Guide.

Location

/usr/lpp/mmfs/bin