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>
Subject: Re: [RFC PATCH] Btrfs: send, add calculate data size flag to allow for progress estimation
Date: Sun, 6 Apr 2014 10:20:30 -0700	[thread overview]
Message-ID: <20140406172030.GF5006@merlins.org> (raw)
In-Reply-To: <CAL3q7H7Em8hX1CeARSjoZHwjvEjiQNs9Ni_ofH5aVbjQ04j0fQ@mail.gmail.com>

On Sun, Apr 06, 2014 at 05:57:38PM +0100, Filipe David Manana wrote:
> > I looked around and found nothing that looked similar enough.
> > Obviously it's an assert, so I can run without it, but my source being
> > very different from yours just made me want to check that this was most
> > likely ok to run with 3.14.0.
> 
> This is based on top of btrfs-next plus previous send patches sent to
> this list but not yet in btrfs-next.
 
Right, I figured. It otherwise applied to 3.14, so I'm hopeful it'll
work since only the assert was missing.

> > 2) I saw the concerns about protocol incompatibility. Is it an issue if you run without -o
> > too?
> 
> No. See the discussion above. Using a send stream created with the new
> flag won't work with an old btrfs receive. But to be able to get a
> send stream with the new flag you need the patched btrfs receive
> (unless you plan to write your own code to call the send ioctl
> directly).

Thanks for confirming. Given that, it sounds more than fine to me.

> > 3) Do you have a patch for btrfs-tools so that I can try it, or a git
> > tree of btrfs-tools with this that I should pull?
> 
> Yes, without it I couldn't test it and it would be pointless. There's
> a patch in the list for btrfs-progs.  I've also pasted a link to it
> (and this one too) in reply to the thread you started days ago.

So yes I knew you had a patch obviously :) but I missed the Email where
you sent it, and just found it now
"[RFC PATCH] Btrfs-progs: send, calculate and report progress based on the new flag"

> > 4) Can I run btrfs send -o snap1 snap2 >/dev/null to get quick stats
> > on the changes between the 2 snapshots, or is it still going to walk
> > through all the data blocks and send them to /dev/null afterwards?
> 
> No, but it's doable and implies only extending the user space tools.
> What is implemented is explained in the commit log for the btrfs-progs
> patch.

Yes, I just read that now, my apologies for missing that other Email.

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-04-06 17:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 15:20 [RFC PATCH] Btrfs: send, add calculate data size flag to allow for progress estimation Filipe David Borba Manana
2014-04-04 14:52 ` Konstantinos Skarlatos
2014-04-04 15:59   ` Filipe David Manana
2014-04-04 15:53 ` David Sterba
2014-04-04 16:01   ` Filipe David Manana
2014-04-04 16:32     ` David Sterba
2014-04-06  0:18 ` Marc MERLIN
2014-04-06 16:57   ` Filipe David Manana
2014-04-06 17:20     ` Marc MERLIN [this message]
2014-04-07 15:25 ` Josef Bacik

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=20140406172030.GF5006@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.