> Next up was my Ubuntu 6.10-based MythTV machine. I again added in the
> new drive, partitioned it, and pvcreated an LVM. I then did vgextend,
> and executed pvmove. Unfortunately, this is a good way to screw up your
> system if you're using Ubuntu. The included LVM, library, and driver
> version are all a couple of minor versions behind what I have setup in
> my Slackware server. This, mixed with the dm-raid package's age, seems
> to be a recipe for unhappyness. The easiest way I could fix this was to
> reboot the machine (since the pvmove will lock up the entire lvm
> subsystem), and then do a pvmove --abort. This managed to recover the
> setup (since it was in an inconsistent pv-alloced state, where some of
> the new drive was dedicated to things...), and allowed me to vgreduce to
> remove the new drive.
Actually its a bug, I seem to recall, in the kernel. Its only
triggered with a pvmove if the pv is in use.
Since then I always go to single user mode before using pvmove.
Received on Wed Mar 14 09:29:06 2007
This archive was generated by hypermail 2.1.8 : Wed Mar 14 2007 - 09:29:14 CST