linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lakshmipathi.G" <lakshmipathi.g@gmail.com>
To: Zak Kohler <y2k@y2kbugger.com>
Cc: btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send yields "ERROR: send ioctl failed with -5: Input/output error"
Date: Tue, 24 Oct 2017 10:22:31 +0530	[thread overview]
Message-ID: <CAKuJGC-aRt_NKboYa9ZK6ApWDJ_knM-UazPxEUq7sHiNXEqA6w@mail.gmail.com> (raw)
In-Reply-To: <CAD8FQQ3kBfy8kLFzSm-OVbsYsQ7-LzH0faD09__4S5_q0bM7pA@mail.gmail.com>

> Does anyone know why scrub did not catch these errors that show up in dmesg?

Can you try offline scrub from this repo
https://github.com/gujx2017/btrfs-progs/tree/offline_scrub and see
whether it
detects the issue?  "btrfs scrub start --offline <dev>"


----
Cheers,
Lakshmipathi.G
http://www.giis.co.in http://www.webminal.org

  reply	other threads:[~2017-10-24  4:53 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 [this message]
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
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=CAKuJGC-aRt_NKboYa9ZK6ApWDJ_knM-UazPxEUq7sHiNXEqA6w@mail.gmail.com \
    --to=lakshmipathi.g@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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).