2014-04-02 08:29:25 +00:00
|
|
|
btrfs-replace(8)
|
|
|
|
|
===============
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
|
|
|
|
btrfs-replace - replace devices managed by btrfs with other device.
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2014-05-19 15:49:35 +00:00
|
|
|
*btrfs replace* <subcommand> <args>
|
2014-04-02 08:29:25 +00:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2014-05-19 15:49:35 +00:00
|
|
|
*btrfs replace* is used to replace btrfs managed devices with other device.
|
2014-04-02 08:29:25 +00:00
|
|
|
|
|
|
|
|
SUBCOMMAND
|
|
|
|
|
----------
|
2015-01-03 01:20:50 +00:00
|
|
|
*cancel* <mount_point>::
|
|
|
|
|
Cancel a running device replace operation.
|
|
|
|
|
|
2014-05-19 15:49:35 +00:00
|
|
|
*start* [-Bfr] <srcdev>|<devid> <targetdev> <path>::
|
2014-04-02 08:29:25 +00:00
|
|
|
Replace device of a btrfs filesystem.
|
|
|
|
|
+
|
|
|
|
|
On a live filesystem, duplicate the data to the target device which
|
|
|
|
|
is currently stored on the source device.
|
|
|
|
|
If the source device is not available anymore, or if the -r option is set,
|
|
|
|
|
the data is built only using the RAID redundancy mechanisms.
|
|
|
|
|
After completion of the operation, the source device is removed from the
|
|
|
|
|
filesystem.
|
|
|
|
|
If the <srcdev> is a numerical value, it is assumed to be the device id
|
|
|
|
|
of the filesystem which is mounted at <path>, otherwise is is
|
|
|
|
|
the path to the source device. If the source device is disconnected,
|
|
|
|
|
from the system, you have to use the devid parameter format.
|
|
|
|
|
The <targetdev> needs to be same size or larger than the <srcdev>.
|
|
|
|
|
+
|
2016-02-28 21:11:54 +00:00
|
|
|
NOTE: the filesystem has to be resized to fully take advantage of a
|
|
|
|
|
larger target device, this can be achieved with
|
|
|
|
|
`btrfs filesystem resize <devid>:max /path`
|
|
|
|
|
+
|
2014-04-02 08:29:25 +00:00
|
|
|
`Options`
|
|
|
|
|
+
|
|
|
|
|
-r::::
|
|
|
|
|
only read from <srcdev> if no other zero-defect mirror exists.
|
|
|
|
|
(enable this if your drive has lots of read errors, the access would be very
|
|
|
|
|
slow)
|
|
|
|
|
-f::::
|
|
|
|
|
force using and overwriting <targetdev> even if it looks like
|
|
|
|
|
containing a valid btrfs filesystem.
|
|
|
|
|
+
|
|
|
|
|
A valid filesystem is assumed if a btrfs superblock is found which contains a
|
|
|
|
|
correct checksum. Devices which are currently mounted are
|
|
|
|
|
never allowed to be used as the <targetdev>.
|
2015-01-08 02:40:53 +00:00
|
|
|
+
|
2014-04-02 08:29:25 +00:00
|
|
|
-B::::
|
|
|
|
|
no background replace.
|
|
|
|
|
|
2014-05-19 15:49:35 +00:00
|
|
|
*status* [-1] <mount_point>::
|
2014-04-02 08:29:25 +00:00
|
|
|
Print status and progress information of a running device replace operation.
|
|
|
|
|
+
|
|
|
|
|
`Options`
|
|
|
|
|
+
|
|
|
|
|
-1::::
|
|
|
|
|
print once instead of print continuously until the replace
|
2016-03-14 13:10:16 +00:00
|
|
|
operation finishes (or is cancelled)
|
2014-04-02 08:29:25 +00:00
|
|
|
|
|
|
|
|
EXIT STATUS
|
|
|
|
|
-----------
|
2014-09-19 01:49:59 +00:00
|
|
|
*btrfs replace* returns a zero exit status if it succeeds. Non zero is
|
2014-04-02 08:29:25 +00:00
|
|
|
returned in case of failure.
|
|
|
|
|
|
|
|
|
|
AVAILABILITY
|
|
|
|
|
------------
|
2014-05-19 16:04:26 +00:00
|
|
|
*btrfs* is part of btrfs-progs.
|
2014-04-02 08:29:25 +00:00
|
|
|
Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
|
|
|
|
|
further details.
|
|
|
|
|
|
|
|
|
|
SEE ALSO
|
|
|
|
|
--------
|
|
|
|
|
`mkfs.btrfs`(8),
|
2014-04-11 02:43:52 +00:00
|
|
|
`btrfs-device`(8),
|
