| 1 |
Well to answer my own question after looking in the man page for |
| 2 |
pvmove I have just run it again with no arguments and it has resumed |
| 3 |
where it left off. Which will hopefully resurect the one logical |
| 4 |
volume that at the moment cannot be mounted. I'll let you know how it |
| 5 |
goes. |
| 6 |
|
| 7 |
-David |
| 8 |
|
| 9 |
On 6/1/05, David Miller <david3d@×××××.com> wrote: |
| 10 |
> Well the server did a kernel dump last night while doing the pvmove. |
| 11 |
> Resulting in one logical volume being corrupted in the process. Not a |
| 12 |
> big deal as the data is on tape. However now lvdisplay still lists |
| 13 |
> the pvmove0 logical volume. So how do I clean up what was left |
| 14 |
> behind? |
| 15 |
> |
| 16 |
> -David |
| 17 |
> |
| 18 |
> On 5/31/05, Benjamin Smee <strerror@g.o> wrote: |
| 19 |
> > lo, |
| 20 |
> > |
| 21 |
> > On Tuesday 31 May 2005 17:49, David Miller wrote: |
| 22 |
> > > I've been running LVM2 now for some time but recently I have not |
| 23 |
> > > been able to update device-mapper or lvm2 without vgscan failing to |
| 24 |
> > > find all the pv's. So I'm stuck using lvm2-2.00.25 and device-mapper |
| 25 |
> > > 1.00.19-r2. |
| 26 |
> > > Now one thing to note is that a few of my pv's were added as the |
| 27 |
> > > entire device rather than a partition. Could this be throwing a newer |
| 28 |
> > > version for a loop since it may first be looking for an LVM partition |
| 29 |
> > > before looking for a vg metadata? Or have I just overlooked something |
| 30 |
> > > that I need to do in order to migrate my current vg's up to the newer |
| 31 |
> > > versions? |
| 32 |
> > |
| 33 |
> > There is nothing that you need to do to "migrate" your lvm2 partitions to a |
| 34 |
> > newer format, whatever problem that you have will be something local not |
| 35 |
> > generic as many people are successfully using the latest versions of both |
| 36 |
> > with no problems. You could start off running the vgscan in debug mode and |
| 37 |
> > letting us know the relevant output, and if that fails try running it with a |
| 38 |
> > strace or similar util to see precisely what is happening. Other pertinant |
| 39 |
> > questions are things like, are you using udev? with persistant devices (ie |
| 40 |
> > the tarball option in the rc.conf) what version of baselayout are you using, |
| 41 |
> > do you have devfs enabled? |
| 42 |
> > |
| 43 |
> > regards, |
| 44 |
> > |
| 45 |
> > -- |
| 46 |
> > Benjamin Smee (strerror) |
| 47 |
> > 497F 5E98 1FA0 C313 EA0B 08C7 004A 66ED 448B E78C |
| 48 |
> > |
| 49 |
> > |
| 50 |
> > |
| 51 |
> |
| 52 |
|
| 53 |
-- |
| 54 |
gentoo-server@g.o mailing list |
Archives