All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <Mauelshagen@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Kernel Patch for LVm-1.0.8
Date: Wed Feb 25 09:31:03 2004	[thread overview]
Message-ID: <20040225143257.GC11757@redhat.com> (raw)
In-Reply-To: <E1AtfOX-0007TZ-00@jade.ima.umn.edu>

Kumsup,

you can use actual 2.4 kernels fine with the LVM 1.0.8 tools.
Your problem seems to be related to on-disk metadata.

Can you see all Physical Volumes fine with pvscan ?
What does vgck display ?

On Wed, Feb 18, 2004 at 10:02:37PM -0600, Kumsup Lee wrote:
> Hi There,
> 
>   I used to have kernel 2.8.18 with LVM-1.0.4 on my machine.  After I
> upgraded kernel to 2.4.22 because of security problem, I couldn't 
> make any snapshot.  So, I tried to use LVM-1.0.8 on kernel 2.4.22.  Then 
> it complains about inconsistency.  Is there any LVM patch for 2.4.22+ ?
> 
> sys:/# vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found active volume group "mailspool"
> vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of
> volume group "mailspool" from physical volume(s)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume
> group
> 
> sys:/#
> 
> Thanks,
> 
> -- 
> 
> =============================================================================
>  Kumsup Lee (À̱݌·) 				 System/Network Manager 
>  Institute for Mathematics and its Applications, University of Minnesota 
>  400 Lind Hall,   207 Church Street S.E.,   Minneapolis, MN 55455   USA
>  Tel : 612-624-4353	FAX : 612-626-7370	PAGE : 952-608-0112
>  klee@ima.umn.edu	www.ima.umn.edu/~klee
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

Regards,
Heinz    -- The LVM Guy --

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

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

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2004-02-25 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  8:41 [linux-lvm] Kernel Patch for LVm-1.0.8 Kumsup Lee
2004-02-25  9:31 ` Heinz 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=20040225143257.GC11757@redhat.com \
    --to=mauelshagen@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 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.