summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorGui Hecheng <guihc.fnst@cn.fujitsu.com>2014-07-07 09:54:53 +0800
committerDavid Sterba <dsterba@suse.cz>2014-10-01 16:34:05 +0200
commit7ab92a3e685d7a301df4e9e685f3809f648987b7 (patch)
tree2ca5434fd8fa54db3a5da6940d6ded06118ba9c7 /Documentation
parent5eb89fb10927796128cc2d2561b84f9026d855f0 (diff)
btrfs-progs: update manpage with new option -f for btrfstune
The new option -f will force to do dangerous changes. e.g. clear the seeding flag. Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com> [more text from 3db4c0a3d35dd5f8 changelog] Signed-off-by: David Sterba <dsterba@suse.cz>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/btrfstune.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/btrfstune.txt b/Documentation/btrfstune.txt
index 56cf66bb..d49a9742 100644
--- a/Documentation/btrfstune.txt
+++ b/Documentation/btrfstune.txt
@@ -24,7 +24,14 @@ Enable seeding forces a fs readonly so that you can use it to build other filesy
Enable extended inode refs.
-x::
Enable skinny metadata extent refs.
+-f::
+Allow dangerous changes, e.g. clear the seeding flag
+When mounting the new device, btrfs will check whether the seeding flag is set
+when try to open seeding device. If the user clears the seeding flag of the
+seeding device, the new device will not be mountable. Even setting the seeding
+flag back will not fix this problem, because the generation will be changed at
+that time. Clear the seeding flag may damage the new filesystem.
EXIT STATUS
-----------