From: raingloom <raingloom@riseup.net>
To: help-guix@gnu.org
Subject: Re: How do I specify a btrfs subvolume?
Date: Wed, 17 Mar 2021 02:44:25 +0100 [thread overview]
Message-ID: <20210317024425.5b6cb1de@riseup.net> (raw)
In-Reply-To: <CAEEhgEujVPWLyFChEB2hWXk2rkhGcDRCDPN-2eGsvn1hS5H_PQ@mail.gmail.com>
On Sun, 14 Mar 2021 20:33:06 -0500
Nathan Dehnel <ncdehnel@gmail.com> wrote:
> This is extremely confusing:
> https://guix.gnu.org/manual/en/html_node/Btrfs-file-system.html
>
> I made my best attempt at creating and mounting a subvolume at
> /media/offsite-backup:
>
> (file-systems
> (cons* (file-system
> (mount-point "/")
> (device
> (uuid "b2e0f449-0583-46fd-8c23-ad2e6cd661a1"
> 'btrfs))
> (type "btrfs"))
> (file-system
> (mount-point "/media/offsite-backup")
> (device
> (uuid "b2e0f449-0583-46fd-8c23-ad2e6cd661a1"
> 'btrfs))
> (type "btrfs")
> (options "subvol=offsite-backup,compress=zlib:9"))
>
> It gives this error:
>
> building
> /gnu/store/mrs1qbg619qk4n2lv8k377arclgzwqjq-install-bootloader.scm.drv...
> guix system: bootloader successfully installed on '/dev/sda' guix
> system: warning: exception caught while executing 'start' on service
> 'file-system-/media/offsite-backup': In procedure mount: mount
> "/dev/sda2" on "///media/offsite-backup": No such file or directory
> guix system: warning: some services could not be upgraded
>
> But /media/offsite-backup exists.
>
I'm looking at
https://wiki.archlinux.org/index.php/Btrfs#Mounting_subvolumes
and it seems like you either need a numberic ID or an absolute path,
not a relative one.
On my machine `findmnt` returns `subvol=/`.
next prev parent reply other threads:[~2021-03-17 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 1:33 How do I specify a btrfs subvolume? Nathan Dehnel
2021-03-17 1:44 ` raingloom [this message]
2021-03-18 2:48 ` Maxim Cournoyer
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=20210317024425.5b6cb1de@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@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.
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).