X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=Documentation%2Fbtrfs-replace.asciidoc;h=bc73b0b7ac20ae23c661fe0ed58885d6aaa9b99d;hb=82a1442e9cd025436be8ae65e684fd6b2701efbb;hp=a259f96d4e2e0d89107a93b31e4876e1b71355c6;hpb=5f17513313ddd39d4348b382cf2224dbf4d35e7b;p=platform%2Fupstream%2Fbtrfs-progs.git diff --git a/Documentation/btrfs-replace.asciidoc b/Documentation/btrfs-replace.asciidoc index a259f96..bc73b0b 100644 --- a/Documentation/btrfs-replace.asciidoc +++ b/Documentation/btrfs-replace.asciidoc @@ -1,5 +1,5 @@ btrfs-replace(8) -=============== +================ NAME ---- @@ -28,13 +28,13 @@ 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 is a numerical value, it is assumed to be the device id -of the filesystem which is mounted at , otherwise is is +of the filesystem which is mounted at , otherwise it 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 needs to be same size or larger than the . + NOTE: the filesystem has to be resized to fully take advantage of a -larger target device, this can be achieved with +larger target device; this can be achieved with `btrfs filesystem resize :max /path` + `Options` @@ -45,10 +45,10 @@ only read from if no other zero-defect mirror exists. slow) -f:::: force using and overwriting even if it looks like -containing a valid btrfs filesystem. +it contains 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 +correct checksum. Devices that are currently mounted are never allowed to be used as the . + -B::::