From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: David Cramblett <david@functionalchaos.net>
Subject: Re: device mapper not finding all devices
Date: Tue, 19 Jul 2011 14:51:10 -0400 [thread overview]
Message-ID: <4E25D21E.8050901@cfl.rr.com> (raw)
In-Reply-To: <CA+cRLpLs7CL4VeSw9YNGdTDOUG8mz=TpUuzyP=sWXpLiKywA+A@mail.gmail.com>
On 7/17/2011 3:03 PM, David Cramblett wrote:
> Current Software:
> Linux 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:23:01 EDT 2011 i686
> i686 i386 GNU/Linux
> device-mapper-1.02.55-2.el5
2.6.18 is now 5 years old; it might be time to upgrade.
> I did some research and the only info I could find was regarding dmsetup:
>
> #dmsetup status
> pdc_eehgddjjp1: 0 976768002 linear
> pdc_eehgddjj: 0 976772992 linear
> via_cdeadaheebp1: 0 976768002 linear
> via_cdeadaheeb: 0 1953546240 striped 2 8:0 8:16 1 AA
>
>
> Looks like something is wrong with the vg0-lvol0 entry above, but I
> can't figure out how to fix it. There is also another HDD on each of
You only seem to have 4 entries for two dmraid disks ( which is not well
supported so you should not be using it unless you need to dual boot
with windows ) and a partition on each. It is also quite strange that
the pdc array is using a linear mapping. Could it be a degraded mirror?
> the via and pdc controllers that are seen by the system, but not
> showing up in the "status" list above. There is also a disk connected
> to PATA port "/dev/hda" that is part of the lvol.
What disks are supposed to be LVM physical volumes? The output of
pvdisplay may prove useful. An lvchange -ay might also be worthwhile.
> The device-mapper device is being created for the lvol:
>
> /dev/mapper/vg0-lvol0
If it had actually been created, then it should show up in dmsetup
status. The system appears to be failing to create it.
next prev parent reply other threads:[~2011-07-19 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 19:03 device mapper not finding all devices David Cramblett
2011-07-19 18:51 ` Phillip Susi [this message]
2011-07-19 20:48 ` David Cramblett
2011-07-20 16:27 ` Gianluca Cecchi
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=4E25D21E.8050901@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=david@functionalchaos.net \
--cc=dm-devel@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.