From: georges.giralt@free.fr
To: Marek Podmaka <marki@marki-online.net>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] A hint on a process
Date: Tue, 7 Dec 2010 10:41:12 +0100 (CET) [thread overview]
Message-ID: <444802660.3510791291714872820.JavaMail.root@zimbra44-e7.priv.proxad.net> (raw)
In-Reply-To: <1728359014.3510561291714776589.JavaMail.root@zimbra44-e7.priv.proxad.net>
Hello !
Thank you both for your answer.
Marek, I've checked the grow mdadm option.
Here is what the manpage said about it :
"Normally when an array is built the "size" it taken from the smallest
of the drives. If all the small drives in an arrays are, one at a
time, removed and replaced with larger drives, then you could have an
array of large drives with only a small amount used. In this
situation, changing the "size" with "GROW" mode will allow the extra
space to start being used. If the size is increased in this way, a
"resync" process will start to make sure the new parts of the array are
synchronised.
Note that when an array changes size, any file system that may be stored
in the array will not automatically grow to use the space. The
filesystem will need to be explicitly told to use the extra space."
So if my kernel revision support it, I should change one disc at a time, with the 2 bigger disks,
wait for synchronization after every change, then ask the array to grow to reach the disks boundaries (I'll make the second partition up to the physical end of the disk).
If everything works, I just have to pvresize the above PV to get the extra space available...
If something goes south, I will still have the original 160GB disk available to start again, I hope (I do not know what exactly does the mdadm --fail command on the actual disk and data...).
I would greatly appreciate a comment from a person actually having dealt with such issues ;-)
I know I'm some sort of a coward here..... But I would not like loosing data ~:-)
Thanks !
----- Mail Original -----
De: "Marek Podmaka" <marki@marki-online.net>
À: "LVM general discussion and development" <linux-lvm@redhat.com>
Envoyé: Mardi 7 Décembre 2010 08h31:34 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [linux-lvm] A hint on a process
Hello,
Tuesday, December 7, 2010, 2:13:35, Stuart D Gathman wrote:
> Your method will fail because the raid superblock is at the end of the
> partition.
I think it should be possible - just create bigger partition on the
bigger drive, synchronize, replace 2nd drive (also with bigger
partition), synchronize and then use mdadm --grow, which should grow
the md1 device to the full partition size. Then pvresize to resize the
PV inside VG and use can use the extra space.
--
bYE, Marki
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next parent reply other threads:[~2010-12-07 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1728359014.3510561291714776589.JavaMail.root@zimbra44-e7.priv.proxad.net>
2010-12-07 9:41 ` georges.giralt [this message]
2010-12-06 22:36 [linux-lvm] A hint on a process Georges Giralt
2010-12-07 1:13 ` Stuart D Gathman
2010-12-07 7:31 ` Marek Podmaka
2010-12-12 13:20 ` Georges Giralt
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=444802660.3510791291714872820.JavaMail.root@zimbra44-e7.priv.proxad.net \
--to=georges.giralt@free.fr \
--cc=linux-lvm@redhat.com \
--cc=marki@marki-online.net \
/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;
as well as URLs for NNTP newsgroup(s).