From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CPU upgrade and LVM questions.
Date: Thu, 6 Dec 2018 14:03:05 -0700 [thread overview]
Message-ID: <181f8d16-d2cf-89a8-78e5-eade93f26fdd@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <492d8bf4-4b8d-f7f6-05d8-2473b6825fab@gmail.com>
On 12/06/2018 02:27 AM, Dale wrote:
> From what I've read, I can use pvmove and pvremove to replace that drive.
> Just tell pv to move the data and when done, remove the old drive. After
> that, the new 6TB drive will be used in that PV and the 3TB drive can
> be used for something else. Is it really that easy or is there more to
> it than that? Pardon me but that doesn't sound complicated enough to me.
I've migrated multiple hundreds of TB of data this way.
In short:
1) Partition the new drive(s) as desired.
2) pvcreate /dev/$newPv
3) vgextend $vgName /dev/$newPv
4) pvmove /dev/$oldPv /dev/$newPv
5) vgreduce $vgName /dev/$oldPv
6) pvremove /dev/$oldPv
This does work well, even if the LV(s) are in use / file system(s) are
mounted.
I have occasionally had issues where the system seems to not respond,
despite the fact that it is doing what it's supposed to. I wonder if
it's related to the memory leak that J. Roeleveld was talking about.
Note: I /do/ *STRONGLY* recommend that you do partition the new drive
and /not/ pvcreate the entire drive. — Many of the data recovery tools
/expect/ there to be a partition table. Those that don't care are happy
to work with a partition table. I've seen others be in a very
uncomfortable situation when they /didn't/ use a partition table.
Simple easy thing to avoid painting yourself into a corner.
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2018-12-06 21:03 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 9:27 [gentoo-user] CPU upgrade and LVM questions Dale
2018-12-06 10:03 ` Neil Bothwick
2018-12-06 15:17 ` Dale
2018-12-06 16:51 ` J. Roeleveld
2018-12-06 18:36 ` Corbin Bird
2018-12-06 20:58 ` Dale
2018-12-06 21:24 ` Jack
2018-12-06 21:55 ` Dale
2018-12-07 1:06 ` Corbin Bird
2018-12-07 1:17 ` Dale
2018-12-07 5:10 ` Dale
2018-12-07 6:22 ` [gentoo-user] " Nikos Chantziaras
2018-12-07 7:30 ` Dale
2018-12-07 10:49 ` Alec Ten Harmsel
2018-12-07 23:47 ` Nikos Chantziaras
2018-12-07 23:59 ` Dale
2018-12-09 18:23 ` Taiidan
2018-12-09 18:57 ` J. Roeleveld
2018-12-09 22:41 ` Dale
2018-12-10 21:33 ` Taiidan
2018-12-10 22:14 ` Neil Bothwick
2018-12-10 22:54 ` Dale
2018-12-11 2:00 ` Taiidan
2018-12-11 8:49 ` Neil Bothwick
2018-12-11 9:23 ` Mick
2018-12-11 10:48 ` Dale
2018-12-11 15:14 ` J. Roeleveld
2018-12-11 22:46 ` Adam Carter
2018-12-11 23:56 ` Dale
2018-12-12 2:15 ` Adam Carter
2018-12-11 10:20 ` Alan Mackenzie
2018-12-11 15:03 ` J. Roeleveld
2018-12-07 8:47 ` [gentoo-user] " Neil Bothwick
2018-12-07 8:58 ` Dale
2018-12-06 21:02 ` [gentoo-user] " Nikos Chantziaras
2018-12-06 21:45 ` Dale
2018-12-06 22:22 ` Nikos Chantziaras
2018-12-06 23:23 ` Dale
2018-12-06 23:40 ` Nikos Chantziaras
2018-12-07 0:19 ` Dale
2018-12-07 10:01 ` Peter Humphrey
2018-12-07 12:41 ` Dale
2018-12-07 16:51 ` Peter Humphrey
2018-12-08 1:01 ` Dale
2018-12-08 2:51 ` Nikos Chantziaras
2018-12-08 4:39 ` Dale
2018-12-08 5:33 ` David Haller
2018-12-08 5:45 ` Dale
2018-12-08 6:00 ` Nikos Chantziaras
2018-12-08 6:28 ` David Haller
2018-12-08 4:23 ` David Haller
2018-12-08 5:35 ` Dale
2018-12-08 6:06 ` David Haller
2018-12-08 5:38 ` David Haller
2018-12-08 9:40 ` Peter Humphrey
2018-12-08 9:50 ` Peter Humphrey
2018-12-06 21:03 ` Grant Taylor [this message]
2018-12-09 22:45 ` [gentoo-user] " Dale
2018-12-10 1:35 ` Grant Taylor
2018-12-10 2:38 ` Dale
2018-12-10 3:37 ` Grant Taylor
2018-12-10 9:27 ` Neil Bothwick
2018-12-10 16:00 ` Dale
2018-12-08 17:49 ` Alexander Puchmayr
2018-12-08 18:23 ` Dale
2018-12-08 19:09 ` J. Roeleveld
2018-12-08 20:48 ` Dale
2018-12-11 10:41 ` Dale
2018-12-22 23:58 ` Dale
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=181f8d16-d2cf-89a8-78e5-eade93f26fdd@spamtrap.tnetconsulting.net \
--to=gtaylor@gentoo.tnetconsulting.net \
--cc=gentoo-user@lists.gentoo.org \
/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