.\" -*- nroff -*-
.\" Copyright (c) 2007, 2010, Oracle and/or its affiliates. All rights reserved.
.\"
-.\" Copyright (c) 2011, 2012, 2014, Intel Corporation.
+.\" Copyright (c) 2011, 2017, Intel Corporation.
.\"
.\" This file may be copied under the terms of the GNU Public License.
.\"
.TP
.BI \--index= index
Specify a particular OST or MDT index. Required for all targets other than the MGS.
+The index parameter may either be a decimal number or a hexadecimal number
+starting with '0x'.
.TP
.BI \--mkfsoptions= opts
Format options for the backing fs. For example, ext3 options could be set here.
.I key
to value
.IR value .
-This option can be repeated as desired. Typical options might include:
+This option can be repeated as desired. Typical options might include:
.RS
.I \--param sys.timeout=40
.RS
.BI \--stripe-count-hint= stripes
Used for optizing MDT inode size
.TP
+.BI \--force-nohostid
+Ignore unset hostid for ZFS import protection. To set hostid either set
+spl_hostid parameter for spl.ko or set /etc/hostid, see zgenhostid(8). To
+populate the spl_hostid parameter, spl.ko must be (re)loaded after /etc/hostid is
+created.
+
+.TP
.BI \--verbose
Print more information.
.TP
.BI \--version
Output build version of the mkfs.lustre utiltiy.
+.SH NID
+A Lustre network identifier (NID) is used to uniquely identify a Lustre network
+endpoint by node ID and network type. The format of the NID is:
+\fInetwork_id@network_type\fR.
+If a node has multiple network interfaces, it may have multiple NIDs, which must
+all be identified so other nodes can choose the NID that is appropriate for
+their network interfaces. Typically, NIDs are specified in a list delimited by
+commas (,). However, when failover nodes are specified, the NIDs are delimited
+by a colon (:) or by repeating a keyword such as \fI--mgsnode=\fR or
+\fI--servicenode=\fR.
+
.SH EXAMPLES
.TP
.B mkfs.lustre --fsname=testfs --index=0 --mdt --mgs /dev/sda1
.B mkfs.lustre --fsname=testfs --index=0 --ost --mgsnode=cfs21@tcp0 /dev/sdb
OST for filesystem 'testfs' on any node using the above MGS.
.TP
+.B mkfs.lustre --fsname=testfs --index=0 --mdt --mgs --servicenode=cfs21@tcp0,cfs21ib@o2ib0 --servicenode=cfs22@tcp0,cfs22ib@o2ib0 /dev/sda1
+Combined MGS and MDT for filesystem 'testfs' on failover pair cfs21 and cfs22.
+.TP
+.B mkfs.lustre --fsname=testfs --index=0 --ost --mgsnode=cfs21@tcp0,cfs21ib@o2ib0:cfs22@tcp0,cfs22ib@o2ib0 --failnode=cfs24@tcp0,cfs24ib@o2ib0 /dev/sdb
+OST for filesystem 'testfs' using the above MGS and having a failover partner
+cfs24.
+.TP
.B mkfs.lustre --mgs /dev/sda1
Standalone MGS on e.g. node cfs22
.TP