From: Juan Francisco Cantero Hurtado <iam@juanfra.info>
To: linux-btrfs@vger.kernel.org
Subject: mkfs.btrfs(8) --data outdated?
Date: Sun, 27 Sep 2015 22:33:01 +0200 [thread overview]
Message-ID: <mu9jpv$l25$1@ger.gmane.org> (raw)
kernel: 4.1.7
btrfs-progs: 4.2
mkfs.btrfs(8) man page says:
-d|--data <type>
Specify how the data must be spanned across the devices
specified. Valid values are raid0, raid1, raid5, raid6,
raid10 or single.
$ sudo mkfs.btrfs -d dup -m dup -M -O no-holes -f /dev/sdb1
SMALL VOLUME: forcing mixed metadata/data groups
btrfs-progs v4.2
See http://btrfs.wiki.kernel.org for more information.
Label: (null)
UUID: 29de8c3e-92da-4fe1-aa31-830c1068f532
Node size: 4096
Sector size: 4096
Filesystem size: 3.00GiB
Block group profiles:
Data+Metadata: DUP 161.56MiB
System: DUP 12.00MiB
SSD detected: no
Incompat features: mixed-bg, extref, skinny-metadata, no-holes
Number of devices: 1
Devices:
ID SIZE PATH
1 3.00GiB /dev/sdb1
The man page doesn't mention the option "-d dup". Am I missing something
or the man page is outdated?. The partition will contain two copies of
the data blocks?
next reply other threads:[~2015-09-27 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 20:33 Juan Francisco Cantero Hurtado [this message]
2015-09-28 1:22 ` mkfs.btrfs(8) --data outdated? Qu Wenruo
2015-09-29 11:40 ` David Sterba
2015-09-28 2:19 ` Duncan
2015-09-28 21:53 ` Juan Francisco Cantero Hurtado
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mu9jpv$l25$1@ger.gmane.org' \
--to=iam@juanfra.info \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.