All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] How to upgrade old LVM version.
Date: Mon Sep  9 06:24:54 2002	[thread overview]
Message-ID: <20020909125357.B15934@sistina.com> (raw)
In-Reply-To: <3D790636.5010603@lingbrae.com>; from dick@lingbrae.com on Fri, Sep 06, 2002 at 08:47:02PM +0100

On Fri, Sep 06, 2002 at 08:47:02PM +0100, Dick Middleton wrote:
> Hi,
> 
>     I'm currently running LVM 0.9.1_beta6 on Debian 2.2 with kernel 
> 2.2.19 and have been trying
> for some time to upgrade to something more recent.
> 
> Whenever I try this I find that vgscan from any newer version of LVM 
> hangs (without
> error messages) - I'm forced to reboot.  The only evidence I can find is 
> if I run pvscan.  
> This reports "different structure size".

vgscan coming with a newer LVM version should scan your disks fine.
Tha fact that it hangs could refer to an empty CDROM or the like scanned
and a large timeout involved.

Running "vgscan -d" should find the relevant 'candidate'.
If so, temporarily inserting a valid CD or removing the /dev/ entry
could help it.

> 
> I currently have all my filesystem including root running on LVM on top 
> of software RAID so
> it's a fairly delicate business mucking about with this.  I'm looking 
> for  a way to fix the problem
> other than decanting everything to tape and starting from scratch again.
> 
> I do have a separate bootable disc with 2.4 kernel and LVM 1.0 which I 
> can use as a stepping
> stone but so far this too hangs as soon as vgscan is run.
> 
> Any advice would be appreciated.
> 
> Dick
> 
> 
> 
> 
> _______________________________________________
> 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:[~2002-09-09  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 14:47 [linux-lvm] How to upgrade old LVM version Dick Middleton
2002-09-09  6:24 ` 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=20020909125357.B15934@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 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.