All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org, Filipe David Manana <fdmanana@gmail.com>
Subject: Re: 3.15-rc5 btrfs send/receive corruption errors?
Date: Sat, 10 May 2014 15:42:49 -0700	[thread overview]
Message-ID: <20140510224249.GA15909@merlins.org> (raw)
In-Reply-To: <20140510220710.GA6772@merlins.org>

On Sat, May 10, 2014 at 03:07:10PM -0700, Marc MERLIN wrote:
> Howdy,
> 
> While moving data back to a brand new btrfs FS I had just created (with
> 3.14 tools and under 3.15), I got this:
> 
> legolas:/mnt/btrfs_pool2# for i in tmp_ro.20140507_09:00:31 root_ro.20140507_10:00:20 usr_ro.20140507_09:00:41 var_ro.20140507_09:00:58 home_ro.20140507_10:00:01; do btrfs send $i | btrfs receive /mnt/btrfs_pool1/; done
> At subvol tmp_ro.20140507_09:00:31
> At subvol tmp_ro.20140507_09:00:31
> At subvol root_ro.20140507_10:00:20
> At subvol root_ro.20140507_10:00:20
> At subvol usr_ro.20140507_09:00:41
> At subvol usr_ro.20140507_09:00:41
> At subvol var_ro.20140507_09:00:58
> At subvol var_ro.20140507_09:00:58
> ERROR: chown www/Q\x17\x06\x04����Q\x17\x06\x04��� failed. No such file or directory
> At subvol home_ro.20140507_10:00:01
> At subvol home_ro.20140507_10:00:01
> ERROR: chmod merlin/.config/google-chrome-mysetup/\x04���� failed. No such file or directory
> legolas:/mnt/btrfs_pool2#
> 
> legolas:/mnt/btrfs_pool2/var_ro.20140507_09:00:58/www# ls
> shows no file that looks like Q^W^F^D����Q^W^F^D��� 
> 
> Same deal with merlin/.config/google-chrome-mysetup/
> 
> However, I see:
> legolas:/mnt/btrfs_pool1/home_ro.20140507_10:00:01# l
> total 16
> drwxr-xr-x 1 root   root    20 May 10 09:09 ./
> drwxr-xr-x 1 root   root   244 May 10 07:50 ../
> drwx------ 1 root   root     0 May 10 09:09 ?0$?/
> drwxr-xr-x 1 merlin merlin 198 May  7 06:21 merlin/
> => corruption

I tried with 3.14.3 and it went further, however it died with
legolas:/mnt/btrfs_pool2# btrfs send  home_ro.20140507_10:00:01 | btrfs receive /mnt/btrfs_pool1/
At subvol home_ro.20140507_10:00:01
At subvol home_ro.20140507_10:00:01
ERROR: send ioctl failed with -5: Input/output error
ERROR: unexpected EOF in stream.

I'll look up -5 later when I have time, but I guess there is a problem
on the source that is causing copies to fail with both kernels?

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-05-10 22:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10 22:07 3.15-rc5 btrfs send/receive corruption errors? Marc MERLIN
2014-05-10 22:42 ` Marc MERLIN [this message]
2014-05-11  0:06   ` Chris Murphy
2014-05-11  0:16     ` Marc MERLIN
2014-05-11  0:50       ` Chris Murphy
2014-05-11  2:29     ` 3.15-rc5 btrfs send/receive corruption errors? Does scrub warn of silent corruption? Marc MERLIN
2014-05-12 23:26   ` Marc MERLIN
2014-05-13 20:11     ` Filipe David Manana
2014-05-14 13:26       ` Marc MERLIN
2014-05-17 22:23         ` Marc MERLIN
2014-05-19 12:54           ` Filipe David Manana

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=20140510224249.GA15909@merlins.org \
    --to=marc@merlins.org \
    --cc=fdmanana@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.