all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Upgrading storage on bordeaux.guix.gnu.org
Date: Tue, 07 Dec 2021 14:26:39 -0500	[thread overview]
Message-ID: <87a6hcjjww.fsf@gmail.com> (raw)
In-Reply-To: <87pmq9nbfe.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Mon, 06 Dec 2021 13:51:49 +0100")

Hello,

Ludovic Courtès <ludo@gnu.org> writes:

> Hello!
>
> (+Cc: Andreas.)
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> [space is running out on bayfront, so I wrote:]
>>
>>> Remember that I’ve got three 256G SSDs here that I could send to
>>> wherever bayfront now sits.  With LVM or a RAID configuration these
>>> could just be added to the storage pool — if bayfront has
>>> sufficient slots for three more disks.
>>
>> You wrote in response:
>>
>>> Good to know.  In that case we’d need to come up with (1) an updated
>>> Guix System config with LVM, and (2) a way to copy the existing
>>> store
>>> over to the new storage, which sounds tricky if the existing disk is
>>> to
>>> be kept.
>>
>> We could first install Guix System with the adjusted bayfront config
>> on a separate machine (e.g. on a build node at the MDC), onto a volume
>> with LVM (using as many of the SSDs as needed). Copy signing keys etc
>> from bayfront.  Then we’d pretty much export/import the bayfront store
>> over the network.  Once everything has been copied, we turn off
>> bayfront, swap the disks, boot it up again.  If everything works all
>> right we add the original disk (and any unused left-over disks) to the
>> LVM volume to extend the storage pool.
>
> Sounds like a plan.  But note that there’s the store and there’s the
> cached nars, though maybe we can tolerate missing, say, a week or two of
> nars.

I don't know anything about the Bayfront machine specifics, but if it
was running with a Btrfs file system, it could be extendable live by
adding the new drives to it in Btrfs RAID0 configuration.

Cheers,

Maxim


  reply	other threads:[~2021-12-07 19:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24  8:52 Update on bordeaux.guix.gnu.org Christopher Baines
2021-11-28 17:26 ` Ludovic Courtès
2021-11-28 19:54   ` Ricardo Wurmus
2021-12-01 17:42     ` Ludovic Courtès
2021-12-01 22:04       ` Ricardo Wurmus
2021-12-06 12:51         ` Upgrading storage " Ludovic Courtès
2021-12-07 19:26           ` Maxim Cournoyer [this message]
2021-12-03 10:17     ` Update " Christopher Baines
2021-12-03 11:18       ` Ricardo Wurmus
2021-12-03  9:39   ` Christopher Baines

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=87a6hcjjww.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.