[linux-lvm] pv_move failed

[linux-lvm] pv_move failed

[Dieter Stueken]

I just got my new 240GB disk and want to move my VG to it.
Unfortunately I get an unexpected error:

lv: /dev/backup/mirror[2]  old_dev: 22:00  new_dev: 03:02
old_pe_sector: 117703032  new_pe_sector: 357564792
pvmove -- opening output physical volume "/dev/hda2"
pvmove -- llseeking input physical volume "/dev/hdc"
pvmove -- llseeking output physical volume "/dev/hda2"
pvmove -- /dev/hdc [PE 897 [mirror [LE 2727]] -> /dev/hda2 [PE 2727] [1/247]
pvmove -- locking physical extent 897 of "/dev/hdc" in kernel
pvmove -- about to read input physical volume "/dev/hdc" and to write
output physical volume "/dev/hda2"
pvmove -- ERROR writing output physical volume "/dev/hda2" (still
12648448 bytes to write)
pvmove -- ERROR "pv_move_pe(): writing output PE" moving physical extents

this time I can not identify any reason an no messages on syslog.
Any idea? What informations should I dump/post in addition?

I'm using SuSE8.1 with kernel 2.4.20, the LVM-version is 1.0.5.

... and, sorry for my ill formed subject line from last week.

Dieter
-- 
Dieter St�ken, con terra GmbH, M�nster
     stueken@conterra.de
     http://www.conterra.de/
     (0)251-7474-501

Re: [linux-lvm] pv_move failed

[Heinz J . Mauelshagen]

Dieter,

the first write to hda2 fails.
Could be a hardware installation problem with your new drive.

Have you tested if you can access hda2 fine without LVM ?

Regards,
Heinz    -- The LVM Guy --

On Tue, Feb 25, 2003 at 10:32:27AM +0100, Dieter Stueken wrote:
> I just got my new 240GB disk and want to move my VG to it.
> Unfortunately I get an unexpected error:
> 
> lv: /dev/backup/mirror[2]  old_dev: 22:00  new_dev: 03:02
> old_pe_sector: 117703032  new_pe_sector: 357564792
> pvmove -- opening output physical volume "/dev/hda2"
> pvmove -- llseeking input physical volume "/dev/hdc"
> pvmove -- llseeking output physical volume "/dev/hda2"
> pvmove -- /dev/hdc [PE 897 [mirror [LE 2727]] -> /dev/hda2 [PE 2727] [1/247]
> pvmove -- locking physical extent 897 of "/dev/hdc" in kernel
> pvmove -- about to read input physical volume "/dev/hdc" and to write
> output physical volume "/dev/hda2"
> pvmove -- ERROR writing output physical volume "/dev/hda2" (still
> 12648448 bytes to write)
> pvmove -- ERROR "pv_move_pe(): writing output PE" moving physical extents
> 
> this time I can not identify any reason an no messages on syslog.
> Any idea? What informations should I dump/post in addition?
> 
> I'm using SuSE8.1 with kernel 2.4.20, the LVM-version is 1.0.5.
> 
> ... and, sorry for my ill formed subject line from last week.
> 
> Dieter
> -- 
> Dieter Stüken, con terra GmbH, Münster
>      stueken@conterra.de
>      http://www.conterra.de/
>      (0)251-7474-501
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

RE: [linux-lvm] pv_move failed

[Dieter Stueken]

Heinz J . Mauelshagen wrote:

 >the first write to hda2 fails.
 >Could be a hardware installation problem with your new drive.

no indication. I had my VG on two 120G + 75G disks before.
The 120G disk could be moved completely, whereas moving
the 75G disk failed after 896 LE moved.

 >Have you tested if you can access hda2 fine without LVM ?

I run badblocks with no errors.

I just "strace" pvmove and get:

write(5, ..., 65536) = -1 ENOSPC (No space left on device)

seems pvmove gets a unexpected ENOSPC. OK, I got it:

fdisk -l /dev/hda   reports:

Disk /dev/hda: 255 heads, 63 sectors, 30515 cylinders
Units = cylinders of 16065 * 512 bytes

    Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1       262   2104483+  83  Linux
/dev/hda2           263     22526 178835580   8e  Linux LVM

The 2nd partition does not span to the end of the disk,
where as pvdisplay shows up with 231.75 GB. I'll remove all
data from hda2 again and try to find out, how this discrepancy
came about....

Dieter.
-- 
Dieter St�ken, con terra GmbH, M�nster
     stueken@conterra.de
     http://www.conterra.de/
     (0)251-7474-501

[linux-lvm] pv_move failed

[Dieter Stueken]

ok, is was all my fault:

I cloned my hda1 using dd and also tried to clone the MBR later
on, too. Stupidly i copied 512 bytes (instead of 446) and thus
"cloned" the partition table of my smaller 180G disk, too, and
the 240G target partition got truncated. After fixing this,
every thing works all right now.

Suggestion: For pvmove it might be helpful to report the actual
system errno occurred, if something went wrong.

Dieter.
-- 
Dieter St�ken, con terra GmbH, M�nster
     stueken@conterra.de
     http://www.conterra.de/
     (0)251-7474-501