From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting maximum space out of a hard drive
Date: Thu, 25 Aug 2022 17:08:17 -0400 [thread overview]
Message-ID: <CAGfcS_nVwEpmwHsQbB1JKQedTR7LfT=eZUeCrQYCs9eBz7k26A@mail.gmail.com> (raw)
In-Reply-To: <d960be97-8183-a264-f86a-5eb3e6c21e21@gmail.com>
On Thu, Aug 25, 2022 at 2:59 PM Dale <rdalek1967@gmail.com> wrote:
>
> While at it, can I move the drives on LVM to another system without
> having to copy anything? Just physically move the drives and LVM see
> them correctly on the new system?
As long as we aren't talking about boot partitions/sectors, the answer
is yes. As long as all the drives are attached and accessible by the
kernel (necessary drivers/etc present), then LVM will put them
together. It doesn't care where it finds them, as all the necessary
metadata is stored on the drives and gets scanned.
If you're talking about boot partitions/sectors then it isn't a huge
problem, but you do need to ensure the bootloader can find the right
drives/etc, as it isn't nearly as flexible and may need updates if the
drives switch order/etc, at least for legacy bootloaders.
--
Rich
next prev parent reply other threads:[~2022-08-25 21:08 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 18:04 [gentoo-user] Getting maximum space out of a hard drive Dale
2022-08-18 18:18 ` Rich Freeman
2022-08-19 2:03 ` Dale
2022-08-19 4:26 ` David Haller
2022-08-24 22:45 ` Frank Steinmetzger
2022-08-25 6:22 ` William Kenworthy
2022-08-25 12:43 ` Dale
2022-08-25 12:52 ` Rich Freeman
2022-08-25 15:10 ` Jack
2022-08-25 18:59 ` Dale
2022-08-25 21:08 ` Rich Freeman [this message]
2022-08-25 23:59 ` Dale
2022-08-26 0:15 ` Mark Knecht
2022-08-26 11:26 ` Dale
2022-08-26 11:55 ` Gerrit Kuehn
2022-08-26 12:07 ` Rich Freeman
2022-08-26 23:07 ` Dale
2022-08-26 14:09 ` Mark Knecht
2022-08-26 14:25 ` Rich Freeman
2022-08-26 14:40 ` Mark Knecht
2022-08-26 23:20 ` Dale
2022-08-26 23:37 ` Mark Knecht
2022-08-27 1:16 ` Mark Knecht
2022-08-27 23:30 ` Dale
2022-08-28 9:27 ` Michael
2022-08-28 21:07 ` Frank Steinmetzger
2022-08-28 21:33 ` Wol
2022-08-28 21:53 ` Mark Knecht
2022-08-28 23:31 ` Wol
2022-08-28 21:34 ` Frank Steinmetzger
2022-08-29 5:49 ` Dale
2022-08-29 14:42 ` Frank Steinmetzger
2022-08-29 21:28 ` Dale
2022-08-30 14:26 ` Frank Steinmetzger
2022-08-25 22:41 ` Wols Lists
2022-08-25 23:56 ` Dale
2022-08-26 7:24 ` Wols Lists
2022-08-26 11:27 ` Dale
2022-08-26 13:35 ` Wols Lists
2022-08-26 4:47 ` David Haller
2022-08-18 18:20 ` Andreas Fink
2022-08-20 19:15 ` Dale
2022-08-20 20:57 ` Rich Freeman
2022-08-25 3:44 ` Dale
2022-08-20 21:46 ` Grant Taylor
2022-08-20 21:57 ` Grant Taylor
2022-08-20 22:45 ` Dale
2022-08-21 4:22 ` William Kenworthy
2022-08-21 5:34 ` Grant Taylor
2022-08-21 9:26 ` William Kenworthy
2022-08-21 10:09 ` Dale
2022-08-21 16:47 ` Dale
2022-08-21 5:27 ` Grant Taylor
2022-08-24 22:39 ` Frank Steinmetzger
2022-08-24 22:50 ` Wol
2022-08-22 14:50 ` Laurence Perkins
2022-08-22 15:02 ` Rich Freeman
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='CAGfcS_nVwEpmwHsQbB1JKQedTR7LfT=eZUeCrQYCs9eBz7k26A@mail.gmail.com' \
--to=rich0@gentoo.org \
--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