linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Filipe David Manana <fdmanana@gmail.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send/receive still gets out of sync in 3.14.0
Date: Sun, 30 Mar 2014 07:27:33 -0700	[thread overview]
Message-ID: <20140330142733.GB22552@merlins.org> (raw)
In-Reply-To: <CAL3q7H6C+fBBK4n7cL8r1zoZ=onn2hM5jKLcxN4b5dbQnUKXcA@mail.gmail.com>

On Sun, Mar 30, 2014 at 02:13:35PM +0100, Filipe David Manana wrote:
> On Sun, Mar 30, 2014 at 1:42 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> > On Sat, Mar 29, 2014 at 08:22:02PM -0700, Marc MERLIN wrote:
> >> On Sat, Mar 22, 2014 at 02:04:56PM -0700, Marc MERLIN wrote:
> >> > After deleting a huge directory tree in my /home subvolume, syncing
> >> > snapshots now fails with:
> >> >
> >> > ERROR: rmdir o1952777-157-0 failed. No such file or directory
> >>
> >> So, I'm ok again after I deleted my destination snapshot and re-init'ed,
> >> but on multi terabyte backups, this ain't great :)
> >>
> >> Do I need to file a bug that btrfs send/receive still gets out of sync
> >> in 3.14, or is it already known and maybe even fixed in btrfs-next?
> >
> >    Filipe has been posting a series of patches related to send/receive
> > recently, so this may be related to those bugs.
> 
> Yes, this one in particular might have fixed the issue:
> 
> http://git.kernel.org/cgit/linux/kernel/git/josef/btrfs-next.git/commit/?id=29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5
> 
> (There might be other cases that attempt to rmdir a non-existing
> orphan directory)

Cool, thanks for fixing those. 
Is that meant to make it in 3.14 final, or is it going to be 3.15?

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-03-30 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 21:04 btrfs send/receive still gets out of sync in 3.14.0 Marc MERLIN
2014-03-30  3:22 ` Marc MERLIN
2014-03-30 12:42   ` Hugo Mills
2014-03-30 13:13     ` Filipe David Manana
2014-03-30 14:27       ` Marc MERLIN [this message]
2014-03-30 15:14         ` Filipe David Manana
2014-03-30 23:01           ` Marc MERLIN
2014-04-22 16:07 ` 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=20140330142733.GB22552@merlins.org \
    --to=marc@merlins.org \
    --cc=fdmanana@gmail.com \
    --cc=hugo@carfax.org.uk \
    --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 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).