Linux LVM users
 help / color / mirror / Atom feed
From: Dan Boger <lvm@peeron.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] more pvmove problems
Date: Wed, 11 Aug 2004 15:31:26 -0400	[thread overview]
Message-ID: <20040811193126.GT32074@peeron.com> (raw)

I've tried to search online, and found some mentions of a patch, but I
can't be sure if it applies to my case.

Setup:
Redhat 7.2
LVM 1.0.8 from source

One of my drives started reporting read errors, so I got a new one, and
wanted to replace it.  Since I was replacing a 200G drive with a 250G, I
too the chance to get rid of the 30G drive in there too.

Added the new drive, created a PV on it, added it to the VG and moved
the 30G drive to it with pvmove, no problem.  Then I started moving the
200G drive over.  

Had an error early in the process, so I had to retry with the -i flag.
It kept failing, so after reading up in the man page, I was able to copy
the rest of the PV using the -n flag:

  pvmove -v -i -n medialv:61-6076 /dev/hde /dev/hdh

36 hours later, the process finished.  Now I figured I still need to
move the first 60 PEs.  But whatever I try, I can't get pvmove to work.

Here's what pvscan reports (hde is the drive I'm trying to retire):
  pvscan -- reading all physical volumes (this may take a while...)
  pvscan -- ACTIVE   PV "/dev/hdg" of VG "mediavg" [189.88 GB / 0 free]
  pvscan -- ACTIVE   PV "/dev/hdh" of VG "mediavg" [233.72 GB / 17.84 GB free]
  pvscan -- ACTIVE   PV "/dev/hde" of VG "mediavg" [189.88 GB / 187.97 GB free]
  pvscan -- inactive PV "/dev/hdd" is in no VG  [27.96 GB]
  pvscan -- ACTIVE   PV "/dev/hdb" of VG "mediavg" [74.47 GB / 0 free]
  pvscan -- total: 5 [716.10 GB] / in use: 4 [688.14 GB] / in no VG: 1 [27.96 GB]

And here's what I get when I try "pvmove -vv /dev/hde":
  pvmove -- checking name of source physical volume "/dev/hde"
  pvmove -- locking logical volume manager
  pvmove -- reading data of source physical volume from "/dev/hde"
  pvmove -- checking volume group existence
  pvmove -- reading data of volume group "mediavg" from lvmtab
  pvmove -- checking volume group consistency of "mediavg"
  pvmove -- searching for source physical volume "/dev/hde" in volume group "mediavg"
  pvmove -- building list of possible destination physical volumes
  pvmove -- checking volume group activity
  pvmove -- moving physical extents in active volume group "mediavg"
  pvmove -- WARNING: if you lose power during the move you may need
          to restore your LVM metadata from backup!
  pvmove -- do you want to continue? [y/n] y
  pvmove -- starting to move extents away from physical volume "/dev/hde"
  pvmove -- checking for enough free physical extents in "mediavg"
  lv: /dev/mediavg/medialv[1]  old_dev: 33:00  new_dev: 34:64  old_pe_sector: 65920  new_pe_sector: 452788608
  pvmove -- opening output physical volume "/dev/hdh"
  pvmove -- llseeking input physical volume "/dev/hde"
  pvmove -- llseeking output physical volume "/dev/hdh"
  pvmove -- /dev/hde [PE 0 [medialv [LE 0]]] -> /dev/hdh [PE 6908] [1/61]
  pvmove -- locking physical extent 0 of "/dev/hde" in kernel
  pvmove -- about to read input physical volume "/dev/hde" and to write output physical volume "/dev/hdh"
  pvmove -- remapping physical extent in VGDA of kernel
  pvmove -- ERROR "Invalid argument" remapping
  pvmove -- ERROR "pv_move(): LE of LV remap" moving physical extents

  zsh: exit 23    sudo pvmove -vv /dev/hde

Any suggestions?  At this point, I'm willing to lose some data off the
drive, just so I can remove it and remount my partition.

If there's any other information I can provide, I'd be happy to.

Thanks!

Dan

-- 
Dan Boger
lvm@peeron.com

                 reply	other threads:[~2004-08-11 20:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040811193126.GT32074@peeron.com \
    --to=lvm@peeron.com \
    --cc=linux-lvm@redhat.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