All of lore.kernel.org
 help / color / mirror / Atom feed
From: lvm@perkamentus.com
To: linux-lvm@redhat.com
Subject: [linux-lvm] Disk partition required for LVM?
Date: Tue, 21 Sep 2004 14:32:06 +0200	[thread overview]
Message-ID: <20040921123206.GA1467@perkamentus> (raw)

We have been experiencing strange LVM behaviour on multiple
machines. The situation:

 - Debian 3.1 (Sarge)
 - 2.6.8.1 Kernel
 - LVM2
 - 3 IDE disks (2x80GB, 1x120GB) (All Maxtors)

Creating physical volumes is no problem for two disks, but with the
third disk (it is actually on hdb and already a different disk then
the one originally used) problems begin. pvcreate does not give any
errors, but with pvdisplay the disk is not shown while pvscan gives
"Couldn't find device with uuid
'xAMOJ3-xIGd-AJQK-HN5Q-Q9Yg-Mu2D-UYxn0Y'"

It is possible to create volume groups and logical volumes, but
pvscan, vgscan and lvscan keeping failing with the above error.

Neither of the 3 disks has a partition when starting. When on hdb a
partition is created and then hdb1 is used as physical volume
everything works fine.

Why does the partition need to be created on that disk for LVM to work
(and not on the other two)? Is this a problem with LVM2, the 2.6
kernel? Or could it be hardware not functioning as it should,
e.g. disk or controller?

I would like to know why the creation of a partition is necessary. Has
anyone experienced the same problem/behaviour with LVM? If so, is
there a solution so no partition is needed?

Thanks in advance for the help.

             reply	other threads:[~2004-09-21 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 12:32 lvm [this message]
2004-09-21 13:09 ` [linux-lvm] Disk partition required for LVM? Patrick Caulfield
2004-09-21 13:30   ` lvm
2004-09-22  3:01     ` David Johnston

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=20040921123206.GA1467@perkamentus \
    --to=lvm@perkamentus.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.