All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Karlsson <anders.karlsson@meansolutions.com>
To: "Heinz J. Mauelshagen" <linux-lvm@sistina.com>
Subject: [linux-lvm] Linux LVM
Date: Sat Dec 28 16:29:01 2002	[thread overview]
Message-ID: <20021228222936.GA3752@alien.meansolutions.com> (raw)

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

Hello,

I have been using LVM for a long time (0.9beta era and onwards) and always
been very happy with it. It always seems to work well for me, so no
complaints on that.

I have been running SuSE 8.1 Professional for a while, and recently updated
to kernel 2.4.20-ac2. Since then, I have problem with doing anything that
modifies anything, the error I get doing anything at all is:

ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan

Now, this has been reported on the mailinglist, and I have tried the
prescribed remedies. First I tried upgrading the LVM tools to 1.0.6, that
did not help. Recompiled the kernel with linux lvm 1.0.6 patch applied,
that did not help either. Then I built 2.4.20 with lvm 1.0.6 patch applied
and that, you guessed it, has not fixed the problem either.

I am at this point a little stumped and do not quite know what to do. Kernel
2.4.20 (and 2.4.20-ac2) enabled me to use DRM/DRI and to customise a few
other things that SuSE does not provide in their kernel.

If you could come up with a few pointers on things to look at to fix this,
I would be happy to try them...

Regards,

-- 
Anders Karlsson <anders.karlsson@meansolutions.com>
Trudheim Technology Ltd. - AIX and Linux System Administrator

PGP Usage Strongly Advised!!      My Key ID = 4B20601A
Fingerprint = 1B11 2F8C CBD6 7E53 E246  B23B 2D8C B0AA 4B20 601A

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

                 reply	other threads:[~2002-12-28 16:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021228222936.GA3752@alien.meansolutions.com \
    --to=anders.karlsson@meansolutions.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.