From: Efraim Flashner <efraim@flashner.co.il>
To: Matt Huszagh <huszaghmatt@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix system init with mounted btrfs
Date: Mon, 24 Jun 2019 14:49:24 +0300 [thread overview]
Message-ID: <20190624114924.GA1163@macbook41> (raw)
In-Reply-To: <87v9wwhusn.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
On Sun, Jun 23, 2019 at 02:10:48PM -0700, Matt Huszagh wrote:
> 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.
>
I spent some time yesterday with the arch wiki and I have an idea.
assuming you're using %desktop-services, inside services:
(modify-services %desktop-services
(udev-service-type config =>
(udev-configuration
(inherit config)
(rules (list lvm2 fuse alsa-utils crda btrfs)))))
Perhaps adding the udev rules for btrfs will force it to run 'btrfs
device scan' or whatever the magic is that it apparently isn't running
now.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-24 11:49 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
2019-06-24 11:49 ` Efraim Flashner [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190624114924.GA1163@macbook41 \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=huszaghmatt@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).