From patchwork Mon Apr 30 19:45:20 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Luis Chamberlain X-Patchwork-Id: 10372469 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id E25D76053E for ; Mon, 30 Apr 2018 19:45:30 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id D46E8288DB for ; Mon, 30 Apr 2018 19:45:30 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id C68CB288FE; Mon, 30 Apr 2018 19:45:30 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00, MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=unavailable version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 8B236288FE for ; Mon, 30 Apr 2018 19:45:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932298AbeD3Tp0 (ORCPT ); Mon, 30 Apr 2018 15:45:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:42894 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756365AbeD3TpY (ORCPT ); Mon, 30 Apr 2018 15:45:24 -0400 Received: from garbanzo.do-not-panic.com (c-73-15-241-2.hsd1.ca.comcast.net [73.15.241.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DCA5D21875; Mon, 30 Apr 2018 19:45:23 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DCA5D21875 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=mcgrof@kernel.org From: "Luis R. Rodriguez" To: damien.lemoal@wdc.com Cc: hare@suse.de, linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org, "Luis R. Rodriguez" Subject: [PATCH dm-zoned-tools 2/2] README: fix example script Date: Mon, 30 Apr 2018 12:45:20 -0700 Message-Id: <20180430194520.9065-2-mcgrof@kernel.org> X-Mailer: git-send-email 2.17.0 In-Reply-To: <20180430194520.9065-1-mcgrof@kernel.org> References: <20180430194520.9065-1-mcgrof@kernel.org> Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP The target type should be "zoned", not "dm-zoned". Signed-off-by: Luis R. Rodriguez Reviewed-by: Damien Le Moal --- 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}` ]]