From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pv_move failed
Date: Tue Feb 25 09:19:01 2003 [thread overview]
Message-ID: <20030225161237.A832@sistina.com> (raw)
In-Reply-To: <3E5B382B.2090908@conterra.de>; from stueken@conterra.de on Tue, Feb 25, 2003 at 10:32:27AM +0100
Dieter,
the first write to hda2 fails.
Could be a hardware installation problem with your new drive.
Have you tested if you can access hda2 fine without LVM ?
Regards,
Heinz -- The LVM Guy --
On Tue, Feb 25, 2003 at 10:32:27AM +0100, Dieter Stueken wrote:
> I just got my new 240GB disk and want to move my VG to it.
> Unfortunately I get an unexpected error:
>
> lv: /dev/backup/mirror[2] old_dev: 22:00 new_dev: 03:02
> old_pe_sector: 117703032 new_pe_sector: 357564792
> pvmove -- opening output physical volume "/dev/hda2"
> pvmove -- llseeking input physical volume "/dev/hdc"
> pvmove -- llseeking output physical volume "/dev/hda2"
> pvmove -- /dev/hdc [PE 897 [mirror [LE 2727]] -> /dev/hda2 [PE 2727] [1/247]
> pvmove -- locking physical extent 897 of "/dev/hdc" in kernel
> pvmove -- about to read input physical volume "/dev/hdc" and to write
> output physical volume "/dev/hda2"
> pvmove -- ERROR writing output physical volume "/dev/hda2" (still
> 12648448 bytes to write)
> pvmove -- ERROR "pv_move_pe(): writing output PE" moving physical extents
>
> this time I can not identify any reason an no messages on syslog.
> Any idea? What informations should I dump/post in addition?
>
> I'm using SuSE8.1 with kernel 2.4.20, the LVM-version is 1.0.5.
>
> ... and, sorry for my ill formed subject line from last week.
>
> Dieter
> --
> Dieter Stüken, con terra GmbH, Münster
> stueken@conterra.de
> http://www.conterra.de/
> (0)251-7474-501
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-02-25 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 3:33 [linux-lvm] pv_move failed Dieter Stueken
2003-02-25 9:19 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-25 12:20 Dieter Stueken
2003-02-26 4:34 Dieter Stueken
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=20030225161237.A832@sistina.com \
--to=mauelshagen@sistina.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 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.