From: Patrick Caulfield <pcaulfie@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Coraid Support <support@coraid.com>
Subject: Re: [linux-lvm] Strange LVM Error With AoE Disks
Date: Wed, 07 Feb 2007 14:44:00 +0000 [thread overview]
Message-ID: <45C9E5B0.5010703@redhat.com> (raw)
In-Reply-To: <A2E4EC06-9B8D-4C63-8567-4DF6475D4543@engineyard.com>
Jayson Vantuyl wrote:
> Hello,
>
> We have been using Coraid's ATA-Over-Ethernet shelves for a while with
> much success.
>
> Recently, we added a second shelf (numbered 1) to our first shelf
> (numbered 0). CLVM has been running on the old shelf perfectly fine.
>
> As soon as I added the second shelf, attempting to lvcreate a new lv
> utilizing the new disks generated roughly the following errors:
>
> Error locking on node ey00-02: Internal lvm error, check syslog
> Error locking on node ey00-05: Internal lvm error, check syslog
> Error locking on node ey00-01: Internal lvm error, check syslog
> Error locking on node ey00-00: Internal lvm error, check syslog
> Error locking on node ey00-04: Internal lvm error, check syslog
> Error locking on node ey00-03: Internal lvm error, check syslog
> Failed to activate new LV.
>
> All of the nodes show the following errors in syslog:
>
> Feb 7 06:09:36 ey00-00 lvm[4869]: Couldn't find all physical volumes
> for volume group ey00-data.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Couldn't find device with uuid
> '0Cot9Z-BHjK-2Nkw-eEdy-fbFF-Wh1q-qhRaut'.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Couldn't find all physical volumes
> for volume group ey00-data.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Couldn't find device with uuid
> '0Cot9Z-BHjK-2Nkw-eEdy-fbFF-Wh1q-qhRaut'.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Couldn't find all physical volumes
> for volume group ey00-data.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Couldn't find device with uuid
> '0Cot9Z-BHjK-2Nkw-eEdy-fbFF-Wh1q-qhRaut'.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Couldn't find all physical volumes
> for volume group ey00-data.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Couldn't find device with uuid
> '0Cot9Z-BHjK-2Nkw-eEdy-fbFF-Wh1q-qhRaut'.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Couldn't find all physical volumes
> for volume group ey00-data.
> Feb 7 06:09:37 ey00-00 lvm[4869]: Volume group for uuid not found:
> WWbD8SXOsAJzDYRCFQiciQho84Rl99nVF7QbO0ArRxnH4cZeKgzG0Nx4gbEhgALU
>
> Inspecting the lvm.conf shows that these devices are the new ones that
> were added.
>
> Even more bizarre, pvscan finds them just fine on all nodes.
>
> The only thing I can note about these devices that is particularly
> different is that they appear to be using minor numbers above 256. Note
> this ls output:
>
> brw-rw---- 1 root disk 152, 288 Feb 7 04:43 /dev/etherd/e1.2
> brw-rw---- 1 root disk 152, 289 Feb 7 06:10 /dev/etherd/e1.2p1
> brw-rw---- 1 root disk 152, 304 Feb 7 04:44 /dev/etherd/e1.3
> brw-rw---- 1 root disk 152, 305 Feb 7 06:10 /dev/etherd/e1.3p1
>
> Is there a known problem with LVM or CLVM related to large device minor
> numbers?
Did you restart clvmd after adding the new disks? There is a bug where it
doesn't always recognise new hardware.
--
patrick
next prev parent reply other threads:[~2007-02-07 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 14:16 [linux-lvm] Strange LVM Error With AoE Disks Jayson Vantuyl
2007-02-07 14:44 ` Patrick Caulfield [this message]
2007-02-07 22:23 ` Jayson Vantuyl
2007-02-07 19:21 ` [linux-lvm] " Ed L. Cashin
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=45C9E5B0.5010703@redhat.com \
--to=pcaulfie@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=support@coraid.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.