From: Julien Lepiller <julien@lepiller.eu>
To: Giovanni Biscuolo <g@xelera.eu>,
Raghav Gururajan <raghavgururajan@disroot.org>,
43132@debbugs.gnu.org
Subject: bug#43132: [GUIX SYSTEM]: Malfunction
Date: Mon, 31 Aug 2020 08:07:45 -0400 [thread overview]
Message-ID: <0819FC2B-8BCA-4479-8CFC-800DF7098EB6@lepiller.eu> (raw)
In-Reply-To: <87pn77cbou.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
No, it's supposed to be like that. /gnu/store is mounted read-only (on the guix system) to prevent you from writing to it. The guix daemon has write access to the store when it wants to add a new item, or garbage collect.
Le 31 août 2020 07:11:13 GMT-04:00, Giovanni Biscuolo <g@xelera.eu> a écrit :
>Hello Raghav
>
>when forwarding the output of commands next time, plz beware your MUS
>does not reformat the relevant :-)
>
>This seems as a system issue on your side, not a Guix bug
>
>Raghav Gururajan <raghavgururajan@disroot.org> writes:
>
>>> It seems connected to a filesystem issue: can you also tell us
>what's
>>> the output of "mount"?
>
>[...]
>
>> w on / type btrfs
>> (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
>
>[...]
>
>> /dev/mapper/secondary on /gnu/store type btrfs
>> (ro,relatime,ssd,space_cache,subvolid=5,subvol=/)
>
>I see two problems here:
>
>1. the btrfs volume /dev/mapper/secondary seems mounted twice, and with
>the same subvolume; I never tryed to mount the same btrfs volume on two
>different mountpoints: is this the reason your /gnu/store is read-only?
>
>2. /gnu/store is mounted read-only, that's why you get the errors
>
>Please can you try removing the mounting of /gnu/store from your
>filesystem configuration (or fstab if on a foreign distro)?
>
>[...]
>
>HTH! Gio'
>
>--
>Giovanni Biscuolo
>
>Xelera IT Infrastructures
[-- Attachment #2: Type: text/html, Size: 2156 bytes --]
next prev parent reply other threads:[~2020-08-31 12:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 9:48 bug#43132: [GUIX SYSTEM]: Malfunction Raghav Gururajan
2020-08-31 9:53 ` Efraim Flashner
2020-08-31 10:01 ` Raghav Gururajan
2020-08-31 10:39 ` Giovanni Biscuolo
2020-08-31 10:48 ` Raghav Gururajan
2020-08-31 11:11 ` Giovanni Biscuolo
2020-08-31 12:07 ` Julien Lepiller [this message]
2020-08-31 12:40 ` Giovanni Biscuolo
2020-08-31 21:17 ` Danny Milosavljevic
2020-09-01 3:04 ` Raghav Gururajan
2020-09-01 7:58 ` Danny Milosavljevic
2020-09-10 7:56 ` Ludovic Courtès
2020-09-14 15:14 ` Maxim Cournoyer
2020-09-14 19:34 ` Ludovic Courtès
2020-09-15 11:51 ` Raghav Gururajan
2020-09-15 13:31 ` Maxim Cournoyer
2020-09-15 22:13 ` Mark H Weaver
2020-09-15 22:38 ` Raghav Gururajan
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=0819FC2B-8BCA-4479-8CFC-800DF7098EB6@lepiller.eu \
--to=julien@lepiller.eu \
--cc=43132@debbugs.gnu.org \
--cc=g@xelera.eu \
--cc=raghavgururajan@disroot.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).