From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Overlapping logical volumes
Date: Mon Nov 3 04:11:02 2003 [thread overview]
Message-ID: <20031103111117.F1850@sistina.com> (raw)
In-Reply-To: <1293.435T2650T11474321tom@carrott.org>; from tom@carrott.org on Sat, Nov 01, 2003 at 07:07:53PM +1200
On Sat, Nov 01, 2003 at 07:07:53PM +1200, Tom Parker wrote:
> Hi,
>
> I have just experianced a rather nasty bug in lvextend. I grew a logical
> volume and it used extents that were already in use for another logical
> volume.
You're the first reporting.
Do you have abn archive copy in /etc/lvmconf representing that situation still ?
If so, send it to me please <mge@sistina.com>.
>
> I'm using Debian Woody and Linux 2.4.22 (unpatched Linus kernel.org sources)
>
> amislave:/# lvextend --help
>
> Logical Volume Manager 1.0.4
> Heinz Mauelshagen, Sistina Software 02/05/2002 (IOP 10)
>
> Luckily I noticed the corrupting filesystems fairly quickly and was able to
> mostly recover the situation with minimal losses. Currently I still have the
> two overlapping logical volumes and a lot less trust in the LVM than I had
> before.
>
> Is there a program that can validate the logical volume configuration and
> ensure that no physical extent is allocated to more the one logical volume?
vgck
>
> When extending a logical volume, or creating a new one, is anything written to
> the newly allocated extents?
While extending, the answer is no.
If creating, the answer is ye, unless you "lvcreate -Zn ...".
> If this were to happen again, and I discovered
> the problem before I made use of the extra space or a new logical volume,
> would I have any corruption of the first logical volume to use the extents in
> question?
As said, use "lvcreate -Zn ..." in order to avoid writing zerores to the first
KB of the new LV (this is necessary because fs mounts can crash your system
otherwise on an un'fscked LV).
>
> To finish my data recovery, I would like to allocate another large logical
> volume, I'm somewhat wary of doing this without a tool to ensure that the
> group is valid.
Do an "lvcreate -Zn ...", run vgck and check the "lvdisplay -v ..." output
on all your LVs if there's any overlaps again. If so, that's the archive copy
you want to send to me.
>
> --
> Tom Parker - tom@carrott.org
> - http://www.carrott.org
>
>
> _______________________________________________
> 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-11-03 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 0:10 [linux-lvm] Overlapping logical volumes Tom Parker
2003-11-03 4:11 ` Heinz J . Mauelshagen [this message]
2003-11-03 5:33 ` Tom Parker
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=20031103111117.F1850@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.