Lustre 1.6 Operations Manual

Mounting Lustre on a client node
$ mkdir -p /mnt/testfs
$ mount -t lustre cfs21@tcp:0:/testfs /mnt/testfs
The MGS and the MDT can be run on separate devices. With the MGS on node
’mgs16’:
$ mkfs.lustre --mgs /dev/sda1
$ mkdir -p /mnt/mgs
$ mount -t lustre /dev/sda1 /mnt/mgs
$ mkfs.lustre --fsname=spfs --mdt --mgsnode=mgs16@tcp0 /dev/sda2
$ mkdir -p /mnt/test/mdt
$ mount -t lustre /dev/sda1 /mnt/test/mdt
If the MGS node has multiple interfaces (for example, mgs16 and 1@elan), only the
client mount command has to change. The MGS NID specifier must be an
appropriate nettype for the client (for instance, TCP client could use uml1@tcp0 and
Elan client could use 1@elan). Alternatively, a list of all MGS NIDs can be provided
and the client chooses the correct one.
$ mount -t lustre mgs16@tcp0,1@elan:/spfs /mnt/spfs
Reformat a device that has already been formatted with mkfs.lustre
$ mkfs.lustre --fsname=spfs --mdt --mgs --reformat /dev/sda1
Note – Error -19 = -ENODEV (from /usr/include/asm/errno.h) occurs when the
client tries to connect to the server and fails to export the Lustre filesystem. The
scenario can be: shut down the service, start up the service, fail over to another
server node (if you have failover configured), or configuration errors.
Chapter 4 Lustre Installation 4-7