All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Doubled PV
Date: Tue May 27 06:11:02 2003	[thread overview]
Message-ID: <20030527130119.B8518@sistina.com> (raw)
In-Reply-To: <1053561043.12809.166.camel@localhost>; from markus@bluegap.ch on Thu, May 22, 2003 at 01:50:43AM +0200

Markus,

what _exactly_ happened during the pvmove ?
Would help to analyze any pvmove bug.

Using LVM2 tools is a good idea.

You'll have text metadata that way, would be able to hand-edit it removing
the 10 LEs and vgcfgrestore the changed metadata back onto the PVs.


On Thu, May 22, 2003 at 01:50:43AM +0200, Markus Schiltknecht wrote:
> Hello everybody
> 
> I just read that it's not recommended to run LVM on top of Softraid
> devices. Why is that? Looks like a perfect combination to me.
> 
> However. Recently two (?!?) disks of a RAID5 device got bad sectors. The
> RAID array stopped immediately. Recreating the RAID with 'mkraid -R', I
> could save most of its data. I did move it away with 'pvmove'.
> 
> Then - only 10 PE remaining on the bad PV - I decided to use 'pvmove -i'
> to remove those faulty PE's. That worked. But now my VG is in a silly
> state: because 'pvmove' touched the bad sectors, the RAID shut down,
> i.e. the whole PV (/dev/md/20) was no longer writeable nor readable. So
> pvmove couldn't write to /dev/md/20, not even LVM metadata in an intact
> area.
> 
> Now /dev/md/20 is still registered as part of myVG. Aktivating it again
> with 'mkraid -R /dev/md20' I can pvdisplay on it and all metadata seems
> okay, but like before the 'pvmove -i'. Those 10 LE's are still on there.
> 
> 'vgscan -v' outputs the following, somewhat silly message:
> 
> vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
> vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- scanning for all active volume group(s) first
> vgscan -- reading data of volume group "myVG" from physical volume(s)
> vgscan -- only found 6561 of 6551 LEs for LV /dev/myVG/data (2)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get
> data of volume group "myVG" from physical volume(s)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume
> group
> 
> 
> That's exactly 10 LEs too much!
> 
> I don't mind too much about the data in those 10 LEs. But I would like
> to be able to activate myVG again!
> 
> How can I tell it, to forget about /dev/md/20? Do I have to use LVM2
> tools? I've read through the mailing list, but didn't find the proper
> tool / command.
> 
> Thanks for your help
> 
> Markus
> 
> 
> 
> 
> _______________________________________________
> 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/

-- 

Regards,
Heinz    -- The LVM Guy --

*** 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:[~2003-05-27  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 18:51 [linux-lvm] Doubled PV Markus Schiltknecht
2003-05-27  6:11 ` Heinz J . Mauelshagen [this message]
2003-05-29 12:20   ` Markus Schiltknecht

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=20030527130119.B8518@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.