From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org,
Filipe David Manana <fdmanana@gmail.com>,
Chris Murphy <lists@colorremedies.com>
Subject: Re: 3.15-rc5 btrfs send/receive corruption errors? Does scrub warn of silent corruption?
Date: Sat, 10 May 2014 19:29:54 -0700 [thread overview]
Message-ID: <20140511022954.GA14398@merlins.org> (raw)
In-Reply-To: <D55BDA6A-5DFA-4981-AC69-3156317ED169@colorremedies.com>
On Sat, May 10, 2014 at 04:57:18PM -0700, Marc MERLIN wrote:
> On Sat, May 10, 2014 at 03:42:49PM -0700, Marc MERLIN wrote:
> > 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?
>
> This brings me back to the earlier question:
>
> When my other FS died, scrub ran ok just earlier.
>
> Now, having 2 btrfs sends (not incremental, full) fail with 2 kernels
> would indicate that something might be wrong on the source filesystem.
>
> Yet, last night's scrub ran fine too:
>
> On Fri, May 09, 2014 at 11:39:13AM -0700, Anacron wrote:
> > /etc/cron.daily/btrfs-scrub:
> > scrub device /dev/mapper/cryptroot (id 1) done
> > scrub started at Fri May 9 06:09:14 2014 and finished after 19153 seconds
> > total bytes scrubbed: 646.15GiB with 0 errors
>
> So, does scrub actually make sure everything on my filesystem is sane,
> or can it miss some kinds of corruptions?
I'm thinking that there must be some corruption on btrfs_pool2,
because:
On Sat, May 10, 2014 at 06:06:46PM -0600, Chris Murphy wrote:
> I think the issue might be there are still problems and changing code on the receive side (btrfs-progs). The kernel side code responsible for send is probably working correctly.
I tried
3.15 and progs 3.12
3.15 and progs 3.14
3.14 and progs 3.12
3.14 and progs 3.14
All 4 failed to run
legolas:/mnt/btrfs_pool2# btrfs send home_ro.20140507_10:00:01 | btrfs receive /mnt/btrfs_pool1/
3.14 gives:
ERROR: send ioctl failed with -5: Input/output error
ERROR: unexpected EOF in stream.
3.15 gives a more detailled message how it can't rename some corrupted
filename (regardless of whether I use progs 3.12 or 3.14).
So, since scrub tells me my FS is ok, is scrub right, or do I have a
file pattern that is causing a bug in btrfs send ?
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
next prev parent reply other threads:[~2014-05-11 2:30 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
2014-05-11 0:06 ` Chris Murphy
2014-05-11 0:16 ` Marc MERLIN
2014-05-11 0:50 ` Chris Murphy
[not found] ` <E1WiphR-0003MN-50@legolas.merlins.org>
2014-05-11 2:29 ` Marc MERLIN [this message]
2014-05-12 23:26 ` 3.15-rc5 btrfs send/receive corruption errors? Does scrub warn of silent corruption? 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=20140511022954.GA14398@merlins.org \
--to=marc@merlins.org \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).