From 7165d9024df628593a6c6fe9fe50d02547105afc Mon Sep 17 00:00:00 2001 From: Eric Sandeen Date: Thu, 15 May 2014 19:14:40 +0200 Subject: [PATCH] btrfs-progs: clarify mkfs.btrfs --alloc-start option Fedora had a bug where a poor user thought that --alloc-start meant that the filesystem would be created at that offset into the device, rather than just starting allocations at that offset. A subtle difference, but worth clarifying, because the manpage is misleading on this point. The original commit log for this option says: Add mkfs.btrfs -A offset to control allocation start on devices This is a utility option for the resizer, it makes sure to allocate at offset bytes in the disk or higher. It ensures the resizer will have something to move when testing it. so allude to that intended use in the manpage. Signed-off-by: Eric Sandeen [converted to asciidoc] Signed-off-by: David Sterba --- Documentation/mkfs.btrfs.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Documentation/mkfs.btrfs.txt b/Documentation/mkfs.btrfs.txt index 0cab626..c6becb9 100644 --- a/Documentation/mkfs.btrfs.txt +++ b/Documentation/mkfs.btrfs.txt @@ -39,7 +39,10 @@ spanning across the specified devices. OPTIONS ------- -A|--alloc-start :: -Specify the offset from the start of the device to start the btrfs filesystem. The default value is zero, or the start of the device. +Specify the offset from the start of the device at which to start allocations +in this btrfs filesystem. The default value is zero, or the start of the +device. This option is intended only for debugging filesystem resize +operations. -b|--byte-count :: Specify the size of the resultant filesystem. If this option is not used, -- 2.7.4