Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Upgrade path
Date: Tue, 17 Jul 2001 13:31:58 +0200	[thread overview]
Message-ID: <20010717133158.F17345@sistina.com> (raw)
In-Reply-To: <20010716155838.A882@btconnect.com>; from thornber@btconnect.com on Mon, Jul 16, 2001 at 03:58:38PM +0100

On Mon, Jul 16, 2001 at 03:58:38PM +0100, Joe Thornber wrote:
> On Mon, Jul 16, 2001 at 04:42:53PM +0200, Wichert Akkerman wrote:
> > Previously Heinz J. Mauelshagen wrote:
> > > I announced the holdup caused by the misalignment bugs we found.
> > > We'll need to release another Beta ASAP to get test feedback on that.
> > 
> > I saw that, but there seems to have been a consensus on a fix
> > for that for over a week now already.
> 
> Fixing it isn't the problem, ensuring people with existing VG's can
> use the new driver/tools *is* the problem.

Yep.

> The pe positions weren't
> being stored in the metadata before beta8 :( So we have to upgrade
> peoples VG's.  I understand that Heinz has written the upgrade tool,
> but I'm not sure how much testing he wants before we release.

Every Sistina LVM team member needs to test, that up-/downgrades work propperly
before we release. The regular tests need to be run as well.

> 
> - Joe
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

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-07-17 11:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-13 12:26 [linux-lvm] Upgrade path Patrick Boutilier
2001-07-16 11:29 ` Heinz J. Mauelshagen
2001-07-16 12:03   ` Wichert Akkerman
2001-07-16 14:25     ` Heinz J. Mauelshagen
2001-07-16 14:42       ` Wichert Akkerman
2001-07-16 14:58         ` Joe Thornber
2001-07-17 11:31           ` Heinz J. Mauelshagen [this message]
2001-07-16 19:48         ` Heinz J. Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2001-07-16 20:11 Gonyou, Austin
2001-07-17 11:29 ` Heinz J. Mauelshagen
2003-03-20 15:48 Bradley M Alexander

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=20010717133158.F17345@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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