On 01/24, Jan Kara wrote:
> On Fri 20-01-17 07:42:09, Dan Williams wrote:
> > On Fri, Jan 20, 2017 at 1:47 AM, Jan Kara <j...@suse.cz> wrote:
> > > On Thu 19-01-17 14:17:19, Vishal Verma wrote:
> > >> On 01/18, Jan Kara wrote:
> > >> > On Tue 17-0
diry Xu <and...@gmail.com> wrote:
>
> > On Tue, Jan 17, 2017 at 4:16 PM, Andreas Dilger <adil...@dilger.ca> wrote:
> > > On Jan 17, 2017, at 3:15 PM, Andiry Xu <and...@gmail.com> wrote:
> > >> On Tue, Jan 17, 2017 at 1:35 PM, Vishal Verma <vishal.l.ve.
On 01/18, Jan Kara wrote:
> On Tue 17-01-17 15:37:05, Vishal Verma wrote:
> > I do mean that in the filesystem, for every IO, the badblocks will be
> > checked. Currently, the pmem driver does this, and the hope is that the
> > filesystem can do a better job at it. The d
8, 2017 at 03:39:17PM -0500, Jeff Moyer wrote:
> > > > > Jan Kara <j...@suse.cz> writes:
> > > > >
> > > > > > On Tue 17-01-17 15:14:21, Vishal Verma wrote:
> > > > > > > Your note on the online repair does rai
On 01/17, Andiry Xu wrote:
> >>
> >> The pmem_do_bvec() read logic is like this:
> >>
> >> pmem_do_bvec()
> >> if (is_bad_pmem())
> >> return -EIO;
> >> else
> >> memcpy_from_pmem();
> >>
> >> Note memcpy_from_pmem() is calling memcpy_mcsafe(). Does this imply
> >> that
On 01/17, Jan Kara wrote:
> On Mon 16-01-17 02:27:52, Slava Dubeyko wrote:
> >
> > -Original Message-
> > From: Vishal Verma [mailto:vishal.l.ve...@intel.com]
> > Sent: Friday, January 13, 2017 4:49 PM
> > To: Slava Dubeyko <vyacheslav.dube...
On 01/16, Darrick J. Wong wrote:
> On Fri, Jan 13, 2017 at 05:49:10PM -0700, Vishal Verma wrote:
> > On 01/14, Slava Dubeyko wrote:
> > >
> > > Original Message
> > > Subject: [LSF/MM TOPIC] Badblocks checking/representation in filesystems
> &g
On 01/14, Slava Dubeyko wrote:
>
> Original Message
> Subject: [LSF/MM TOPIC] Badblocks checking/representation in filesystems
> Sent: Jan 13, 2017 1:40 PM
> From: "Verma, Vishal L"
> To: lsf...@lists.linux-foundation.org
> Cc: linux-nvd...@lists.01.org,