All of lore.kernel.org
 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: Mon, 30 Oct 2017 09:37:08 +0530	[thread overview]
Message-ID: <CAKuJGC-K3ph_fiZe49pm27Fz+YtVh7WB5kC7JrJ9Ry6KkTrzxA@mail.gmail.com> (raw)
In-Reply-To: <1484297967.48018.1508985286675@email.1and1.com>

> I will gladly repeat this process, but I am very concerned why this
> corruption happened in the first place.
>
Can you share these steps as simple bash script? Currently I'm running
few tests, I can check your script and share the results.


> The only thing I could think of is that the btrfs version that I used to mkfs
> was not up to date. Is there a way to determine which version was used to
> create the filesystem?
>

If I'm not wrong, i don't think we can get mkfs version from existing file
system layout. what was your kernel version?

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

      parent reply	other threads:[~2017-10-30  4:07 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
2017-10-30  4:07             ` Lakshmipathi.G [this message]

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-K3ph_fiZe49pm27Fz+YtVh7WB5kC7JrJ9Ry6KkTrzxA@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 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.