All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Filipe David Manana <fdmanana@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	Hugo Mills <hugo@carfax.org.uk>, Josef Bacik <jbacik@fb.com>
Subject: Re: How to recover from failing btrfs send | btrfs receive?
Date: Sun, 16 Feb 2014 21:32:32 -0800	[thread overview]
Message-ID: <20140217053232.GQ27097@merlins.org> (raw)
In-Reply-To: <CAL3q7H7uuaTjH7RWW-Q73E7zpc5=bpHP4nCrK3JkOsXaAj08Jw@mail.gmail.com>

On Sun, Feb 16, 2014 at 09:08:57PM +0000, Filipe David Manana wrote:
> I'll see if I come up with other ways of getting into that issue.

If you're collecting them, I found another bug, although it might not
matter to most: if I put my laptop in S3 sleep during a send/receive, it
reliably breaks the copy (this is disk to disk, not disk to network).

Not a problem for a server, but on a laptop, if you happen to have a
background backup from disk1 to disk2 and you put the laptop to sleep,
it will break the backup in a way that's not recoverable and you need to
start back up from scratch.

btrfs send | btrfs receive gives:
Create a readonly snapshot of 'home' in './home_ro.20140216_21:03:53'
At subvol home_ro.20140216_21:03:53
At subvol home_ro.20140216_21:03:53

ERROR: crc32 mismatch in command.
Error line 137 with status 234

If that helps, I can reproduce at will.

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-17  5:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 14:22 How to recover from failing btrffs send | btrfs receive? Marc MERLIN
2014-02-14  1:54 ` Marc MERLIN
2014-02-16 14:23   ` How to recover from failing btrfs " Marc MERLIN
2014-02-16 15:38     ` Filipe David Manana
2014-02-16 17:23       ` Marc MERLIN
2014-02-16 21:08         ` Filipe David Manana
2014-02-17  5:32           ` Marc MERLIN [this message]
2014-02-22 19:22             ` btrfs send ioctl failed with -25: Inappropriate ioctl for device Marc MERLIN
  -- strict thread matches above, loose matches on Subject: below --
2014-02-16 13:43 [PATCH] Btrfs: incremental send, fix invalid path after dir rename Filipe David Borba 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=20140217053232.GQ27097@merlins.org \
    --to=marc@merlins.org \
    --cc=fdmanana@gmail.com \
    --cc=hugo@carfax.org.uk \
    --cc=jbacik@fb.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.