From: "Ed L. Cashin" <ecashin@coraid.com>
To: Jayson Vantuyl <jvantuyl@engineyard.com>
Cc: Coraid Support <support@coraid.com>,
Linux LVM List <linux-lvm@redhat.com>
Subject: [linux-lvm] Re: Strange LVM Error With AoE Disks
Date: Wed, 7 Feb 2007 14:21:22 -0500 [thread overview]
Message-ID: <20070207192122.GE7006@coraid.com> (raw)
In-Reply-To: <A2E4EC06-9B8D-4C63-8567-4DF6475D4543@engineyard.com>
On Wed, Feb 07, 2007 at 08:16:23AM -0600, Jayson Vantuyl wrote:
...
> 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'.
...
> 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.
...
> Is there a known problem with LVM or CLVM related to large device
> minor numbers?
Hello, Jayson Vantuyl. I just wanted to chime in to say that we are
not aware of such a problem, but we wouldn't necessarily have heard
about it, since the population using CLVM on AoE is probably not large
yet. (Many use LVM, but I haven't heard much feedback from folks
using CLVM.)
I haven't looked at the CLVM sources really recently, but we have seen
the large minor device number problem before in older versions of LVM
where glibc's macros are used to work with the major and minor parts
that are encoded within device numbers. So if there's a problem, it
might be possible to find it by looking for those macros.
--
Ed L Cashin <ecashin@coraid.com>
next prev parent reply other threads:[~2007-02-07 19:25 UTC|newest]
Thread overview: 5+ 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
2007-02-07 22:23 ` Jayson Vantuyl
2007-02-07 19:21 ` Ed L. Cashin [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 13:11 [linux-lvm] " Daniele Palumbo
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=20070207192122.GE7006@coraid.com \
--to=ecashin@coraid.com \
--cc=jvantuyl@engineyard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).