From: Edmund Nadolski <enadolski@suse.de>
To: bo.li.liu@oracle.com, dsterba@suse.cz,
Anand Jain <anand.jain@oracle.com>,
Peter Grandi <pg@btrfs.list.sabi.co.UK>,
Linux fs Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/7] retry write on error
Date: Mon, 4 Dec 2017 13:49:28 -0700 [thread overview]
Message-ID: <89ffe153-7f1a-8d14-7a68-d95fcf9a8e25@suse.de> (raw)
In-Reply-To: <20171130202253.GA8197@dhcp-whq-twvpn-1-vpnpool-10-159-155-222.vpn.oracle.com>
On 11/30/2017 01:22 PM, Liu Bo wrote:
>>>>>>> If the underlying protocal doesn't support retry and there
>>>>>>> are some transient errors happening somewhere in our IO
>>>>>>> stack, we'd like to give an extra chance for IO.
> Anyway, this is for a corner case, not for everyone, I think I need to
> make it configurable so that at least we can provide some extra
> robustness for people who super care about their data.
Not sure I follow -- wouldn't such users prefer a transport like e.g.
scsi that *does* perform retries (as well as other error recovery)?
(Possibly they would also want features like mirroring & multipath, but
in those scenarios doing additional retries from the filesystem is also
unlikely to help much.)
Ed
next prev parent reply other threads:[~2017-12-04 20:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 0:35 [PATCH 0/7] retry write on error Liu Bo
2017-11-22 0:35 ` [PATCH 1/7] Btrfs: keep a copy of bi_iter in btrfs_io_bio Liu Bo
2017-11-22 0:35 ` [PATCH 2/7] Btrfs: add helper __btrfs_end_bio Liu Bo
2017-11-22 0:35 ` [PATCH 3/7] Btrfs: retry write for non-raid56 Liu Bo
2017-11-22 14:41 ` Nikolay Borisov
2017-11-28 23:01 ` Liu Bo
2017-11-22 0:35 ` [PATCH 4/7] Btrfs: get rbio inside fail_bio_stripe Liu Bo
2017-11-22 0:35 ` [PATCH 5/7] Btrfs: add helper __raid_write_end_io Liu Bo
2017-11-22 0:35 ` [PATCH 6/7] Btrfs: retry write for raid56 Liu Bo
2017-11-22 0:35 ` [PATCH 7/7] Btrfs: retry the whole bio on write error Liu Bo
2017-11-28 19:22 ` [PATCH 0/7] retry write on error David Sterba
2017-11-28 22:07 ` Edmund Nadolski
2017-11-28 23:41 ` Peter Grandi
2017-11-29 4:09 ` Anand Jain
2017-11-29 16:47 ` David Sterba
2017-11-30 20:22 ` Liu Bo
2017-12-03 21:00 ` Peter Grandi
2017-12-04 9:14 ` Anand Jain
2017-12-04 20:49 ` Edmund Nadolski [this message]
2017-12-05 18:57 ` David Sterba
2017-11-29 18:09 ` Liu Bo
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=89ffe153-7f1a-8d14-7a68-d95fcf9a8e25@suse.de \
--to=enadolski@suse.de \
--cc=anand.jain@oracle.com \
--cc=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=pg@btrfs.list.sabi.co.UK \
/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).