linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: damien.lemoal@wdc.com
Cc: hare@suse.de, linux-fsdevel@vger.kernel.org,
	linux-block@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: [PATCH dm-zoned-tools 2/2] README: fix example script
Date: Mon, 30 Apr 2018 12:45:20 -0700	[thread overview]
Message-ID: <20180430194520.9065-2-mcgrof@kernel.org> (raw)
In-Reply-To: <20180430194520.9065-1-mcgrof@kernel.org>

The target type should be "zoned", not "dm-zoned".

Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

The README does note explain if one should use dmzadm to format a drive
if using dm zone or only if one is to use a filesystem which supports
zones, such as f2fs. Or if we should *always* use dmzadm format regardless
of the circumstance.

Could this be clarfied? What are the downsides to not using dmzadm
format on a drive and say a user just going straight to use the dm zone
and then mkfs on top of it?

diff --git a/README b/README
index 7762694..9aea28e 100644
--- a/README
+++ b/README
@@ -184,7 +184,7 @@ options="$@"
 
 modprobe dm-zoned
 
-echo "0 `blockdev --getsize ${dev}` dm-zoned ${dev} ${options}" | \
+echo "0 `blockdev --getsize ${dev}` zoned ${dev} ${options}" | \
 dmsetup create zoned-`basename ${dev}`
 ]]
 
-- 
2.17.0

  reply	other threads:[~2018-04-30 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 19:45 [PATCH dm-zoned-tools 1/2] README: fix small typo host-manmaged --> host-managed Luis R. Rodriguez
2018-04-30 19:45 ` Luis R. Rodriguez [this message]
2018-04-30 20:36   ` [PATCH dm-zoned-tools 2/2] README: fix example script Damien Le Moal
2018-04-30 22:04     ` Luis R. Rodriguez
2018-04-30 20:32 ` [PATCH dm-zoned-tools 1/2] README: fix small typo host-manmaged --> host-managed Damien Le Moal

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=20180430194520.9065-2-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=damien.lemoal@wdc.com \
    --cc=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).