Section: configuration utilities (8)Updated: 2008 Mar 15Local indexUp
NAME
tunefs.lustre - modify the Lustre configuration information on a disk
SYNOPSIS
tunefs.lustre
[options]
device
DESCRIPTION
tunefs.lustre
is used to modify the configuration information on a Lustre target
disk. This includes upgrading old (pre-Lustre 1.6) disks. This does not
reformat the disk or erase the target information, but modifying the
configuration information can result in an unusable filesystem. You have
been warned.
Changes made here will affect a filesystem only when the target is next
mounted.
OPTIONS
--comment=comment
Set user comment about this disk, ignored by Lustre.
--dryrun
Only print what would be done; does not affect the disk
--erase-params
Remove all previous parameter info
--failnode=nid,...
Set the NID(s) of a failover partner. This option can be repeated as desired.
--fsname=filesystem_name
The Lustre filesystem this service will be part of. Default is 'lustre'
--index=index
Force a particular OST or MDT index
--mountfsoptions=opts
Set the mount options that will be used when mounting the backing fs.
WARNING: unlike earlier versions of tunefs.lustre, this version
completely replaces the existing mount options with those specified on
the command line, issuing a warning on stderr if any of the default
mount options are omitted. The defaults for ldiskfs are
OST: errors=remount-ro,mballoc,extents;
MGS/MDT: errors=remount-ro,iopen_nopriv,user_xattr.
DO NOT alter the default mount options unless you know what you are doing.
--mgs
Add a configuration management service to this target
--mgsnode=nid,...
Set the NID(s) of the MGS node, required for all targets other than the MGS.
--nomgs
Remove a configuration management service to this target
--quiet
Print less information.
--verbose
Print more information.
--writeconf
Erase all config logs for the filesystem that this MDT is part of, and
regenerate them. This is very dangerous. All clients and servers should
be stopped.
All targets must then be restarted to regenerate the logs.
No clients should be started until all targets have restarted.
In general this should be executed on the MDT only, not the OSTs.