From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: linux-btrfs@vger.kernel.org, Michael Welsh Duggan <mwd@md5i.com>
Subject: Re: btrfs send ioctl failed with -5: Input/output error
Date: Mon, 26 May 2014 18:16:09 -0400 [thread overview]
Message-ID: <5383BD29.5010309@gmail.com> (raw)
In-Reply-To: <87k398z1xk.fsf@maru2.md5i.com>
[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]
On 05/26/2014 05:04 PM, Michael Welsh Duggan wrote:
> Michael Welsh Duggan <mwd@md5i.com> writes:
>
>> I am now getting the following error when trying to do a btrfs send:
>>
>> root@maru2:/usr/local/src/btrfs-progs# ./btrfs send
>> /usr/local/snapshots/2014-05-15 > /backup/intermediate
>> At subvol /usr/local/snapshots/2014-05-15
>> ERROR: send ioctl failed with -5: Input/output error
>>
>> I'm running a 3.14.4 kernel, and Btrfs progs v3.14.1.
>>
>> root@maru2:/usr/local/src/btrfs-progs# uname -a
>> Linux maru2 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 GNU/Linux
>>
>> root@maru2:/usr/local/src/btrfs-progs# ./btrfs --version
>> Btrfs v3.14.1
>>
>> Is there anything I can do to help debug this issue?
>
> I'd like to find out what is happening here. I am an experienced C
> programmer, but have not dealt with kernel hacking before. I _do_ know
> how to build and install a kernel. I'd like some hints on what logging,
> etc., I could add in order to determine where in the send ioctl
> processing the IO error is coming from. From there, I hope to move to
> "why." Ideally I'd be able to run gdb on this, but nothing I have read
> online about kernel debugging with gdb sounds promising.
>
> I'd make an image, but the amount of data is enough to make this
> prohibitive.
>
I would look into ftrace (the Tracing submenu of the Kernel Hacking menu
in menuconfig and nconfig). The other thing to look at at least
initially is KDB, but using that requires either a serial console or an
AT or PS/2 keyboard. Using UML and GDB for debugging is possible, but
it can take a long time to set-up and is often slow (admitedly, KDB
isn't much faster). If you do go the UML+GDB route, make sure to build
in fault-injection (the flaky DM module is particularly nice for this
type of thing), and I would suggest using something like Buildroot
(http://www.buildroot.net) to generate the root filesystem for it.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
prev parent reply other threads:[~2014-05-26 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 23:17 btrfs send ioctl failed with -5: Input/output error Michael Welsh Duggan
2014-05-26 21:04 ` Michael Welsh Duggan
2014-05-26 22:16 ` Austin S Hemmelgarn [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=5383BD29.5010309@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mwd@md5i.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).