1 |
Doh....gmail didn't send my reply to the list. |
2 |
|
3 |
Hopefully this information will help someone else. |
4 |
|
5 |
-- |
6 |
David Miller |
7 |
|
8 |
---------- Forwarded message ---------- |
9 |
From: David Miller <david3d@×××××.com> |
10 |
Date: May 31, 2005 9:29 PM |
11 |
Subject: Re: [gentoo-server] LVM2 issues |
12 |
To: strerror@g.o |
13 |
|
14 |
|
15 |
Ben, |
16 |
Thanks. I found an answer to this on redhat's lvm list. The |
17 |
problem is a result of mixed up partitioning. In my case I had |
18 |
created LVM partitions on the devices in the partition table and had |
19 |
added the entire device to the volume group rather than the partition. |
20 |
But this unused partition in the partition table is confusing the |
21 |
newer version of the device-mapper or LVM2. According to this post |
22 |
removing the partition tables from the devices should straighten this |
23 |
problem up. https://www.redhat.com/archives/linux-lvm/2005-April/msg00019.html |
24 |
|
25 |
Hopefully this post will help someone else who finds themself in the |
26 |
same situation. |
27 |
|
28 |
I'm in the process now of moving my PV's from one raid controller to |
29 |
another so I plan to re-add them to the VG using the partition that I |
30 |
created just to make things clearer as I add them to my VG again.. |
31 |
|
32 |
-David |
33 |
|
34 |
|
35 |
On 5/31/05, Benjamin Smee <strerror@g.o> wrote: |
36 |
> lo, |
37 |
> |
38 |
> On Tuesday 31 May 2005 17:49, David Miller wrote: |
39 |
> > I've been running LVM2 now for some time but recently I have not |
40 |
> > been able to update device-mapper or lvm2 without vgscan failing to |
41 |
> > find all the pv's. So I'm stuck using lvm2-2.00.25 and device-mapper |
42 |
> > 1.00.19-r2. |
43 |
> > Now one thing to note is that a few of my pv's were added as the |
44 |
> > entire device rather than a partition. Could this be throwing a newer |
45 |
> > version for a loop since it may first be looking for an LVM partition |
46 |
> > before looking for a vg metadata? Or have I just overlooked something |
47 |
> > that I need to do in order to migrate my current vg's up to the newer |
48 |
> > versions? |
49 |
> |
50 |
> There is nothing that you need to do to "migrate" your lvm2 partitions to a |
51 |
> newer format, whatever problem that you have will be something local not |
52 |
> generic as many people are successfully using the latest versions of both |
53 |
> with no problems. You could start off running the vgscan in debug mode and |
54 |
> letting us know the relevant output, and if that fails try running it with a |
55 |
> strace or similar util to see precisely what is happening. Other pertinant |
56 |
> questions are things like, are you using udev? with persistant devices (ie |
57 |
> the tarball option in the rc.conf) what version of baselayout are you using, |
58 |
> do you have devfs enabled? |
59 |
> |
60 |
> regards, |
61 |
> |
62 |
> -- |
63 |
> Benjamin Smee (strerror) |
64 |
> 497F 5E98 1FA0 C313 EA0B 08C7 004A 66ED 448B E78C |
65 |
> |
66 |
> |
67 |
> |
68 |
|
69 |
-- |
70 |
gentoo-server@g.o mailing list |