From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: Re[2]: [linux-lvm] pvmove with Bad bocks
Date: Sun Oct 21 15:42:02 2001 [thread overview]
Message-ID: <20011021224416.B23544@vestdata.no> (raw)
In-Reply-To: <7632207772.20011021193259@gmx.de>; from stonki@gmx.de on Sun, Oct 21, 2001 at 07:32:59PM +0200
On Sun, Oct 21, 2001 at 07:32:59PM +0200, Stonki wrote:
> 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
Do you have kernel messages with ide or scsi errors in
/var/log/messages?
I think there are two potential causes of pvmove erroring out - one is a
bug related to the last allocaten extent, and one is actual disk error.
I fail to see why reducing the size will solve any problems if the cause
is a bad disk - I think you need the patch I mentioned earlier, or a
simular fix.
--
Ragnar Kjørstad
Big Storage
next prev parent reply other threads:[~2001-10-21 15:42 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 ` Re[2]: [linux-lvm] pvmove with Bad bocks Stonki
2001-10-21 14:53 ` Joe Thornber
2001-10-21 15:42 ` Ragnar Kjørstad [this message]
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=20011021224416.B23544@vestdata.no \
--to=lvm@ragnark.vestdata.no \
--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.