From: Liu Bo <bo.li.liu@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: tolerate errors if we have retried successfully
Date: Tue, 9 May 2017 12:40:53 -0700 [thread overview]
Message-ID: <20170509194053.GF17312@lim.localdomain> (raw)
In-Reply-To: <20170505165245.GF10575@twin.jikos.cz>
On Fri, May 05, 2017 at 06:52:45PM +0200, David Sterba wrote:
> On Thu, Apr 13, 2017 at 06:11:56PM -0700, Liu Bo wrote:
> > With raid1 profile, dio read isn't tolerating IO errors if read length is
> > less than the stripe length (64K).
>
> Can you please write more details why this is true? Some pointers to
> code etc, I'm lost. Eg. where the errors is tolerated. Thanks.
Sure.
Our bio didn't get split in btrfs_submit_direct_hook() if (dip->flags &
BTRFS_DIO_ORIG_BIO_SUBMITTED) is true. If the underlying device returns error
somehow, bio->bi_error has recorded that error.
If we could recover the correct data from another copy in profile raid1/10/5/6,
with btrfs_subio_endio_read() returning 0, bio would have the correct data in
its vector, but bio->bi_error is not updated accordingly so that the following
dio_end_io(dio_bio, bio->bi_error) makes directIO think this read has failed.
Thanks,
-liubo
>
> > This fixes the problem by setting bio's error to 0 if a good copy has been
> > found.
> >
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> > fs/btrfs/inode.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> > index 632b616..4e1398e 100644
> > --- a/fs/btrfs/inode.c
> > +++ b/fs/btrfs/inode.c
> > @@ -8113,8 +8113,11 @@ static void btrfs_endio_direct_read(struct bio *bio)
> > struct btrfs_io_bio *io_bio = btrfs_io_bio(bio);
> > int err = bio->bi_error;
> >
> > - if (dip->flags & BTRFS_DIO_ORIG_BIO_SUBMITTED)
> > + if (dip->flags & BTRFS_DIO_ORIG_BIO_SUBMITTED) {
> > err = btrfs_subio_endio_read(inode, io_bio, err);
> > + if (!err)
> > + bio->bi_error = 0;
> > + }
> >
> > unlock_extent(&BTRFS_I(inode)->io_tree, dip->logical_offset,
> > dip->logical_offset + dip->bytes - 1);
> > --
> > 2.5.5
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-09 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 1:11 [PATCH] Btrfs: tolerate errors if we have retried successfully Liu Bo
2017-05-05 16:52 ` David Sterba
2017-05-09 19:40 ` Liu Bo [this message]
2017-05-15 15:57 ` David Sterba
2017-05-17 21:42 ` [PATCH v2] " Liu Bo
2017-06-06 13:42 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170509194053.GF17312@lim.localdomain \
--to=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).