2 .\" Copyright 2008 by Sun Microsystems. All Rights Reserved.
3 .\" This file may be copied under the terms of the GNU Public License v2.
5 .TH mount.lustre 8 "2008 Mar 15" Lustre "configuration utilities"
7 mount.lustre \- start a Lustre client or target service
10 .BI "mount \-t lustre [\-o " options "] " directory
13 is used to start a Lustre client or target service. This program should not be
14 called directly; rather it is a helper program invoked through
16 as above. Lustre clients and targets are stopped by using the
21 There are two forms for the
23 option, depending on whether a client or a target service is started:
25 .IR <mgsspec> :/ <fsname>
26 mounts the Lustre filesystem named
28 on the client by contacting the Management Service at
30 on the pathname given by
34 is defined below. A mounted client filesystem appears in
36 and is usable like any local filesystem and provides a full
37 POSIX-compilant interface.
40 starts the target service defined by the
42 command on the physical disk
44 A mounted target service filesystem is only useful for
46 operations and appears in
48 to show the device is in use.
51 .BI <mgsspec>:= <mgsnode>[:<mgsnode>]
52 The mgs specification may be a colon-separated list of nodes:
54 .BI <mgsnode>:= <mgsnid>[,<mgsnid>]
55 each node may be specified by a comma-separated list of NIDs.
57 In addition to the standard options listed in
59 Lustre understands the following
64 Enable full flock support, coherent across all client nodes.
67 Enable local flock support, using only client-local flock (faster, for applications that require flock but do not run on multiple nodes).
70 Disable flock support entirely. Applications calling flock will get an error.
73 Enable get/set of extended attributes by regular users. See the
78 Disable use of extended attributes by regular users. Root and system processes can still use extended attributes.
81 Enable POSIX Access Control List support. See the
86 Disable Access Control List support.
88 In addition to the standard mount options and backing disk type
89 (e.g. ext3) options listed in
91 Lustre understands the following
96 Only start the MGC (and MGS, if co-located) for a target service, and not the actual service.
99 Start a MDT with a co-located MGS without starting the MGS.
102 Start a client or MDT with a (colon-separated) list of known inactive OSTs.
105 Abort client recovery and start the target service immediately.
108 .B mount -t lustre cfs21@tcp0:/testfs /mnt/myfilesystem
109 Start a client for the Lustre filesystem 'testfs' at the mount point
110 /mnt/myfilesystem. The Management Service is running on a node reachable
111 from this client via the nid cfs21@tcp0.
113 .B mount -t lustre /dev/sda1 /mnt/test/mdt
114 Start the Lustre metadata target service from /dev/sda1 on mountpoint /mnt/test/mdt.
116 .B mount -t lustre -L testfs-MDT0000 -o abort_recov /mnt/test/mdt
117 Start the testfs-MDT0000 service (by using the disk label), but abort the
120 If the Service Tags tool (from the sun-servicetag package) can be found in
121 /opt/sun/servicetag/bin/stclient an inventory service tag will be created
122 reflecting the Lustre service being provided. If this tool cannot be found
124 will silently ignore it and no service tag is created. The
126 tool only creates the local service tag. No information is sent to the asset
127 management system until you run the Registration Client to collect the tags
128 and then upload them to the inventory system using your inventory system account.
129 See https://inventory.sun.com/ for more details on a web-based, free, IT asset
132 Not very many mount options can be changed with
134 Please report all bugs to Sun Microsystems using http://bugzilla.lustre.org/
139 filesystem package and is available from Sun Microsystems, Inc.
141 http://downloads.lustre.org
146 .BR tunefs.lustre (8),