From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] i2o devices and lvm Error on LE versus PE
Date: Mon Sep 22 05:06:02 2003 [thread overview]
Message-ID: <20030922115453.V2618@sistina.com> (raw)
In-Reply-To: <200309201114.40369.g.murano@vinsoft.it>; from gingiabios@email.it on Sat, Sep 20, 2003 at 01:54:18PM +0200
On Sat, Sep 20, 2003 at 01:54:18PM +0200, Gianmichele Murano wrote:
> HI ALL
>
> as first thing, i say hallo to you.
>
> now i tell you my problem:
> on a controler raid (i2o devices) i have a debian distro.
> Recently i have enlarged the logical volumes on this controler.
> All seemed ok, i was able to remount the file systems and to copy and install
> programs and data on resized volumes.
>
> So, i was out of office and the development server was tuned off by person who
> wasn't me (so i don't know what is the matter, if happened any thing ).
Are all Physical Volumes accessible (run pvscan and analyze) ?
If any are missing that is likely to explain your problem.
It is hard to help you here without knowing what happened to the system :(
Of course you can use a metadata backup and restore it but this is no
good advice either without knowing which changes have been made (i.e. multiple
lvcreate/lvremove/lvextend/lvreduce meanwhile) and which metadata backup
should be restored, preusmably _all_ PVs are accessible.
You want to read pvcreate and vgcfgrestore manual pages and use
the -ll option of vgcfgrestore to analyze your backup contents.
>
> later, when in was in office i have turn on the server and the vgscan failed,
> it said " ..omissis... only found 499 of 500 LE for LV
> /dev/volume1/lgv1(0)" .
> I don't undestand what was happened.
> It is possible that a bad tuned off make a problem as this?
> Any body know the answer?
>
> To solve the trouble i thinked to do in this way:
> to reduce the LV lgv1 of some LE , in this way the info about the number of LE
> will rewrite and (i hope) the problem vanish.The idea seems good, isn't?
> But i can't do this because the volume group is inactive.
> Anybody know a method to active a volume group also if vgscan fail?
>
> Please, i MUST to recove the data on the lv, we don't have a backup policy
> >:^>
>
>
>
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-09-22 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 7:02 [linux-lvm] i2o devices and lvm Error on LE versus PE Gianmichele Murano
2003-09-22 5:06 ` Heinz J . Mauelshagen [this message]
2003-09-23 5:44 ` Gingia
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=20030922115453.V2618@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.