All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stonki <stonki@gmx.de>
To: Joe Thornber <linux-lvm@sistina.com>
Subject: Re[2]: [linux-lvm] pvmove with Bad bocks
Date: Sun Oct 21 12:34:02 2001	[thread overview]
Message-ID: <7632207772.20011021193259@gmx.de> (raw)
In-Reply-To: <20011021155622.A9367@btconnect.com>

Hello Joe,

Sunday, October 21, 2001, 4:56:22 PM, schriebst Du:

JT> The first thing I would try is shrinking the filesystem and pv by one
JT> extent.  If this works the pv move should now work ok.

ok, I reduced the reiserfs from 150 GB down to 140 GB. I also reduced
the LVM to 145 GB. This worked fine without any errors...

Than I started pvmove again (linux:~ # pvmove -v /dev/hdf1 /dev/hdc1),
where hdf1 is the faulty drive and hdc1 is the new one...

linux:~ # pvmove -v /dev/hdf1 /dev/hdc1
pvmove -- checking name of source physical volume "/dev/hdf1"
pvmove -- locking logical volume manager
pvmove -- reading data of source physical volume from "/dev/hdf1"
pvmove -- checking volume group existence
pvmove -- reading data of volume group "Stonki2" from lvmtab
pvmove -- checking volume group consistency of "Stonki2"
pvmove -- searching for source physical volume "/dev/hdf1" in volume group "Stonki2"
pvmove -- building list of possible destination physical volumes
pvmove -- checking destination physical volume names in command line
pvmove -- checking volume group activity
pvmove -- moving physical extents in active volume group "Stonki2"
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/hdf1"
pvmove -- checking for enough free physical extents in "Stonki2"
pvmove -- /dev/hdf1 [PE 3319 [LV_Stonki2 [LE 27209]] -> /dev/hdc1 [PE 3319] [1/9911]
pvmove -- ERROR reading input physical volume "/dev/hdf1" (still 393216 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


so, same error.. Also also looked trough the archive of this
mailinglist. I didn't find any patch.. Only for version > 1.00. Mine
is:

linux:~ # pvmove -V
Logical Volume Manager 0.9.1_beta7
Heinz Mauelshagen, Sistina Software  10/04/2001  (IOP 10)


cu
 Stonki

  parent reply	other threads:[~2001-10-21 12:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-20  8:52 [linux-lvm] pvmove with Bad bocks Stonki
2001-10-21  7:06 ` Ragnar Kjørstad
2001-10-21  9:55   ` Joe Thornber
2001-10-21 10:45     ` Re[2]: " Stonki
2001-10-21 11:42       ` [linux-lvm] shrink lvm without harddisk ? FEJF
2001-10-22  2:44         ` Heinz J . Mauelshagen
2001-10-21 12:34     ` Stonki [this message]
2001-10-21 14:53       ` [linux-lvm] pvmove with Bad bocks Joe Thornber
2001-10-21 15:42       ` Re[2]: " Ragnar Kjørstad
2001-10-21 15:50         ` Re[4]: " Stonki
2001-10-21 18:20           ` Ragnar Kjørstad

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=7632207772.20011021193259@gmx.de \
    --to=stonki@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.