All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Zak Kohler <y2k@y2kbugger.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: Mon, 6 Nov 2017 13:04:48 -0700	[thread overview]
Message-ID: <CAJCQCtSR3aSe5OfEW3A2vxvv8j71pqTu-mOeYSvjaKhGogT=Jg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtS9he3cpqKgnFQjM2GPA1atvgfmi2ZhrjGZg8Yq1h91BQ@mail.gmail.com>

On Sun, Oct 29, 2017 at 1:05 PM, Chris Murphy <lists@colorremedies.com> wrote:
> On Thu, Oct 26, 2017 at 4:34 AM, Zak Kohler <y2k@y2kbugger.com> wrote:
>
>> I will gladly repeat this process, but I am very concerned why this
>> corruption happened in the first place.
>
> Right. So everyone who can, needs to run the three scrubs on all
> available Btrfs volumes/devices and see if they get any discrepancies.

I've just done this test with five Btrfs volumes of various ages, and
a total of a few TB. There were no errors, and no discrepancies
between the three scrubs. What is needed for more thorough testing is
corrupt metadata and data (unrelated), and see how the three scrubs
report those corruptions. More information in the new thread "feedback
on three different scrub methods"


-- 
Chris Murphy

  parent reply	other threads:[~2017-11-06 20:04 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 [this message]
     [not found]                 ` <CAD8FQQ3XSsLt4XYdeMg7r3oX9WUerW27f8RMuKurjL4cpY8=1g@mail.gmail.com>
2017-11-11 19:11                   ` Chris Murphy
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='CAJCQCtSR3aSe5OfEW3A2vxvv8j71pqTu-mOeYSvjaKhGogT=Jg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.