all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Paul Garlick <pgarlick@tourbillion-technology.com>
Cc: 39727@debbugs.gnu.org
Subject: bug#39727: statx error running 'guix gc' on CentOS 7
Date: Sat, 22 Feb 2020 00:59:13 +0100	[thread overview]
Message-ID: <87sgj3ze3y.fsf@gnu.org> (raw)
In-Reply-To: <ba52a56ac48dfac9fd3a20ae7b47c502c52bc7c0.camel@tourbillion-technology.com> (Paul Garlick's message of "Fri, 21 Feb 2020 22:49:15 +0000")

Hi,

Paul Garlick <pgarlick@tourbillion-technology.com> skribis:

> After a 'guix pull' today to commit
> 536cc4aae5b58b45b974530646a4916a29a8aa6c I noticed that 'guix gc' fails
> with the message:
>
> guix gc: error: statting `/gnu/store/.links/0pck...': Invalid argument

This was during the “removing unused link” phase, right?

> The system is running CentOS 7:
>
> $ cat /etc/centos-release
> CentOS Linux release 7.7.1908 (Core)

What does “uname -r” return?

This is most likely an issue with the ancient kernel being used.

It would be nice if you could try running a C program that does
something like this:

	struct statx st;
	if (statx(AT_FDCWD, "/",
		  AT_SYMLINK_NOFOLLOW | AT_STATX_DONT_SYNC,
		  STATX_SIZE | STATX_NLINK, &st) == -1)
          printf ("failed: %m\n");

It should fail similarly.  Then you can try commenting out
AT_STATX_DONT_SYNC and see whether it fails.

Let me know how it goes!

Thanks,
Ludo’.

  reply	other threads:[~2020-02-22  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 22:49 bug#39727: statx error running 'guix gc' on CentOS 7 Paul Garlick
2020-02-21 23:59 ` Ludovic Courtès [this message]
2020-02-24 12:52   ` Paul Garlick
2020-02-24 15:12     ` Ludovic Courtès
2020-02-24 19:51       ` Paul Garlick
2020-02-26 21:07         ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgj3ze3y.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39727@debbugs.gnu.org \
    --cc=pgarlick@tourbillion-technology.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.