--- Begin Message ---
Subject: |
[GUIX SYSTEM]: Malfunction |
Date: |
Mon, 31 Aug 2020 05:48:30 -0400 |
Hello Guix!
[1] Out of no where, when I did `guix environment foo`, I got:
\note: build failure may have been caused by lack of free disk space
builder for `/gnu/store/2ajnpcblwpgzjdhx3050qapy3li31pr5-profile.drv'
failed with exit code 1
[2] When I redid the command 2nd time, I got:
error (ignored): cannot unlink `/tmp/guix-build-profile.drv-0':
Read-only file system
error (ignored): cannot unlink
`/gnu/store/2ajnpcblwpgzjdhx3050qapy3li31pr5-profile.drv.chroot/tmp/guix-build-profile.drv-0':
Read-only file system
guix environment: error: cannot link
`/gnu/store/.links/1jd7y4xvj853m4aygnyixci5h2y7a1py6iavp9kwzvcinyniqwbd' to
`/gnu/store/3klrs2bkcmypwnmx61q24rc7csgk19f8-profile/share/icons/Adwaita/64x64/emotes/face-smile-big
symbolic.symbolic.png': Read-only file system
[3] When I redid the command 3rd time, I got:
guix environment: error: fport_read: Connection reset by peer
[4] When I redid the command 4th time, I got:
guix environment: error: failed to connect to
`/var/guix/daemon-socket/socket': Connection refused
[5] So I tried to restart guix-daemon and got a weird output:
sudo: unable to open /var/run/sudo/ts/rg: Read-only file system
Password:
Service guix-daemon is not running.
Service guix-daemon is currently disabled.
[6] Then I tried to enable the daemon:
sudo: unable to open /var/run/sudo/ts/rg: Read-only file system
Password:
Enabled service guix-daemon.
[7] Then I tried to start the daemon:
sudo: unable to open /var/run/sudo/ts/rg: Read-only file system
Password:
Service guix-daemon has been started.
[8] Now, I retried the `guix environment foo` and got same error as in 4.
[9] At this point, all the other running applications started to throw
errors regarding read-only file-system. I could not even save the above
errors in a text editor. Glad that I had the IceCat running and I was
able to email it to myself. IceCat wasn't affected, as I think the
web-process was containerized. Everything was back to normal after restart.
[10] I am experiencing this situation for the 3rd time this month. It
never happened before this month.
INFO:
`guix describe`
guix dad963a
repository URL: https://git.savannah.gnu.org/git/guix.git
commit: dad963a4393ea51409baa63817b26b449ed58338
Both my user profile and root profile are on the same commit.
Regards,
RG.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#43132: [GUIX SYSTEM]: Malfunction |
Date: |
Mon, 14 Sep 2020 11:14:28 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Hello,
Ludovic Courtès <ludo@gnu.org> writes:
> Hey Raghav,
>
> Did you eventually find what went wrong? Should we close this bug or at
> least retitle it?
>
> Thanks,
> Ludo’.
I took Raghav to #btrfs last week, where with the help of gentle folks a
failing drive was established as the most likely culprit.
In other words, Btrfs checksuming capabilities helped quickly
discovering a hardware problem which might otherwise have silently
caused non-recoverable damage to Raghav's data.
I'm closing this bug now.
Thanks!
Maxim
--- End Message ---