From: Chris Mason <chris.mason@fusionio.com>
To: "christophe.varoqui@opensvc.com" <christophe.varoqui@opensvc.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] opensvc btrfs send/receive driver
Date: Tue, 4 Sep 2012 17:57:13 -0400 [thread overview]
Message-ID: <20120904215713.GA8857@shiny.int.fusionio.com> (raw)
In-Reply-To: <1346779594.24415.17.camel@lapoo.opensvc.com>
On Tue, Sep 04, 2012 at 11:26:34AM -0600, Christophe Varoqui wrote:
> Here are the stacks encountered during the opensvc btrfs send/receive
> development.
>
> The system is a debian squeeze amd64 in a kvm over debian squeeze amd64.
> The disks handed to btrfs are logical volumes passed to the kvm as vdb
> and vdc. The vm kernel is 3.6rc3 and btrfs-progs are at git commit
> 043a63924c9831ac52ce38f0365b9bfd628fb6a3 (Thu, 9 Aug 2012).
Ok, could you please try to reproduce with my send-receive branch on the
kernel side?
-chris
next prev parent reply other threads:[~2012-09-04 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 17:26 [ANNOUNCE] opensvc btrfs send/receive driver Christophe Varoqui
2012-09-04 21:57 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-04 14:23 Christophe Varoqui
2012-09-04 15:12 ` Chris Mason
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=20120904215713.GA8857@shiny.int.fusionio.com \
--to=chris.mason@fusionio.com \
--cc=christophe.varoqui@opensvc.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 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).