From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] snapshots and filesystem freezing
Date: Fri, 08 Feb 2008 13:04:46 +0100 [thread overview]
Message-ID: <47AC455E.4030502@wpkg.org> (raw)
Some filesystems, like xfs, have a "freeze" feature. There was a
discussion on lkml about implementing it in ext3, too.
What is the relationship between a filesystem freeze and LVM snapshots?
As far as I understand, snapshotting a filesystem in any random
timepoint can mean that the snapshotted fs will be inconsistent (i.e.,
may need fsck).
"Freezing" the filesystem will flush all writes to the media, and a
snapshotted fs should be consistent then (in theory; without an
interface between filesystem freeze and LVM snapshot it does not
guarantee that the operation is "atomic").
Am I correct?
--
Tomasz Chmielewski
http://blog.wpkg.org
next reply other threads:[~2008-02-08 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 12:04 Tomasz Chmielewski [this message]
2008-02-08 12:28 ` [linux-lvm] snapshots and filesystem freezing Dan Kegel
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=47AC455E.4030502@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-lvm@redhat.com \
/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).