linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
* [linux-lvm] error moving last PE away
@ 2002-02-09  9:08 Christian Hammers
  2002-02-09 10:16 ` [linux-lvm] SOLUTION: " Christian Hammers
  2002-02-10 12:40 ` [linux-lvm] " Heinz J . Mauelshagen
  0 siblings, 2 replies; 3+ messages in thread
From: Christian Hammers @ 2002-02-09  9:08 UTC (permalink / raw)
  To: Linux-LVM

Hi

# pvmove   -v   /dev/hda10  /dev/hda8
...
pvmove -- /dev/hda10 [PE 999 [lvol5 [LE 1365]] -> /dev/hda8 [PE 560] [1/1]
pvmove -- ERROR reading input physical volume "/dev/hda10" (still 65536
bytes to read)
pvmove -- ERROR "pv_move_pe(): read input PV" pv_move_pe
pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents

I wanted to release this partition from the LVM to use it with another OS.
The error once occured in June 2001 but I couldn't find a solution in the
archives.

Any ideas? More infos below.

bye,

-christian-

# uname -a
Linux app109 2.4.18-pre6 #7 Mit Jan 23 00:32:29 CET 2002 i686 unknown

# pvmove --version
pvmove: Logical Volume Manager 1.0.1
Heinz Mauelshagen, Sistina Software  26/11/2001 (IOP 10)

#  pvmove  -d -v   /dev/hda10  /dev/hda9
...
<333> pe_lock_internal -- CALLED for vg0
<4444> vg_check_name -- CALLED with VG: vg0
<55555> lvm_check_chars -- CALLED with name: "vg0"
<55555> lvm_check_chars -- LEAVING with ret: 0
<4444> vg_check_name -- LEAVING with ret: 0
<333> pe_lock_internal -- LEAVING with ret: 0
<22> pv_move_pe -- LEAVING with ret: -253
<22> lvm_error -- CALLED with: -253
<22> lvm_error -- LEAVING with: "pv_move_pe(): read input PV"
pvmove -- ERROR "pv_move_pe(): read input PV" pv_move_pe

<1> pv_move_pes -- LEAVING with ret: -253
<1> lvm_error -- CALLED with: -253
<1> lvm_error -- LEAVING with: "pv_move_pe(): read input PV"
pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents

<1> lvm_unlock -- CALLED
<1> lvm_unlock -- LEAVING with ret: 0

# vgdisplay -v
--- Volume group ---
VG Name               vg0
VG Access             read/write
VG Status             available/resizable
VG #                  0
MAX LV                256
Cur LV                4
Open LV               4
MAX LV Size           255.99 GB
Max PV                256
Cur PV                5
Act PV                5
VG Size               19.53 GB
PE Size               4.00 MB
Total PE              5000
Alloc PE / Size       2610 / 10.20 GB
Free  PE / Size       2390 / 9.34 GB
VG UUID               LuuTlh-HESy-ugJF-nxye-TC8f-MAe6-aIvT84

...

--- Physical volumes ---
PV Name (#)           /dev/hda6 (1)
PV Status             available / allocatable
Total PE / Free PE    1000 / 0

PV Name (#)           /dev/hda7 (2)
PV Status             available / allocatable
Total PE / Free PE    1000 / 1

PV Name (#)           /dev/hda8 (3)
PV Status             available / allocatable
Total PE / Free PE    1000 / 440

PV Name (#)           /dev/hda9 (4)
PV Status             available / allocatable
Total PE / Free PE    1000 / 950

PV Name (#)           /dev/hda10 (5)
PV Status             available / NOT allocatable
Total PE / Free PE    1000 / 999

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [linux-lvm] SOLUTION: error moving last PE away
  2002-02-09  9:08 [linux-lvm] error moving last PE away Christian Hammers
@ 2002-02-09 10:16 ` Christian Hammers
  2002-02-10 12:40 ` [linux-lvm] " Heinz J . Mauelshagen
  1 sibling, 0 replies; 3+ messages in thread
From: Christian Hammers @ 2002-02-09 10:16 UTC (permalink / raw)
  To: Linux-LVM

On Sat, Feb 09, 2002 at 04:08:09PM +0100, Christian Hammers wrote:
> # pvmove   -v   /dev/hda10  /dev/hda8
> ...
> pvmove -- /dev/hda10 [PE 999 [lvol5 [LE 1365]] -> /dev/hda8 [PE 560] [1/1]
> pvmove -- ERROR reading input physical volume "/dev/hda10" (still 65536
> bytes to read)
> pvmove -- ERROR "pv_move_pe(): read input PV" pv_move_pe
> pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents

A friend gave me the hint to enlarge the partition by one block. It helped,
after rebooting to let the kernel reload the partition table, pvmove ran
successfully.

The partition in question looked like:
$ LC_ALL=C fdisk -l

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

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1         8     64228+  83  Linux
/dev/hda2   *         9       518   4096575    b  Win95 FAT32
/dev/hda3           519      4867  34933342+   5  Extended
/dev/hda5           519       773   2048256   83  Linux
/dev/hda6           774      1283   4096543+  8e  Linux LVM
/dev/hda7          1284      1793   4096543+  8e  Linux LVM
/dev/hda8          1794      2303   4096543+  8e  Linux LVM
/dev/hda9          2304      2813   4096543+  8e  Linux LVM

/dev/hda10         2814      3323   4096543+  8e  Linux LVM    NOT WORKING
/dev/hda10         2814      3324   4096543+  8e  Linux LVM        WORKING
[the rest of the drive was already empty]

bye,

-christian-

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [linux-lvm] error moving last PE away
  2002-02-09  9:08 [linux-lvm] error moving last PE away Christian Hammers
  2002-02-09 10:16 ` [linux-lvm] SOLUTION: " Christian Hammers
@ 2002-02-10 12:40 ` Heinz J . Mauelshagen
  1 sibling, 0 replies; 3+ messages in thread
From: Heinz J . Mauelshagen @ 2002-02-10 12:40 UTC (permalink / raw)
  To: linux-lvm

Christian,

you are probably suffering from a misalignment bug introduced in the LVM
0.9.1 Beta series :-(

Send "pvdisplay -v /dev/hda10" output to me (mge@sistina.com) to
check this.

Regards,
Heinz    -- The LVM Guy --

On Sat, Feb 09, 2002 at 04:08:09PM +0100, Christian Hammers wrote:
> Hi
> 
> # pvmove   -v   /dev/hda10  /dev/hda8
> ...
> pvmove -- /dev/hda10 [PE 999 [lvol5 [LE 1365]] -> /dev/hda8 [PE 560] [1/1]
> pvmove -- ERROR reading input physical volume "/dev/hda10" (still 65536
> bytes to read)
> pvmove -- ERROR "pv_move_pe(): read input PV" pv_move_pe
> pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents
> 
> I wanted to release this partition from the LVM to use it with another OS.
> The error once occured in June 2001 but I couldn't find a solution in the
> archives.
> 
> Any ideas? More infos below.
> 
> bye,
> 
> -christian-
> 
> # uname -a
> Linux app109 2.4.18-pre6 #7 Mit Jan 23 00:32:29 CET 2002 i686 unknown
> 
> # pvmove --version
> pvmove: Logical Volume Manager 1.0.1
> Heinz Mauelshagen, Sistina Software  26/11/2001 (IOP 10)
> 
> #  pvmove  -d -v   /dev/hda10  /dev/hda9
> ...
> <333> pe_lock_internal -- CALLED for vg0
> <4444> vg_check_name -- CALLED with VG: vg0
> <55555> lvm_check_chars -- CALLED with name: "vg0"
> <55555> lvm_check_chars -- LEAVING with ret: 0
> <4444> vg_check_name -- LEAVING with ret: 0
> <333> pe_lock_internal -- LEAVING with ret: 0
> <22> pv_move_pe -- LEAVING with ret: -253
> <22> lvm_error -- CALLED with: -253
> <22> lvm_error -- LEAVING with: "pv_move_pe(): read input PV"
> pvmove -- ERROR "pv_move_pe(): read input PV" pv_move_pe
> 
> <1> pv_move_pes -- LEAVING with ret: -253
> <1> lvm_error -- CALLED with: -253
> <1> lvm_error -- LEAVING with: "pv_move_pe(): read input PV"
> pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents
> 
> <1> lvm_unlock -- CALLED
> <1> lvm_unlock -- LEAVING with ret: 0
> 
> # vgdisplay -v
> --- Volume group ---
> VG Name               vg0
> VG Access             read/write
> VG Status             available/resizable
> VG #                  0
> MAX LV                256
> Cur LV                4
> Open LV               4
> MAX LV Size           255.99 GB
> Max PV                256
> Cur PV                5
> Act PV                5
> VG Size               19.53 GB
> PE Size               4.00 MB
> Total PE              5000
> Alloc PE / Size       2610 / 10.20 GB
> Free  PE / Size       2390 / 9.34 GB
> VG UUID               LuuTlh-HESy-ugJF-nxye-TC8f-MAe6-aIvT84
> 
> ...
> 
> --- Physical volumes ---
> PV Name (#)           /dev/hda6 (1)
> PV Status             available / allocatable
> Total PE / Free PE    1000 / 0
> 
> PV Name (#)           /dev/hda7 (2)
> PV Status             available / allocatable
> Total PE / Free PE    1000 / 1
> 
> PV Name (#)           /dev/hda8 (3)
> PV Status             available / allocatable
> Total PE / Free PE    1000 / 440
> 
> PV Name (#)           /dev/hda9 (4)
> PV Status             available / allocatable
> Total PE / Free PE    1000 / 950
> 
> PV Name (#)           /dev/hda10 (5)
> PV Status             available / NOT allocatable
> Total PE / Free PE    1000 / 999
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-02-10 12:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-02-09  9:08 [linux-lvm] error moving last PE away Christian Hammers
2002-02-09 10:16 ` [linux-lvm] SOLUTION: " Christian Hammers
2002-02-10 12:40 ` [linux-lvm] " Heinz J . Mauelshagen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).