All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Turner <rich@storix.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] snapshots and VFS lock patch
Date: Mon Feb 16 11:46:27 2004	[thread overview]
Message-ID: <1076950052.2404.33.camel@rich> (raw)

the way i understand it is that the only way to create a snapshot of a
journaled filesystem (ext3, XFS, etc.) is to have the VFS lock patch
applied to the kernel. this will lock the filesystem and allow it to
flush the journal before it creates the snapshot. is this true?

is there anyway to check to see if the VFS lock patch has been applied
on a system before creating the snapshot?

has this patch ever been added to the stock kernel or will every user
that wishes to create a snapshot of a journaled filesystem have to
manually apply the patch?

is the VFS lock patch required for LVM2?

what happens when a snapshot is created with a kernel that does not have
the VFS lock patch? does the snapshot creation fail with valid return
code? does the snapshot just hang up? is there any effect on the
original LV?

                 reply	other threads:[~2004-02-16 16:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1076950052.2404.33.camel@rich \
    --to=rich@storix.com \
    --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 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.