From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"dave.jiang@intel.com" <dave.jiang@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v3] ndctl: add clear error support for ndctl
Date: Mon, 1 May 2017 22:06:10 +0000 [thread overview]
Message-ID: <1493676369.30303.30.camel@hpe.com> (raw)
In-Reply-To: <149367376823.14721.16804310177322088175.stgit@djiang5-desk3.ch.intel.com>
On Mon, 2017-05-01 at 14:23 -0700, Dave Jiang wrote:
:
> +++ b/Documentation/ndctl-clear-error.txt
> @@ -0,0 +1,37 @@
> +ndctl-clear-error(1)
> +====================
> +
> +NAME
> +----
> +ndctl-clear-error - clear badblocks for a device
> +
> +SYNOPSIS
> +--------
> +[verse]
> +'ndctl clear-error' [<options>]
> +
> +EXAMPLES
> +--------
> +
> +Clear poison (bad blocks) for the provided device
> +[verse]
> +ndctl clear-error -f /dev/dax0.0 -s 0 -l 8
> +
> +Clear poison (bad blocks) at block offset 0 for 8 blocks on device
> /dev/dax0.0
> +
> +OPTIONS
> +-------
> +-f::
> +--file::
> + The device/file to be cleared of poison (bad blocks).
> +
> +-s::
> +--start::
> + The offset where the poison (bad block) starts for this
> device.
> + Typically this is acquired from the sysfs badblocks file.
> +
> +-l::
> +--len::
> + The number of badblocks to clear in size of 512 bytes
> increments.
> +
When a specified range is larger than a badblock range, the command
completes with no-op without any message. I think it should either
fail with an error message or clear an inclusive badblock.
Thanks,
-Toshi
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-05-01 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 21:23 [PATCH v3] ndctl: add clear error support for ndctl Dave Jiang
2017-05-01 22:06 ` Kani, Toshimitsu [this message]
2017-05-01 22:16 ` Dave Jiang
2017-05-01 22:28 ` Kani, Toshimitsu
2017-05-01 22:41 ` Jiang, Dave
2017-05-01 23:06 ` Kani, Toshimitsu
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=1493676369.30303.30.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-nvdimm@lists.01.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