On Fri, 2017-04-28 at 17:35 -0700, Dan Williams wrote:
> On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams om> wrote:
> > On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams > .com> wrote:
> > > On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani
On Fri, 2017-04-28 at 17:35 -0700, Dan Williams wrote:
> On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams om> wrote:
> > On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams > .com> wrote:
> > > On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani
> > > wrote:
> > > > Badblocks are tracked at both region and
On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams wrote:
> On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams
> wrote:
>> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
>>> Badblocks are tracked at both region and device
On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams wrote:
> On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams
> wrote:
>> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
>>> Badblocks are tracked at both region and device levels.
>>> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams wrote:
> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
>> Badblocks are tracked at both region and device levels.
>> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
>> and then
On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams wrote:
> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
>> Badblocks are tracked at both region and device levels.
>> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
>> and then badblocks_clear() to clear badblocks at the
On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
> Badblocks are tracked at both region and device levels.
> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
> and then badblocks_clear() to clear badblocks at the device level.
> However, it does not update
On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
> Badblocks are tracked at both region and device levels.
> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
> and then badblocks_clear() to clear badblocks at the device level.
> However, it does not update badblocks at the
Badblocks are tracked at both region and device levels.
pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
and then badblocks_clear() to clear badblocks at the device level.
However, it does not update badblocks at the region level, which
makes them inconsistent.
Change
Badblocks are tracked at both region and device levels.
pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
and then badblocks_clear() to clear badblocks at the device level.
However, it does not update badblocks at the region level, which
makes them inconsistent.
Change
10 matches
Mail list logo