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 11:12:35 -0400 [thread overview]
Message-ID: <20120904151235.GC2358@shiny.int.fusionio.com> (raw)
In-Reply-To: <1346768600.27224.29.camel@lapoo.opensvc.com>
On Tue, Sep 04, 2012 at 08:23:20AM -0600, Christophe Varoqui wrote:
> Hi list,
>
> OpenSVC >= 120904.1516 now contains a replication driver for the btrfs
> send/receive mecanism. This new driver adds up to the zfs, rsync, dds,
> netapp, datacore and drbd existing drivers.
>
> It is no more mature than btrfs send/receive itself, so don't use in
> production clusters for now.
Great, thanks for wiring this up.
> - btrfs receive is easily confused when looking for a subvol parent id :
> for now opensvc has to mount the ID5 root vol
> on /opt/opensvc/var/btrfs/<label> and uses a flat/root-level snapshot
> hosting. If the btrfs feature matures we want to move to a .osvcsnap/
> dedicated subvol mounted in /opt/opensvc/var/btrfs/<label>.osvcnap/
> instead to not expose the whole btrfs structure. Some failure scenarios
> I tested included "receive in a subvol" and "receive in a subdir"
Yes, I'm changing the receive code to be more flexible on where it
receives things.
>
> - some kernel stacks and hangs when off-roading (trying to delete a
> parent subvol for example) ... most on btrfs_get_token_64+0x90/0xca .
> Let me know if you are interested in the details.
Definitely interested. There are a number of fixes for send/receive in
my send-recv branch. These will go into the next merge window.
-chris
next prev parent reply other threads:[~2012-09-04 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 14:23 [ANNOUNCE] opensvc btrfs send/receive driver Christophe Varoqui
2012-09-04 15:12 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-04 17:26 Christophe Varoqui
2012-09-04 21:57 ` 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=20120904151235.GC2358@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).