Although btrfs-convert can rollback converted btrfs, it still has some limitation to ensure rollback.
Add a warning on the limitations. Also add a note for users who decides to go on with btrfs and don't need the rollback ability. Reported-by: Vytautas D <vyt...@gmail.com> Reported-by: Tsutomu Itoh <t-i...@jp.fujitsu.com> Signed-off-by: Qu Wenruo <quwen...@cn.fujitsu.com> --- v2: Add reporter tags v3: Remove 'btrfs fi defrag' from commands that may disable rollback ability. Add a little explain to make the warning more reasonable. --- Documentation/btrfs-convert.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/btrfs-convert.txt b/Documentation/btrfs-convert.txt index 8b3f05b..b57af73 100644 --- a/Documentation/btrfs-convert.txt +++ b/Documentation/btrfs-convert.txt @@ -15,6 +15,16 @@ DESCRIPTION and the original filesystem image is accessible as from separate subvolume named 'ext2_saved' as file image. +WARNING: If one hopes to rollback to ext2/3/4, he or she should not execute +*btrfs balance* command on converted btrfs. +Since it will change the extent layout and make *btrfs-convert* unable to +rollback. + +NOTE: If one is satisfied with converted btrfs, and not longer wants to +rollback to ext2/3/4, it is highly recommended to remove 'ext2_saved' subvolume +and execute *btrfs filesystem defragment* and *btrfs balance* command on the +converted btrfs. + OPTIONS ------- -d|--no-datasum:: -- 2.3.5 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
