nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Dorau, Lukasz" <lukasz.dorau@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "Li, ZhijianX" <zhijianx.li@intel.com>, Slusarz,,
	"Piotr  <piotr.balcer@intel.com>,
	linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: RE: [BUG] Injecting bad blocks in the nfit_test module does not work with kernel v4.17.4 + ndctl v61.1
Date: Thu, 5 Jul 2018 07:51:25 +0000	[thread overview]
Message-ID: <D9FFE20C522965449E182ACE73889AEBF4F2E4A2@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <CAPcyv4gw12anx4tFqG1zeFjS-Be8kxVgXDqNHE5U4eES-=UOBQ@mail.gmail.com>

On Wed, July 4, 2018 4:33 PM, Dan Williams <dan.j.williams@intel.com> wrote:
> On Wed, Jul 4, 2018 at 5:45 AM, Dorau, Lukasz <lukasz.dorau@intel.com> wrote:
> > Hi,
> >
> >
> >
> > This is a bug report:  injecting bad blocks in the nfit_test module does not
> > work with the kernel v4.17.4 (the latest stable at this moment) and ndctl
> > v61.1:
> >
> 
> Sorry, yes, this is a known issue. There is no fix on the near
> horizon, this is a casualty of the ARS rework we did in the kernel
> between v4.16 and v4.17. More details here:
> 
> https://github.com/pmem/issues/issues/897#issuecomment-402495154
>

Hi Dan,

Thanks for the fast reply and the explanation.

I tested the workaround (ndctl start-scrub ; ndctl wait-scrub) but it does not work for me (with kernel v4.17.4 and ndctl v61.1):

# ndctl inject-error --block=16838 --count=512 namespace4.0
# ndctl start-scrub
# ndctl wait-scrub      #       <---       I waited 30 minutes for 'ndctl wait-scrub', but it did not finish...

--
Lukasz


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

  reply	other threads:[~2018-07-05  7:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04 12:45 [BUG] Injecting bad blocks in the nfit_test module does not work with kernel v4.17.4 + ndctl v61.1 Dorau, Lukasz
2018-07-04 14:32 ` Dan Williams
2018-07-05  7:51   ` Dorau, Lukasz [this message]
2018-07-05  8:29   ` Dorau, Lukasz
2018-07-05 10:54     ` Dorau, Lukasz
2018-07-05 16:57     ` Verma, Vishal L

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=D9FFE20C522965449E182ACE73889AEBF4F2E4A2@IRSMSX101.ger.corp.intel.com \
    --to=lukasz.dorau@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=zhijianx.li@intel.com \
    /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).