All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 3.14.0rc3: btrfs send ioctl failed with -5: Input/output error
Date: Tue, 25 Feb 2014 09:30:22 -0800	[thread overview]
Message-ID: <20140225173022.GF3521@merlins.org> (raw)
In-Reply-To: <530C4B37.9000402@cn.fujitsu.com>

On Tue, Feb 25, 2014 at 03:50:15PM +0800, Wang Shilong wrote:
> Hi Marc,
> 
> This seems a regression which has been fixed by the following
> commit(only pushed into btrfs-next):
> 
> https://git.kernel.org/cgit/linux/kernel/git/josef/btrfs-next.git/commit/?id=1334bebe71bebbca47b3b92f25511ea980fdeab8

I'll revert this, thanks.

Mmmh, but I just found another problem I didn't have before upgrading to 3.14.0-rc3
(on my laptop this time):

+ btrfs send -p /mnt/btrfs_pool1/var_ro.20140224_14:01:54 var_ro.20140225_09:27:57
+ btrfs receive /mnt/btrfs_pool2//
At subvol var_ro.20140225_09:27:57
At snapshot var_ro.20140225_09:27:57
ERROR: send ioctl failed with -5: Input/output error
ERROR: unexpected EOF in stream.

Is it another different regression?

Currently it's only happening on one of my subvolumes. The other ones
are still syncing ok.

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  reply	other threads:[~2014-02-25 17:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25  6:36 3.14.0rc3: did not find backref in send_root Marc MERLIN
2014-02-25  7:50 ` Wang Shilong
2014-02-25 17:30   ` Marc MERLIN [this message]
2014-02-26  3:38     ` 3.14.0rc3: btrfs send ioctl failed with -5: Input/output error Wang Shilong
2014-02-26  7:46 ` 3.14.0rc3: did not find backref in send_root Marc MERLIN
2014-02-26  7:51   ` Wang Shilong
2014-02-26 17:16     ` Marc MERLIN
2014-05-06  6:10 ` David Brown
2014-05-06  6:49   ` Blaz Repas
2014-05-10  8:13   ` David Brown

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=20140225173022.GF3521@merlins.org \
    --to=marc@merlins.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangsl.fnst@cn.fujitsu.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.