From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v4 2/2] ndctl: add list --media-errors support
Date: Thu, 11 May 2017 15:55:19 +0000 [thread overview]
Message-ID: <1494518108.30303.90.camel@hpe.com> (raw)
In-Reply-To: <CAPcyv4iTF0S1JgqTc04CJRkO7243AmNyr_kiPhPZq9a5+LLT-g@mail.gmail.com>
On Thu, 2017-05-11 at 08:39 -0700, Dan Williams wrote:
> On Thu, May 11, 2017 at 8:31 AM, Kani, Toshimitsu <toshi.kani@hpe.com
> > wrote:
> > On Wed, 2017-05-10 at 16:57 -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. BTT badblocks show is not
> > > supported in this iteration and will come later.
> > >
> > > 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.
> > > v4: Add indicator to show badblocks exist or not, per Toshi's
> > > comments.
> >
> > This version works pretty good, except that it does not show
> > "has_badblocks" for sector mode.
> >
> > # ndctl list -M -m sector
> > {
> > "dev":"namespace0.0",
> > "mode":"sector",
> > "size":17162027008,
> > "uuid":"7742dff3-3edd-4a28-894d-9ac1aede6b2c",
> > "sector_size":4096,
> > "blockdev":"pmem0s"
> > }
>
> Since we're going to spin the patch to fix this up... Toshi, what do
> you think about changing "has_badblocks" to "badblock_count". My
> concern is that for the btt case it will also count badblocks that
> are on the free list or in metadata, but it at least gives you a
> better indication of the damage level of the underlying namespace.
Good idea. Yes, I like "badblock_count" better.
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-11 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 23:56 [PATCH v4 1/2] ndctl: add foreach helper for region badblocks in libndctl Dave Jiang
2017-05-10 23:57 ` [PATCH v4 2/2] ndctl: add list --media-errors support Dave Jiang
2017-05-11 15:31 ` Kani, Toshimitsu
2017-05-11 15:39 ` Dan Williams
2017-05-11 15:55 ` Kani, Toshimitsu [this message]
2017-05-11 16:09 ` Dave Jiang
2017-05-11 16:12 ` Dan Williams
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=1494518108.30303.90.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=dan.j.williams@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.