From: "Christian Völker" <chrischan@knebb.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVs corrupted after pvresize
Date: Fri, 17 Oct 2008 06:05:15 +0200 [thread overview]
Message-ID: <48F80EFB.30404@knebb.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0810161829570.14457@bmsred.bmsi.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yohoo!
|> I resized one of these RAID arrays for additional 250GB. After this was
| Resizing a RAID-5 array is often not what you think, and doing so often
| scrambles the data, depending on what RAID implementation you are using.
I'm using a hardware RAID 3ware 9500S Controller. And this guy offers
migration from RAID10 (4disks) to RAID5 (4disks, but with larger capacity).
And I already did this task several times on these types of controllers.
| In any case, LVM was not your problem.
This answer is too simple to be true.
After the resize the partition and the PV were recognized correctly! So
I'm pretty sure the migration was ok.
But after the deletion of the partion, recreation and pvcreate
everything went wrong. So for me it is obvious, LVM had an issue. But
which one?
Greets
Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFI+A770XNIYlAXmzsRAicJAKCpogPKLWhuOtABRI/cBthIRVwlHACZAcoi
b7+z+RaIKUKnui+b8XLqtw0=
=TSoe
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-10-17 4:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 21:09 [linux-lvm] LVs corrupted after pvresize Christian Völker
2008-10-16 22:31 ` Stuart D. Gathman
2008-10-17 4:05 ` Christian Völker [this message]
2008-10-17 5:23 ` Peter Larsen
2008-10-20 15:41 ` Stuart D. Gathman
2008-10-20 18:50 ` Peter Larsen
2008-10-21 11:13 ` Morten Torstensen
2008-10-21 14:07 ` Larry Dickson
2008-10-21 14:44 ` Stuart D. Gathman
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=48F80EFB.30404@knebb.de \
--to=chrischan@knebb.de \
--cc=linux-lvm@redhat.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.