From: Stephane CHAZELAS <stephane_chazelas@yahoo.fr>
To: linux-btrfs@vger.kernel.org
Subject: Re: how stable are snapshots at the block level?
Date: Mon, 24 Oct 2011 12:36:28 +0000 (UTC) [thread overview]
Message-ID: <slrnjaamuc.jcd.stephane.chazelas@spam.is.invalid> (raw)
In-Reply-To: CAKvOHKCjxxKTahivOuRBPBB89JBrTwndQ6cCEuFaPbJr8PYtpA@mail.gmail.com
2011-10-23, 17:19(+02), Mathijs Kwik:
[...]
> For this case (my laptop) I can stick to file-based rsync, but I think
> some guarantees should exist at the block level. Many virtual machines
> and cloud hosting services (like ec2) provide block-level snapshots.
> With xfs, I can freeze the filesystem for a short amount of time
> (<100ms), snapshot, unfreeze. I don't think such a lock/freeze feature
> exists for btrfs
[...]
That FS-freeze feature has been moved to the vfs layer so is
available to any filesystem now.
You can either use xfs_io (see -F option to "freeze" for foreign
FS) like for xfs FS or use fsfreeze from util-linux.
Note that you can thaw file systems with a sysrq combination
now. (for instance with xen using "xm sysrq vm j").
For block level snapshots, see also ddsnap (device mapper target
unfortunately no longer maintained) and lvm of course (but
doesn't scale well with several snapshots).
--
Stephane
next prev parent reply other threads:[~2011-10-24 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 7:45 how stable are snapshots at the block level? Mathijs Kwik
2011-10-23 14:08 ` Edward Ned Harvey
2011-10-23 15:19 ` Mathijs Kwik
2011-10-24 12:36 ` Stephane CHAZELAS [this message]
2011-10-24 13:59 ` Edward Ned Harvey
2011-10-24 15:08 ` Stephane CHAZELAS
2011-10-25 11:46 ` Edward Ned Harvey
2011-10-25 12:01 ` Stephane CHAZELAS
2011-10-25 12:04 ` Edward Ned Harvey
2011-10-23 16:05 ` Chris Mason
2011-10-23 16:41 ` Mathijs Kwik
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=slrnjaamuc.jcd.stephane.chazelas@spam.is.invalid \
--to=stephane_chazelas@yahoo.fr \
--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.