Section: configuration utilities (8)Updated: 2008 Mar 15Local indexUp
mount.lustre - start a Lustre client or target service
mount -t lustre [-o options] directory
is used to start a Lustre client or target service. This program should not be
called directly; rather it is a helper program invoked through
as above. Lustre clients and targets are stopped by using the
There are two forms for the
option, depending on whether a client or a target service is started:
mounts the Lustre filesystem named
on the client by contacting the Management Service at
on the pathname given by
The format for
is defined below. A mounted client filesystem appears in
and is usable like any local filesystem and provides a full
starts the target service defined by the
command on the physical disk
A mounted target service filesystem is only useful for
operations and appears in
to show the device is in use.
The mgs specification may be a colon-separated list of nodes:
each node may be specified by a comma-separated list of NIDs.
In addition to the standard options listed in
Lustre understands the following
Enable full flock support, coherent across all client nodes.
Enable local flock support, using only client-local flock (faster, for applications that require flock but do not run on multiple nodes).
Disable flock support entirely. Applications calling flock will get an error.
Enable get/set of extended attributes by regular users. See the
Disable use of extended attributes by regular users. Root and system processes can still use extended attributes.
Enable POSIX Access Control List support. See the
Disable Access Control List support.
In addition to the standard mount options and backing disk type
(e.g. ext3) options listed in
Lustre understands the following
Only start the MGC (and MGS, if co-located) for a target service, and not the actual service.
Start a MDT with a co-located MGS without starting the MGS.
Start a client or MDT with a (colon-separated) list of known inactive OSTs.
Abort client recovery and start the target service immediately.
Sets the stripe cache size for server side disk with a striped raid
Allow 'timeout' seconds for clients to reconnect for recovery after a server
crash. This timeout will be incrementally extended if it is about to expire
and the server is still handling new connections from recoverable clients.
The default soft recovery timeout is set to 300 seconds (5 minutes).
The server will be allowed to incrementally extend its timeout up to a hard
maximum of 'timeout' seconds. The default hard recovery timeout is set to
900 seconds (15 minutes).
mount -t lustre cfs21@tcp0:/testfs /mnt/myfilesystem
Start a client for the Lustre filesystem 'testfs' at the mount point
/mnt/myfilesystem. The Management Service is running on a node reachable
from this client via the nid cfs21@tcp0.
mount -t lustre /dev/sda1 /mnt/test/mdt
Start the Lustre metadata target service from /dev/sda1 on mountpoint /mnt/test/mdt.
mount -t lustre -L testfs-MDT0000 -o abort_recov /mnt/test/mdt
Start the testfs-MDT0000 service (by using the disk label), but abort the
If the Service Tags tool (from the sun-servicetag package) can be found in
/opt/sun/servicetag/bin/stclient an inventory service tag will be created
reflecting the Lustre service being provided. If this tool cannot be found
will silently ignore it and no service tag is created. The
tool only creates the local service tag. No information is sent to the asset
management system until you run the Registration Client to collect the tags
and then upload them to the inventory system using your inventory system account.
See https://inventory.sun.com/ for more details on a web-based, free, IT asset
Not very many mount options can be changed with
Please report all bugs to Sun Microsystems using http://bugzilla.lustre.org/