linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Newbie question: ERROR "pv_move_pe(): PE lock" pv_move_pe
Date: Sat, 17 Feb 2001 09:26:43 +0000	[thread overview]
Message-ID: <E14U3db-0006f9-00@whittlesey.cl.cam.ac.uk> (raw)
In-Reply-To: Your message of Wed, 14 Feb 2001 19:18:31 +0100. <20010214191831.A12417@trez42.net>

I was unable to create RAID1 PVs under 0.9.1_beta2 (RH 7.0.90 - Fisher), so I 
used some raw partitions. I upgraded to 0.9.1_beta4 (which fixed the OOPS or 
boot - great!) and have managed to create and add the RAID PV.

I'd like to remove the old PVs, and the empty one was `vgreduce's OK, but I 
can't pvmove the data from the old one.

# pvmove /dev/hda9 
pvmove -- moving physical extents in inactive volume group "vg01"
pvmove -- WARNING: moving of active logical volumes may cause data loss!
pvmove -- do you want to continue? [y/n] y
pvmove -- ERROR "pv_move_pe(): PE lock" pv_move_pe

pvmove -- ERROR "pv_move_pe(): PE lock" moving physical extents

# 

Any ideas ?

I was hoping to HACK it pro tem, and create new LVs by specifying the PVs to 
use, but this too failed:

# lvcreate -L 50M -n repl vg01 /dev/md8
lvcreate -- rounding up size to physical extent boundary "52 MB"
lvcreate -- couldn't read physical volume "/dev/md8"

# 

Should this work ? (the man page doesn't describe `[PhysicalVolumePath...]'


Not directly LVM, but if I run out of inodes, is there some way to extend an 
ext2 FS so that the ratio of inodes/block is higher than the original FS ?


%  cat /proc/lvm/global     
LVM driver version 0.9.1_beta4 (09/02/2001)

Total:  1 VG  2 PVs  2 LVs (0 LVs open)
Global: 12656 bytes malloced   IOP version: 10   11:29:30 active

VG:  vg01  [2 PV, 2 LV/0 open]  PE Size: 4096 KB
  Usage [KB/PE]: 2097152 /512 total  122880 /30 used  1974272 /482 free
  PVs: [AA] hda9                   1048576 /256       106496 /26     942080/230
       [AA] md8                    1048576 /256            0 /0     1048576/256
    LVs: [AWDL  ] lv01                        106496 /26       close
         [ARDL  ] snap-lv01                   106496 /26       close
%

  parent reply	other threads:[~2001-02-17  9:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 18:18 [linux-lvm] LVM with devfs questions and patches Benoit Gaussen
2001-02-14 19:19 ` Andreas Dilger
2001-02-17  9:26 ` Piete Brooks [this message]
2001-02-17 10:16   ` [linux-lvm] Newbie question: ERROR "pv_move_pe(): PE lock" pv_move_pe Luca Berra
2001-02-17 10:49     ` Piete Brooks
2001-02-17 15:48       ` Joe Thornber
2001-02-17 19:04         ` Heinz J. Mauelshagen
2001-02-17 16:18       ` Andreas Dilger
2001-02-17 16:42         ` [linux-lvm] Newbie question: ERROR "pv_move_pe(): PE lock" Piete Brooks
2001-02-20 18:24           ` Andreas Dilger
2001-02-20 23:21             ` Heinz J. Mauelshagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E14U3db-0006f9-00@whittlesey.cl.cam.ac.uk \
    --to=piete.brooks@cl.cam.ac.uk \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).