From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>,
Martin Steigerwald <Martin@lichtvoll.de>
Subject: Re: Safe fsck / consistent backup while mounted
Date: Sat, 04 Jun 2011 15:46:12 +0200 [thread overview]
Message-ID: <4DEA3724.8070007@wpkg.org> (raw)
> Now I thought about a way to safely backup a MySQL or other database -
> without long service interruption:
>
> - Tell DB to turn itself into consistent state and freeze there
> - sync / btrfs filesystem sync ; fsfreeze -f /mountpoint
> - btrfs subvolume snapshot
> - fsfreeze -u /mountpoint
Hmm, I don't think fsfreeze works properly with btrfs?
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2011-06-04 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 13:46 Tomasz Chmielewski [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-04 10:25 Safe fsck / consistent backup while mounted Martin Steigerwald
2011-06-04 14:13 ` Arne Jansen
2011-06-04 16:07 ` Calvin Walton
2011-06-05 7:58 ` David Pottage
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=4DEA3724.8070007@wpkg.org \
--to=mangoo@wpkg.org \
--cc=Martin@lichtvoll.de \
--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).