linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 Snapshots Question
Date: Sun, 22 Oct 2006 12:12:02 +0100	[thread overview]
Message-ID: <20061022111202.GE17654@agk.surrey.redhat.com> (raw)
In-Reply-To: <20061022110659.82422.qmail@web52911.mail.yahoo.com>

On Sun, Oct 22, 2006 at 04:06:59AM -0700, Rik Herrin wrote:
> Does this mean that I don't have to unmount (or remount ro) a partition if
> I'm using a 2.6 kernel to take a snapshot and I can rest assured that the
> logical volume will be in a consistent state?  Thanks for your help.
 
Yes, in principle; but there was a bug in userspace lvm2 for a while
(fixed in 2.02.08 - introduced around 2.02.02?) and there are problems
with a mistaken semaphone/mutex change someone put into some recent kernels
around 2.6.18.

Alasdair
-- 
agk@redhat.com

      reply	other threads:[~2006-10-22 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22 11:06 [linux-lvm] LVM2 Snapshots Question Rik Herrin
2006-10-22 11:12 ` Alasdair G Kergon [this message]

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=20061022111202.GE17654@agk.surrey.redhat.com \
    --to=agk@redhat.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 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).