From: Christian Hammers <ch@westend.com>
To: Linux-LVM@sistina.com
Subject: [linux-lvm] SOLUTION: error moving last PE away
Date: Sat Feb 9 10:16:02 2002 [thread overview]
Message-ID: <20020209161547.GA16631@westend.com> (raw)
In-Reply-To: <20020209150809.GC28694@westend.com>
On Sat, Feb 09, 2002 at 04:08:09PM +0100, Christian Hammers wrote:
> # pvmove -v /dev/hda10 /dev/hda8
> ...
> pvmove -- /dev/hda10 [PE 999 [lvol5 [LE 1365]] -> /dev/hda8 [PE 560] [1/1]
> pvmove -- ERROR reading input physical volume "/dev/hda10" (still 65536
> 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
A friend gave me the hint to enlarge the partition by one block. It helped,
after rebooting to let the kernel reload the partition table, pvmove ran
successfully.
The partition in question looked like:
$ LC_ALL=C fdisk -l
Disk /dev/hda: 255 heads, 63 sectors, 4867 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 8 64228+ 83 Linux
/dev/hda2 * 9 518 4096575 b Win95 FAT32
/dev/hda3 519 4867 34933342+ 5 Extended
/dev/hda5 519 773 2048256 83 Linux
/dev/hda6 774 1283 4096543+ 8e Linux LVM
/dev/hda7 1284 1793 4096543+ 8e Linux LVM
/dev/hda8 1794 2303 4096543+ 8e Linux LVM
/dev/hda9 2304 2813 4096543+ 8e Linux LVM
/dev/hda10 2814 3323 4096543+ 8e Linux LVM NOT WORKING
/dev/hda10 2814 3324 4096543+ 8e Linux LVM WORKING
[the rest of the drive was already empty]
bye,
-christian-
next prev parent reply other threads:[~2002-02-09 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 9:08 [linux-lvm] error moving last PE away Christian Hammers
2002-02-09 10:16 ` Christian Hammers [this message]
2002-02-10 12:40 ` 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=20020209161547.GA16631@westend.com \
--to=ch@westend.com \
--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).