btrfs-progs: docs: clarify potential problems with convert
Add a note summarizing the problems. [ci skip] Issue: #257 Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
parent
93cdc1c2fc
commit
f5db48e053
|
@ -33,6 +33,13 @@ have a supported data block size (i.e. the same that would be valid for
|
||||||
:command:`mkfs.btrfs`). This is typically the system page size (4KiB on x86_64
|
:command:`mkfs.btrfs`). This is typically the system page size (4KiB on x86_64
|
||||||
machines).
|
machines).
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Always consider if a mkfs and file copy would not be a better option than
|
||||||
|
the in-place conversion given what was said above. The conversion depends on
|
||||||
|
3rd party libraries and the other filesystems could still evolve and add new
|
||||||
|
features. Not all combinations are covered or tested.
|
||||||
|
|
||||||
**BEFORE YOU START**
|
**BEFORE YOU START**
|
||||||
|
|
||||||
The source filesystem must be clean, e.g. no journal to replay or no repairs
|
The source filesystem must be clean, e.g. no journal to replay or no repairs
|
||||||
|
|
Loading…
Reference in New Issue