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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html