All of lore.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Help! Problems finding VG after reboot.
Date: Tue, 6 Feb 2001 13:22:40 -0600	[thread overview]
Message-ID: <20010206132240.E3376@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102061656090.1535-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Tue, Feb 06, 2001 at 04:58:22PM -0200

[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]

On Tue, Feb 06, 2001 at 04:58:22PM -0200, Rik van Riel wrote:
> On Tue, 6 Feb 2001 gobo@gimle.nu wrote:
> 
> > Running vgscan I got the following message:
> > 
> > # vgscan
> > vgscan -- reading all physical volumes (this may take a while...)
> > vgscan -- found inactive volume group "widow"
> > vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get 
> > data of volume group "widow" from physical volume(s)
> > vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" creating 
> > "/etc/lvmtab" and "/etc/lvmtab.d"
> 
> I am running into the same bug, with the very latest LVM
> utilities and kernel 2.4.1.
> 
> I have posted a bugreport in the LVM bugzilla, but I haven't
> heard anything from the LVM developers. Lets just hope they're
> not ignoring us...

The problem with your bug report on Bugzilla is that it is confusing.  You
added to a bug that complained about vgscan seg-faulting.  That bug is
obviously fixed.  The problem now is that vgscan no longer finds proper data
in the volume group.  This should be posted as a separate bug report, not
tacked onto the end of the old one.  

BTW, just because you haven't gotten an immediate reply does not mean the
problem is not being worked on.  We are a distributed development team,
with varying schedules.  Please give us a little credit that we are actually
reading the MLs and working on these problems instead of impatiently
complaining that nobody on the LVM team is doing anything all the time.  It
is rather tiring to see yet another post from you complaining that we don't do
anything.

-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-379-3951
1313 5th St SE, Suite 111              Fax:    612-379-3952
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
A bad random number generator: 1, 1, 1, 1, 1, 4.33e+67, 1, 1, 1...
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-02-06 19:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06 18:35 [linux-lvm] Help! Problems finding VG after reboot gobo
2001-02-06 18:58 ` Rik van Riel
2001-02-06 19:22   ` AJ Lewis [this message]
2001-02-06 19:31     ` AJ Lewis
2001-02-06 20:09     ` Rik van Riel
2001-02-06 20:39       ` AJ Lewis
2001-02-06 21:04         ` Rik van Riel
2001-02-06 23:30         ` gobo
2001-02-07 17:25         ` gobo
2001-02-07 17:34           ` gobo
2001-02-07 18:10           ` Andreas Dilger
2001-02-06 21:13     ` Michael E Brown
2001-02-06 18:31       ` Richard Smith
2001-02-08  0:47         ` Gregory McLean
2001-02-08  1:16           ` Andreas Dilger

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=20010206132240.E3376@sistina.com \
    --to=lewis@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.