All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@Sistina.com>
To: Christoph Hellwig <hch@caldera.de>
Cc: Jonathan Lahr <lahr@sequent.com>,
	lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: block device snapshot capability
Date: Thu, 12 Apr 2001 10:44:02 +0000	[thread overview]
Message-ID: <20010412104402.A25018@sistina.com> (raw)
In-Reply-To: <20010411142654.A23996@w-lahr.des.sequent.com> <200104112140.XAA05309@ns.caldera.de>
In-Reply-To: <200104112140.XAA05309@ns.caldera.de>; from hch@caldera.de on Wed, Apr 11, 2001 at 11:40:36PM +0200

On Wed, Apr 11, 2001 at 11:40:36PM +0200, Christoph Hellwig wrote:
> In article <20010411142654.A23996@w-lahr.des.sequent.com> you wrote:
> 
> > Hello all,
> >
> > Is anyone aware of ongoing development to provide the capability 
> > to take a snapshot of a block device?
> 
> It's part of Linux-LVM since version 0.8 and thus part of Linux 2.4.

You need to get the recent LVM 0.9.1 Beta 7 software *and* to patch your
kernel as well, because that'll fix some snapshot related flaws.

> 
> 	Christoph
> 
> -- 
> Of course it doesn't work. We've performed a software upgrade.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2001-04-12  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 21:26 block device snapshot capability Jonathan Lahr
2001-04-11 21:40 ` Christoph Hellwig
2001-04-12 10:44   ` Heinz J. Mauelshagen [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=20010412104402.A25018@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=hch@caldera.de \
    --cc=lahr@sequent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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.