public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rearranging hard drives and data.
Date: Sat, 19 Dec 2020 13:19:05 -0600	[thread overview]
Message-ID: <fd7ffc65-18a9-50c9-a9a6-5f57ed69a26a@gmail.com> (raw)
In-Reply-To: <37f509ee-491e-045d-a840-e53d7d41a078@youngman.org.uk>

antlists wrote:
> On 19/12/2020 17:32, Dale wrote:
>> Neil Bothwick wrote:
>>> On Sat, 19 Dec 2020 07:02:23 -0600, Dale wrote:
>>>
>>>> I have another question related to LVM.  Let's say a system crashes
>>>> and
>>>> dies.  Or I just move a drive, or drives, with LVM on it to another
>>>> system.  Does the system just recognize the drives and knows how to
>>>> add
>>>> them or do I have to do that manually on the new system?
>>> It should just work if you move all the PVs in the volume group. One
>>> thing to watch out for is if the destination system is already using
>>> LVM,
>>> the volume groups must be named differently. That's why I always use
>>> unique VG names based on the hostname.
>>>
>>
>> Ahhh, so it stores the info on the drive so that it knows what it is.
>> Neato!!  I was thinking it was in /etc/lvm/ or something.  I've wondered
>> about that for a while now.
>
> mdadm version 0 stored its information in mdadm.conf. That was a
> mistake - it had the downside you couldn't boot from the array, it was
> wide open to errors, arrays were regularly trashed because things had
> got confused, etc etc. Sticking all the necessary information in a
> superblock is now considered must-do good practice.
>>
>> Naming them based on hostname is also a good idea.  I don't have mine
>> named that way but if I ever redo them, I will.  It could save me some
>> problems down the road.
>>
> Again, that's now the default for mdadm - not necessarily the user
> name, but the internal array name is something like "tigger:0", to
> quote one of mine - array 0 created on tigger.
>
> Cheers,
> Wol
>
>


Right now, this is mine:


root@fireball / # vgs
VG            #PV #LV #SN Attr   VSize    VFree 
Home2        2   1   0 wz--n-  <12.74t      0
OS               1   3   0 wz--n- <124.46g <35.46g
backup        1   1   0 wz--n-  698.63g      0
root@fireball / #


I'm assuming it would be best to have them named like this:


root@fireball / # vgs
VG            #PV #LV #SN Attr   VSize    VFree 
fb-Home2        2   1   0 wz--n-  <12.74t      0
fb-OS               1   3   0 wz--n- <124.46g <35.46g
fb-backup        1   1   0 wz--n-  698.63g      0
root@fireball / #


The added fb would be short for fireball.  If this rig suddenly blew a
gasket and I stuck the drives in a new system, it would make them
different at least.  Once moved and stable, Neil says I can rename it to
something else to match the new system.  It sounds like a good idea
since right now, I could move those drives to a system that has the same
names which would cause issues.  As a matter of fact, the reason for
Home2 is because I already had a Home group in a previous move.  I guess
we are talking about the same thing.

Dale

:-)  :-) 


  reply	other threads:[~2020-12-19 19:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 13:02 [gentoo-user] Rearranging hard drives and data Dale
2020-12-19 13:47 ` bobwxc
2020-12-19 16:51 ` David Haller
2020-12-19 17:28   ` Dale
2020-12-19 18:37   ` antlists
2020-12-19 18:49     ` David Haller
2020-12-19 20:10       ` antlists
2020-12-19 21:31         ` David Haller
2020-12-19 23:21           ` Wols Lists
2020-12-19 17:06 ` Neil Bothwick
2020-12-19 17:32   ` Dale
2020-12-19 17:48     ` Neil Bothwick
2020-12-19 17:54       ` Dale
2020-12-19 21:48         ` Neil Bothwick
2020-12-20  1:02           ` Dale
2020-12-19 18:55     ` antlists
2020-12-19 19:19       ` Dale [this message]
2020-12-20  1:06 ` Frank Steinmetzger
2020-12-20  3:01   ` Dale
2020-12-20 14:21     ` Frank Steinmetzger
2020-12-20 22:37       ` Dale
2020-12-20 10:03   ` antlists
2020-12-20 13:20     ` Frank Steinmetzger
2020-12-20 13:39       ` Mark Knecht
2020-12-21  0:33       ` antlists
2020-12-21  0:20 ` Dale
2020-12-21  2:52   ` William Kenworthy
2020-12-21  9:19     ` Dale
2020-12-21 11:26       ` Frank Steinmetzger
2020-12-25  9:41         ` Dale
2020-12-21 10:48   ` Frank Steinmetzger
2020-12-21 12:53     ` Dale
2020-12-22  0:12       ` antlists
2020-12-24 16:38         ` Dale
2020-12-24 20:33           ` Frank Steinmetzger
2020-12-25  9:15             ` 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=fd7ffc65-18a9-50c9-a9a6-5f57ed69a26a@gmail.com \
    --to=rdalek1967@gmail.com \
    --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