[linux-lvm] Trouble with pvmove

[linux-lvm] Trouble with pvmove

[Andreé Åström]

Hi everyone,

In one of my volume groups a disk have gone bad.
I extended the volumegroup with another disk to be able to pvmove it.

pvmove -i -v /dev/hdh

It went fine until,
pvmove -- /dev/hdh [PE 259 [archive [LE 259]] -> /dev/hdj [PE 259]
[260/1831]

The machine got total dead. The whole volumegroup consists of 1.1TB so i
couldn't backup it all up beforehand.
I guess the moved PE's didnt get updated now, so the filesystem is kinda
screwy.

pvscan -- ACTIVE   PV "/dev/hdj" of VG "m00"  [93.12 GB / 59.12 GB free]
pvscan -- ACTIVE   PV "/dev/hdh" of VG "m00"  [57.22 GB / 34 GB free]

I tried to use pvmove after the cold reboot to continue.

Using pvmove -i -v /dev/hdh[some_pe-to_some_pe]
The machine dies on a few specific PE's tough, nothing in the logs. Is there
any way to update the config where the PE's got allocated manually ?
as in my case when pvmove died, the lvm config still thinks the PE's exists
on the /dev/hdh ?
It display them as unallocated, but my guess is the LVM dont know where
they've been moved.
Just wild guesses here, i dont really know how it works down under : )

Anyone have any clues how it may be solved or if some of it can be
salvageable?
pvscan finds the volumegroup, it can be mounted, but complains quickly about
missing inodes, etc, when i try to access it.

Regards,
Adain

Re: [linux-lvm] Trouble with pvmove

[Nils Juergens]

On Thu, 01.05.03, Andre� �str�m <andree.astrom@home.se> wrote:

> In one of my volume groups a disk have gone bad.
> I extended the volumegroup with another disk to be able to pvmove it.

Is the disk already producing read errors or are you using a SMART monitor
that tells you it is bad?

> 
> pvmove -i -v /dev/hdh
> 
> It went fine until,
> pvmove -- /dev/hdh [PE 259 [archive [LE 259]] -> /dev/hdj [PE 259]
> [260/1831]
> 
> The machine got total dead. The whole volumegroup consists of 1.1TB so i
> couldn't backup it all up beforehand.

Which version of LVM are you using? IIRC there has been trouble with pvmove
and lockups before, so try to upgrade to newest version.

cya,

Nils

-- 
 >   Nils Juergens  | nils@muon.de | icq 7090774   <
 >  If we all work hard, we can turn this company  <
 >      around 360 degrees -- gruntbert(LOTD)      <

Re: [linux-lvm] Trouble with pvmove

[Andreé Åström]

----- Original Message -----
From: "Nils Juergens" <nils@muon.de>
To: <linux-lvm@sistina.com>
Sent: Saturday, May 03, 2003 1:44 PM
Subject: Re: [linux-lvm] Trouble with pvmove


> On Thu, 01.05.03, Andre� �str�m <andree.astrom@home.se> wrote:
>
> > In one of my volume groups a disk have gone bad.
> > I extended the volumegroup with another disk to be able to pvmove it.
>
> Is the disk already producing read errors or are you using a SMART monitor
> that tells you it is bad?

Both, uncorrectable errors in dmesg, and smartctl reports it as failing.
>
> >
> > pvmove -i -v /dev/hdh
> >
> > It went fine until,
> > pvmove -- /dev/hdh [PE 259 [archive [LE 259]] -> /dev/hdj [PE 259]
> > [260/1831]
> >
> > The machine got total dead. The whole volumegroup consists of 1.1TB so i
> > couldn't backup it all up beforehand.
>
> Which version of LVM are you using? IIRC there has been trouble with
pvmove
> and lockups before, so try to upgrade to newest version.

We were using 1.0.4, so updated to 1.0.7 today. No luck tough. Computer
locks up completly at
certain PE's.
Any clues how i can recover any data from it ? As it complains now, of
missing inodes when i mount it and try to accesss it.
So i cant really do anything. I guess those was moved from the broken
harddisk to the new one, but never got updated
because the computer locked up.

Regards,
Adain

Re: [linux-lvm] Trouble with pvmove

[Nils Juergens]

On Mon, 05.05.03, Andre? ?str?m <andree.astrom@home.se> wrote:

> We were using 1.0.4, so updated to 1.0.7 today. No luck tough. Computer
> locks up completly at
> certain PE's.

You could try to use 'dd' to backup the damaged pv to a new (equally-sized)
partition, using 'conv=noerror' option to skip faulty blocks.

Perhaps you could use strace or on of the debugging options of pvmove to
determine wher it locks. I suspect it locks trying to read the faulty block
over and over again.

good luck,

Nils

-- 
Nils Juergens  | nils@muon.de | icq 7090774
Having problems sending big files over the net?
Try out Efisto (http://efisto.rnbhq.org).

Re: [linux-lvm] Trouble with pvmove

[Anders Widman]

> On Mon, 05.05.03, Andre? ?str?m <andree.astrom@home.se> wrote:

>> We were using 1.0.4, so updated to 1.0.7 today. No luck tough. Computer
>> locks up completly at
>> certain PE's.

> You could try to use 'dd' to backup the damaged pv to a new (equally-sized)
> partition, using 'conv=noerror' option to skip faulty blocks.

Or   even  a  better  tool  specifically  made  for this; dd_rescue :)
Simple, fast and secure.

> Perhaps you could use strace or on of the debugging options of pvmove to
> determine wher it locks. I suspect it locks trying to read the faulty block
> over and over again.

> good luck,

> Nils



   



--------
PGP public key: https://tnonline.net/secure/pgp_key.txt