All of lore.kernel.org
 help / color / mirror / Atom feed
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 2/2] ndctl: add list --media-errors support
Date: Wed, 10 May 2017 20:57:33 +0000	[thread overview]
Message-ID: <1494449841.30303.80.camel@hpe.com> (raw)
In-Reply-To: <e2873152-d765-4bcd-40c8-2f8caaa72803@intel.com>

On Wed, 2017-05-10 at 12:56 -0700, Dave Jiang wrote:
> 
> On 05/10/2017 11:43 AM, Kani, Toshimitsu wrote:
> > On Wed, 2017-05-10 at 11:03 -0700, Dave Jiang wrote:
> > > ACPI NFIT enabled platforms provide media errors as absolute
> > > phyiscal
> > > address offsets. Add an option to ndctl to display those media
> > > errors
> > > tranlsated to region and namespace device level offsets in an
> > > "ndctl
> > > list" listing.
> > > 
> > > Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> > > ---
> > > 
> > > v2: added fix to badblocks display from Toshi's testing result.
> > > v3: fixed naming issues from Dan's comments.
> > >     fixed badblocks boundary offset calculations from Toshi's
> > > testing.
> > 
> > Thanks for the quick update.  This version works nicely for dax and
> > memory modes.  Is there particular reason why it does not list
> > errors for raw and sector modes?
> 
> So it should work for raw AFAICT. Dan said the BTT ones don't make
> sense because the namespace relative offset is dynamic.
> 
> 
> # ./ndctl/ndctl list -NM
> [
>   {
>     "dev":"namespace5.0",
>     "mode":"raw",
>     "size":33554432,
>     "uuid":"bb3539dd-065c-41bd-8bcc-dc3bbc3317a5",
>     "badblocks":[
>       {
>         "offset":4,
>         "length":1
>       },
>       {
>         "offset":32768,
>         "length":8
>       },
>       {
>         "offset":65528,
>         "length":8
>       }
>     ],
>     "blockdev":"pmem5"
>   },

Attached "strace.log".  Note, there is no reference to "badblocks"
files in the log.

I agree that offsets do not make sense for BTT, but it leads to a false
impression that there is no error.  Perhaps, we can remove "offset" or
put "n/a" for BTT.  

Thanks,
-Toshi


_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2017-05-10 20:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 18:01 [PATCH v3 1/2] ndctl: add foreach helper for region badblocks in libndctl Dave Jiang
2017-05-10 18:03 ` [PATCH v3 2/2] ndctl: add list --media-errors support Dave Jiang
2017-05-10 18:43   ` Kani, Toshimitsu
2017-05-10 19:56     ` Dave Jiang
2017-05-10 20:57       ` Kani, Toshimitsu [this message]
2017-05-10 21:13         ` Dave Jiang
2017-05-10 21:28           ` Kani, Toshimitsu
2017-05-10 21:34             ` Dave Jiang
2017-05-10 21:47               ` Kani, Toshimitsu
2017-05-10 22:07                 ` Dan Williams
2017-05-10 22:24           ` Dan Williams
2017-05-10 22:33             ` Kani, Toshimitsu
2017-05-10 22:32 ` [PATCH v3 1/2] ndctl: add foreach helper for region badblocks in libndctl Vishal Verma

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=1494449841.30303.80.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 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.