xfs
[Top] [All Lists]

Re: [RFC PATCH 2/2] xfs: initial/partial support for badblocks

To: Vishal Verma <vishal.l.verma@xxxxxxxxx>
Subject: Re: [RFC PATCH 2/2] xfs: initial/partial support for badblocks
From: Dan Williams <dan.j.williams@xxxxxxxxx>
Date: Fri, 17 Jun 2016 15:27:51 -0700
Cc: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>, linux-nvdimm <linux-nvdimm@xxxxxxxxxxx>, Jan Kara <jack@xxxxxxx>, XFS Developers <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=avvnQ+79SHDw2u6rvGVBu315pbfozh2fitCK3iHwdjU=; b=XWYDDVArJlAqjGxV9Sc/jdhxDS31H1TWLR3sVtuIFarhm1oeWzNFVA5kTW1O5bFaph KktLm35ckR1XfxWe+TRy4cKIYgf0z2iS22BvuON9kYCB8049rpkJg6q0fGgFWbCbfUe7 ZFR5VrOjexmoAXUmBrzlk+4WNOWgFsWH+Wxe05tkoqZst6mOCynCPbwgWDG28HsYp8rO Rgqq/vFrWAB5sFYIDNZUE5PupNLR8MRqDOYz/BRri21NqgJP67dzMpxuos5IlJKTZkFC J/N8T8Nl0MtySGOqo8LHEm7Aj4tvd/oYuAcQJgr9KyFmDBIqxfO/swNHM2lL3rS8Y20U mlFA==
In-reply-to: <20160617203237.GD5893@xxxxxxxxxxxxxxxxxxxxxxx>
References: <1466125419-17736-1-git-send-email-vishal.l.verma@xxxxxxxxx> <1466125419-17736-3-git-send-email-vishal.l.verma@xxxxxxxxx> <20160617022606.GC11810@xxxxxxxxxxxxxxxx> <20160617192647.GC5893@xxxxxxxxxxxxxxxxxxxxxxx> <20160617195345.GA5046@xxxxxxxxxxxxxxxx> <20160617203237.GD5893@xxxxxxxxxxxxxxxxxxxxxxx>
On Fri, Jun 17, 2016 at 1:32 PM, Vishal Verma <vishal.l.verma@xxxxxxxxx> wrote:
>> What happens if pmem signals a bad block and we try to read anyway?  I know
>> about the read-error-MCE thing, but what's the "more expensive" alternative?
>> CPU exception?
>
> MCE is the CPU exception, and is what we want to avoid at all costs, as
> it can cause the machine to crash.

The MCE being fatal vs recoverable is the difference between platforms
that must avoid badblocks vs those that can consume them and keep
going.

<Prev in Thread] Current Thread [Next in Thread>