From: Jack Hill <jackhill@jackhill.us>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Corrupt/missing store items
Date: Tue, 22 Jun 2021 15:29:41 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2106221520040.2109@marsh.hcoop.net> (raw)
In-Reply-To: <8735t9ybyd.fsf@elephly.net>
On Tue, 22 Jun 2021, Ricardo Wurmus wrote:
> Jack Hill <jackhill@jackhill.us> writes:
>
> What happens if you try “guix build --check --no-grafts
> /gnu/store/zkhymfsbrv0s4y7l778g78k6y65nidxd-gnutls-3.6.16.drv” or similar?
> The database probably states that
> /gnu/store/jlk67v3nddhv0z963wfvahk8fc8gqcz8-gnutls-3.6.16 has already been
> built, so with “--check” you might be able to make it build it again.
`guix gc --verify=repair` fixed the problem, so I won't be able to test
this (unless this recurs, but I hope it doesn't).
>> So Guix think's it's sucessfully built gnutls, but it's still not
>> present in the store. I've also tried copying the store items from
>> other hosts. No luck so far…
>
> How did that fail?
I didn't capture verbose output, but I believe nothing was sent because
the problematic host reported it already had that item.
> How could the directory have disappeared? Guix appears to be very surprised
> that the directory is missing.
Apologies for leaving out more details about this host earlier. The
filesystem is btrfs and its a virtual machine running in someone else's VM
cluster. I had to reset and boot into older generations a few times before
I noticed the problem because of a misconfiguration I made. Some of these
older generation involved downgrading the kernel from 5.12 to 5.11. I
suppose that could have caused file system corruption, although I would
not have expected the store to be written to at the time of the resets.
Best,
Jack
prev parent reply other threads:[~2021-06-22 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 18:30 Corrupt/missing store items Jack Hill
2021-06-21 20:28 ` Jack Hill
2021-06-22 8:20 ` Christopher Baines
2021-06-22 13:21 ` Jack Hill
2021-06-22 13:45 ` Jack Hill
2021-06-22 18:46 ` Ricardo Wurmus
2021-06-22 19:29 ` Jack Hill [this message]
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=alpine.DEB.2.21.2106221520040.2109@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).