From: Matt Huszagh <huszaghmatt@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: guix system init with mounted btrfs
Date: Sun, 23 Jun 2019 14:10:48 -0700 [thread overview]
Message-ID: <87v9wwhusn.fsf@gmail.com> (raw)
In-Reply-To: <87v9wwscbm.fsf@nckx> (Tobias Geerinckx-Rice's message of "Sun, 23 Jun 2019 14:42:05 +0200")
Tobias Geerinckx-Rice <me@tobias.gr> writes:
Matt Huszagh <huszaghmatt@gmail.com> writes:
> Ok, so I've simplified the subvolume layout somewhat:
> mount -t btrfs -o compress=lzo LABEL=btrfs /mnt
> btrfs subvolume create /mnt/@guixsd
> btrfs subvolume create /mnt/@home
> btrfs subvolume create /mnt/@snapshots
> umount /mnt
> o_btrfs=defaults,X-mount.mkdir,compress=lzo,ssd,noatime
>
> mount -o subvol=@guixsd,$o_btrfs LABEL=btrfs /mnt
> mount -o subvol=@home,$o_btrfs LABEL=btrfs /mnt/home
> mount -o subvol=@snapshots,$o_btrfs LABEL=btrfs /mnt/.snapshots
> mount -o X-mount.mkdir /dev/nvme0n1p1 /mnt/boot/efi
I think I was a bit hasty in saying this worked. Another possible reason
is guix system init doesn't try to do anything with these directories
anyway so maybe the fact that these subvolumes are "supported" is a
false positive.
I've tried an even simpler layout: no subvolumes, just
mount -t btrfs -o defaults,compress=lzo,ssd,noatime LABEL=btrfs /mnt
mount -o X-mount.mkdir /dev/nvme0n1p1 /mnt/boot/efi
However, I'm experiencing the same decryption error with this setup.
next prev parent reply other threads:[~2019-06-23 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 2:05 guix system init with mounted btrfs Matt Huszagh
2019-06-23 12:42 ` Tobias Geerinckx-Rice
2019-06-23 12:47 ` Tobias Geerinckx-Rice
2019-06-23 17:36 ` Matt Huszagh
2019-06-23 21:10 ` Matt Huszagh [this message]
2019-06-24 11:49 ` Efraim Flashner
2019-06-24 14:51 ` Matt Huszagh
2019-06-24 17:54 ` Matt Huszagh
2019-06-25 6:27 ` Efraim Flashner
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=87v9wwhusn.fsf@gmail.com \
--to=huszaghmatt@gmail.com \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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.