summaryrefslogtreecommitdiff
path: root/btrfstune.c
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@redhat.com>2014-05-15 19:14:40 +0200
committerDavid Sterba <dsterba@suse.cz>2014-08-22 14:39:32 +0200
commit7165d9024df628593a6c6fe9fe50d02547105afc (patch)
tree7ebddd551863ac3ec64e95d5dd501f4fe8d2dd0d /btrfstune.c
parent834b85e9f6753d61d4c0990545de77f0f3dbf6a1 (diff)
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 <sandeen@redhat.com> [converted to asciidoc] Signed-off-by: David Sterba <dsterba@suse.cz>
Diffstat (limited to 'btrfstune.c')
0 files changed, 0 insertions, 0 deletions