Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with pvmove
Date: Mon, 10 Sep 2001 13:17:50 +0200	[thread overview]
Message-ID: <20010910131750.E31313@sistina.com> (raw)
In-Reply-To: <20010909.16553000@host.domain.de>; from estevesgorf@freenet.de on Sun, Sep 09, 2001 at 04:55:30PM +0000

Andreas,

could you provide a "pvdisplay -v | tail -22" output of the PV in question
in order to check if you suffer from a misalocation problem which would lead
to a last PE being allocated partially beyond the end of the underlying devive.

Regards,
Heinz    -- The LVM Guy --


On Sun, Sep 09, 2001 at 04:55:30PM +0000, Andreas Gorf wrote:
> I've followed the discussion started by „fejf“.
> 
> Indeed i have the same problem that pvmove exits with an error when i try 
> to
> move PEs from one PV to another.
> 
> To exclude the possibility of a defect HD i tried to reproduce the error 
> on several
> independent systems.
> 
> The error always occurs when i try to move a complete filled PV to 
> another. In this case all but the last
> PE on this PV are moved. The last one isn't movable whatever i did.
> 
> If the PV wasn't filled at 100% everything goes fine.
> 
> To reproduce the error try the following:
> 
> - create a VG with three Pvs at the same size
> - create a LV which covers the first PV completely and the second partly
> - try to all PEs from the first PV to the third - the error will occur
> - move the moved PEs back to the first PV - everything goes fine
> - try to move the PEs lying on the second PV to the third - everything 
> goes fine
> 
> 
> ...any ideas?
> 
> 
> Andreas...
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-09-10 11:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 16:55 [linux-lvm] Problems with pvmove Andreas Gorf
2001-09-10 11:17 ` Heinz J . Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-14 18:45 Nils Juergens

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=20010910131750.E31313@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox