[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#428409: marked as done (lvm2: pvmove doesn't work)

Your message dated Thu, 6 Sep 2007 08:26:44 +0200
with message-id <20070906062644.GD4469@hupp.se>
and subject line pvmove does not work
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: lvm2
Version: 2.02.24-6
Severity: normal

Over the weekend I added a second disk to my box, identical to the first
once. The plan was to create a RAID1 dataset by bringing up the new disk
as a degraded array, copying / over to it, creating a new swap partition
and then migrating the LVM volume group over (everything but / is
LVMed).

Bringing up the RAID1 degraded array was fine. I then did:

pvcreate /dev/md2

which seemed to work fine and showed the physical volume fine. So I did:

vgextend raidvg /dev/md2

which resulted in vgdisplay displaying as much free space as used in the
volume group, as I expected. So I did:

pvmove -v /dev/sda3

to move everything off the unraided disk and into the raid array. And
that's where it went wrong. pvmove bombed out complaining about being
unable to parse the progress or something similar - I'm sorry, I really
should have recorded the exact error. It seemed to be complaining about
"core 1", which when I ran "dmsetup status" I could see on the first
line for the raidvg-pvmove0 device.

pvmove --abort

cleaned things up successfully, but I failed to figure out how to
correctly get pvmove to operate as expected so created a new volume
group on the RAID device and manually copied the filesystems over -
precisely the sort of thing LVM is designed to avoid I believe, but this
was my home box and I was more concerned about having it back up and
running properly than avoiding downtime due to shuffling filesystems.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-rc3 (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lvm2 depends on:
ii  libc6                        2.5-10      GNU C Library: Shared libraries
ii  libdevmapper1.02.1           2:1.02.18-1 The Linux Kernel Device Mapper use
ii  libncurses5                  5.6-3       Shared libraries for terminal hand
ii  libreadline5                 5.2-3       GNU readline and history libraries
ii  libselinux1                  2.0.15-2    SELinux shared libraries
ii  libsepol1                    2.0.3-1     Security Enhanced Linux policy lib

lvm2 recommends no packages.

-- debconf information:
  lvm2/snapshots:

--- End Message ---
--- Begin Message --- 
linux-image-2.6.22-2 is now available in Debian.

On Saturday, September 01, 2007 at 10:19:54 +0200, Fredrik Olofsson wrote:
> reassign 428409 linux-2.6
> tags 428409 fixed-upstream
> thanks
> 
> I have confirmed that upgrading to linux-image-2.6.22-2-686
> 2.6.22-4~snapshot.9356 fixes this bug. So it is not a problem of lvm2
> but of linux-2.6.
> 
> Thanks
> /Fredrik

--- End Message ---
Reply to: