|author||Josef Bacik <firstname.lastname@example.org>||2013-01-19 13:06:21 -0500|
|committer||David Sterba <email@example.com>||2013-01-23 19:32:30 +0100|
Btrfs-progs: detect if the disk we are formatting is a ssd
Patch rebased because of changes in mkfs.c but otherwise the same as created by Josef Bacik SSD's do not gain anything by having metadata DUP turned on. The underlying file system that is a part of all SSD's could easily map duplicate metadat blocks into the same erase block which effectively eliminates the benefit of duplicating the metadata on disk. So detect if we are formatting a single SSD drive and if we are do not use DUP. Thanks, Signed-off-by: Josef Bacik <firstname.lastname@example.org> Signed-off-by: Gene Czarcinski <email@example.com>
Diffstat (limited to 'man')
1 files changed, 4 insertions, 1 deletions
diff --git a/man/mkfs.btrfs.8.in b/man/mkfs.btrfs.8.in
index 72025ed7..b7bcc1b2 100644
@@ -47,7 +47,10 @@ Specify a label for the filesystem.
\fB\-m\fR, \fB\-\-metadata \fIprofile\fR
Specify how metadata must be spanned across the devices specified. Valid
-values are raid0, raid1, raid10 or single.
+values are raid0, raid1, raid10, single or dup. Single device will have dup
+set by default except in the case of SSDs which will default to single. This is
+because SSDs can remap blocks internally so duplicate blocks could end up in the
+same erase block which negates the benefits of doing metadata duplication.
Mix data and metadata chunks together for more efficient space