2014-04-02 08:29:34 +00:00
|
|
|
btrfstune(8)
|
|
|
|
============
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
2015-06-02 17:34:40 +00:00
|
|
|
btrfstune - tune various filesystem parameters
|
2014-04-02 08:29:34 +00:00
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
2017-06-22 17:49:55 +00:00
|
|
|
*btrfstune* [options] <device> [<device>...]
|
2014-04-02 08:29:34 +00:00
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
2017-12-07 20:26:09 +00:00
|
|
|
*btrfstune* can be used to enable, disable, or set various filesystem
|
2015-06-02 17:34:40 +00:00
|
|
|
parameters. The filesystem must be unmounted.
|
|
|
|
|
|
|
|
The common usecase is to enable features that were not enabled at mkfs time.
|
|
|
|
Please make sure that you have kernel support for the features. You can find a
|
|
|
|
complete list of features and kernel version of their introduction at
|
2016-09-01 16:51:18 +00:00
|
|
|
https://btrfs.wiki.kernel.org/index.php/Changelog#By_feature . Also, the
|
|
|
|
manual page `mkfs.btrfs`(8) contains more details about the features.
|
|
|
|
|
2017-12-07 20:26:09 +00:00
|
|
|
Some of the features could be also enabled on a mounted filesystem by other
|
|
|
|
means. Please refer to the 'FILESYSTEM FEATURES' in `btrfs`(5).
|
2014-04-02 08:29:34 +00:00
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
-------
|
2017-04-16 17:20:02 +00:00
|
|
|
|
2019-01-16 23:33:08 +00:00
|
|
|
-f::
|
|
|
|
Allow dangerous changes, e.g. clear the seeding flag or change fsid. Make sure
|
|
|
|
that you are aware of the dangers.
|
2017-04-16 17:20:02 +00:00
|
|
|
|
2019-01-16 23:52:09 +00:00
|
|
|
-m::
|
|
|
|
(since kernel: 5.0)
|
|
|
|
+
|
|
|
|
change fsid stored as 'metadata_uuid' to a randomly generated UUID,
|
|
|
|
see also '-U'
|
|
|
|
|
|
|
|
-M <UUID>::
|
|
|
|
(since kernel: 5.0)
|
|
|
|
+
|
|
|
|
change fsid stored as 'metadata_uuid' to a given UUID, see also '-U'
|
|
|
|
+
|
|
|
|
The metadata_uuid is stored only in the superblock and is a backward
|
|
|
|
incompatible change. The fsid in metadata blocks remains unchanged and
|
|
|
|
is not overwritten, thus the whole operation is significantly faster than
|
|
|
|
'-U'.
|
|
|
|
+
|
|
|
|
The new metadata_uuid can be used for mount by UUID and is also used to
|
|
|
|
identify devices of a multi-device filesystem.
|
|
|
|
|
2015-06-02 16:41:01 +00:00
|
|
|
-n::
|
2016-09-01 16:51:18 +00:00
|
|
|
(since kernel: 3.14)
|
|
|
|
+
|
2015-11-02 10:08:57 +00:00
|
|
|
Enable no-holes feature (more efficient representation of file holes), enabled
|
2016-09-01 16:51:18 +00:00
|
|
|
by mkfs feature 'no-holes'.
|
2017-04-16 17:20:02 +00:00
|
|
|
|
2019-01-16 23:33:08 +00:00
|
|
|
-r::
|
|
|
|
(since kernel: 3.7)
|
|
|
|
+
|
|
|
|
Enable extended inode refs (hardlink limit per file in a directory is 65536),
|
|
|
|
enabled by mkfs feature 'extref'.
|
|
|
|
|
|
|
|
-S <0|1>::
|
|
|
|
Enable seeding on a given device. Value 1 will enable seeding, 0 will disable it. +
|
|
|
|
A seeding filesystem is forced to be mounted read-only. A new device can be added
|
|
|
|
to the filesystem and will capture all writes keeping the seeding device intact.
|
|
|
|
+
|
|
|
|
WARNING: Clearing the seeding flag on a device may be dangerous.
|
|
|
|
If a previously-seeding device is changed, all filesystems that used that
|
|
|
|
device will become unmountable. Setting the seeding flag back will not fix
|
|
|
|
that. +
|
|
|
|
A valid usecase is 'seeding device as a base image'. Clear the seeding
|
|
|
|
flag, update the filesystem and make it seeding again, provided that it's OK
|
|
|
|
to throw away all filesystems built on top of the previous base.
|
2017-04-16 17:20:02 +00:00
|
|
|
|
2015-05-15 06:28:26 +00:00
|
|
|
-u::
|
2015-06-02 17:34:40 +00:00
|
|
|
Change fsid to a randomly generated UUID or continue previous fsid change
|
|
|
|
operation in case it was interrupted.
|
2017-04-16 17:20:02 +00:00
|
|
|
|
2015-05-15 06:28:26 +00:00
|
|
|
-U <UUID>::
|
2019-01-16 23:52:09 +00:00
|
|
|
Change fsid to 'UUID' in all metadata blocks.
|
2015-05-15 06:28:26 +00:00
|
|
|
+
|
2015-11-02 10:08:57 +00:00
|
|
|
The 'UUID' should be a 36 bytes string in `printf`(3) format
|
|
|
|
'"%08x-%04x-%04x-%04x-%012x"'.
|
2015-06-02 17:34:40 +00:00
|
|
|
If there is a previous unfinished fsid change, it will continue only if the
|
2015-11-02 10:08:57 +00:00
|
|
|
'UUID' matches the unfinished one or if you use the option '-u'.
|
2019-01-16 23:33:08 +00:00
|
|
|
+
|
2019-01-16 23:52:09 +00:00
|
|
|
All metadata blocks are rewritten, this may take some time, but the final
|
|
|
|
filesystem compatibility is unaffected, unlike '-M'.
|
|
|
|
+
|
2015-05-15 06:28:26 +00:00
|
|
|
WARNING: Cancelling or interrupting a UUID change operation will make the
|
2019-01-16 23:52:09 +00:00
|
|
|
filesystem temporarily unmountable. To fix it, rerun 'btrfstune -u' and let
|
|
|
|
it complete.
|
2014-04-02 08:29:34 +00:00
|
|
|
|
2019-01-16 23:33:08 +00:00
|
|
|
-x::
|
|
|
|
(since kernel: 3.10)
|
|
|
|
+
|
|
|
|
Enable skinny metadata extent refs (more efficient representation of extents),
|
|
|
|
enabled by mkfs feature 'skinny-metadata'.
|
|
|
|
+
|
|
|
|
All newly created extents will use the new representation. To completely switch
|
|
|
|
the entire filesystem, run a full balance of the metadata. Please refer to
|
|
|
|
`btrfs-balance`(8).
|
2014-04-02 08:29:34 +00:00
|
|
|
|
|
|
|
EXIT STATUS
|
|
|
|
-----------
|
2015-06-02 17:34:40 +00:00
|
|
|
*btrfstune* returns 0 if no error happened, 1 otherwise.
|
|
|
|
|
|
|
|
COMPATIBILITY NOTE
|
|
|
|
------------------
|
2017-12-07 20:26:09 +00:00
|
|
|
|
|
|
|
This deprecated tool exists for historical reasons but is still in use today.
|
|
|
|
Its functionality will be merged to the main tool, at which time *btrfstune*
|
|
|
|
will be declared obsolete and scheduled for removal.
|
2014-04-02 08:29:34 +00:00
|
|
|
|
|
|
|
SEE ALSO
|
|
|
|
--------
|
2016-09-01 16:51:18 +00:00
|
|
|
`btrfs`(5),
|
|
|
|
`btrfs-balance`(8),
|
2014-04-02 08:29:34 +00:00
|
|
|
`mkfs.btrfs`(8)
|