From: Chris Murphy <lists@colorremedies.com>
To: Zak Kohler <y2k@y2kbugger.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
"Lakshmipathi.G" <lakshmipathi.g@gmail.com>,
btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send yields "ERROR: send ioctl failed with -5: Input/output error"
Date: Sat, 11 Nov 2017 12:11:49 -0700 [thread overview]
Message-ID: <CAJCQCtT+ZTi1BMchk5orGaraO2079SbSJterVMgVjO+fiYC1=Q@mail.gmail.com> (raw)
In-Reply-To: <CAD8FQQ3XSsLt4XYdeMg7r3oX9WUerW27f8RMuKurjL4cpY8=1g@mail.gmail.com>
On Sat, Nov 11, 2017 at 11:27 AM, Zak Kohler <y2k@y2kbugger.com> wrote:
> It seems that since the errors were due to a very slight instability in
> computer due to overclock, the online and offline scrub's causing different
> stresses or paths. Could it be that one is telling the drives to use some
> level of caching where the offline is explicitly tells it not to(or one of
> many similar scenarios)? There must be some line to draw about supporting
> faulty Hardware but I think having all forms of scrubbing in agreement must
> be within scope.
I think once you're in some non-deterministic state, all bets are off.
But I don't know anything about what physical parts of a CPU could
cause more or less error, or more or less determinism, based on code
differences.
--
Chris Murphy
next prev parent reply other threads:[~2017-11-11 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 4:25 btrfs send yields "ERROR: send ioctl failed with -5: Input/output error" Zak Kohler
2017-10-24 0:23 ` Zak Kohler
2017-10-24 4:52 ` Lakshmipathi.G
2017-10-24 6:00 ` Zak Kohler
2017-10-25 1:52 ` Zak Kohler
2017-10-25 3:43 ` Lakshmipathi.G
2017-10-26 2:34 ` Zak Kohler
2017-10-29 19:05 ` Chris Murphy
2017-10-30 1:57 ` Zak Kohler
2017-10-30 4:09 ` Duncan
2017-10-30 14:36 ` Zak Kohler
2017-10-31 2:33 ` Duncan
2017-11-02 12:23 ` Zak Kohler
2017-10-30 18:52 ` Chris Murphy
2017-11-06 20:04 ` Chris Murphy
[not found] ` <CAD8FQQ3XSsLt4XYdeMg7r3oX9WUerW27f8RMuKurjL4cpY8=1g@mail.gmail.com>
2017-11-11 19:11 ` Chris Murphy [this message]
2017-10-30 4:07 ` Lakshmipathi.G
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='CAJCQCtT+ZTi1BMchk5orGaraO2079SbSJterVMgVjO+fiYC1=Q@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=lakshmipathi.g@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=y2k@y2kbugger.com \
/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).