[lkml]   [2018]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v3 0/3] nfit, address-range-scrub: rework and fixes
Changes since v2 [1]:
* Handle -EAGAIN (no result) ars_status responses


Given the fact that ARS can take 10s to 100s of seconds it is not
feasible to wait for ARS completion before publishing persistent memory
namespaces. Instead convert the ARS implementation to perform a short
ARS for critical errors, ones that caused a previous system reset,
before registering namespaces. Finally, arrange for all long ARS
operations to run in the background and populate the badblock lists at
run time.

In the extreme situation that an implementation is unable to return
sufficient results in a short scan and the system encounters media
errors that machine check recovery does not handle, an administrator can
arrange to wait for a full ARS scan by doing the following:

1/ Boot with "modprobe.blacklist=nd_pmem" to stop pmem namespaces from
starting automatically

2/ Call "ndctl wait-scrub" to wait for the OS or BIOS initiated ARS to complete

3/ Manually start up namespaces with the up to date error list
"modprobe nd_pmem"


Dan Williams (3):
nfit, address-range-scrub: determine one platform max_ars value
nfit, address-range-scrub: rework and simplify ARS state machine
nfit, address-range-scrub: add module option to skip initial ars

drivers/acpi/nfit/core.c | 557 +++++++++++++++++++++-------------------------
drivers/acpi/nfit/nfit.h | 6
2 files changed, 261 insertions(+), 302 deletions(-)

 \ /
  Last update: 2018-04-07 17:56    [W:0.028 / U:3.616 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site