Re: [RFC PATCH v1 0/7] Block/XFS: Support alternative mirror device retry

Darrick J. Wong
2018-11-28T05:49:36Z

On Wed, Nov 28, 2018 at 04:33:03PM +1100, Dave Chinner wrote:
> On Tue, Nov 27, 2018 at 08:49:44PM -0700, Allison Henderson wrote:
> > Motivation:
> > When fs data/metadata checksum mismatch, lower block devices may have other
> > correct copies. e.g. If XFS successfully reads a metadata buffer off a raid1 but
> > decides that the metadata is garbage, today it will shut down the entire
> > filesystem without trying any of the other mirrors. This is a severe
> > loss of service, and we propose these patches to have XFS try harder to
> > avoid failure.
> >
> > This patch prototype this mirror retry idea by:
> > * Adding @nr_mirrors to struct request_queue which is similar as
> > blk_queue_nonrot(), filesystem can grab device request queue and check max
> > mirrors this block device has.
> > Helper functions were also added to get/set the nr_mirrors.
> >
> > * Expanding bi_write_hint to bi_rw_hint, now @bi_rw_hint has three meanings.
> > 1.Original write_hint.
> > 2.end_io() will update @bi_rw_hint to reflect which mirror this i/o really happened.
> > 3.Fs set @bi_rw_hint to force driver e.g raid1 read from a specific mirror.
> >
> > * Modify md/raid1 to support this retry feature.
> >
> > * Add b_rw_hint to xfs_buf
> > This patch adds a new field b_rw_hint to xfs_buf. We will use this to set the
> > new bio->bi_rw_hint when submitting the read request, and also to store the
> > returned mirror when the read compleates
>
> One thing that is going to make this more complex at the XFS layer
> is discontiguous buffers. They require multiple IOs (and therefore
> bios) and so we are going to need to ensure that all the bios use
> the same bi_rw_hint.

Hmm, we hadn't thought about that. What happens if we have a
discontiguous buffer mapped to multiple blocks, and there's only one
good copy of each block on separate disks in the whole array?

e.g. we have 8k directory blocks on a 4k block filesystem, only disk 0
has a good copy of block 0 and only disk 1 has a good copy of block 1?

I think we're just stuck with failing the whole thing because we can't
check the halves of the 8k block independently and there's too much of a
combinatoric explosion potential to try to mix and match.

> This is another reason I suggest that bi_rw_hint has a magic value
> for "block layer selects mirror" and separate the initial read from

(As mentioned in a previous reply of mine, setting rw_hint == 0 is the
magic value for "device picks mirror"...)

> the retry iterations. That allows us to let he block layer ot pick
> whatever leg it wants for the initial read, but if we get a failure
> we directly control the mirror we retry from and all bios in the
> buffer go to that same mirror.
>
> > We're not planning to take over all 16 bits of the read hint field; just looking for
> > feedback about the sanity of the overall approach.
>
> It seems conceptually simple enough - the biggest questions I have
> are:
>
> - how does propagation through stacked layers work?

Right now it doesn't, though once we work out how to make stacking work
through device mapper (my guess is that simple dm targets like linear
and crypt can set the mirror count to min(all underlying devices).

> - is it generic/abstract enough to be able to work with
> RAID5/6 to trigger verification/recovery from the parity
> information in the stripe?

In theory we could supply a raid5 implementation, wherein rw_hint == 0
lets the raid do as it pleases; rw_hint == 1 reads from the stripe; and
rw_hint == 2 forces stripe recovery for the given block.

A trickier scenario that I have no idea how to solve is the question of
how to handle dynamic redundancy levels. We don't have a standard bio
error value that means "this mirror is temporarily offline", so if you
have a raid1 of two disks and disk 0 goes offline, the retry loop in xfs
will hit the EIO and abort without even asking disk 1. It's also
unclear if we need to designate a second bio error value to mean "this
mirror is permanently gone".

[Also insert handwaving about whether or not online fsck will want to
control retries and automatic rewrite; I suspect the answer is that it
doesn't care.]

[[Also insert severe handwaving about do we expose this to userspace so
that xfs_repair can use it?]]

--D

> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com