From: Vagrant Cascadian <vagrant@debian.org>
To: David Wilson <david@daviwil.com>, help-guix@gnu.org
Subject: Re: Diagnosing "In procedure symlink: No space left on device"
Date: Mon, 10 Feb 2020 09:53:18 -0800 [thread overview]
Message-ID: <87sgjil46p.fsf@ponder> (raw)
In-Reply-To: <2fe8237a-8e46-4a13-bcf3-28849d699d73@www.fastmail.com>
On 2020-02-10, David Wilson wrote:
> Recently on one of my machines I've not been able to update one of my
> profiles due to a "No space left on device" error (see snippet below).
> My device is most definitely not out of space (/dev/dm-0 has 42gb
> free):
>
> ---
> λ df -h
> Filesystem Size Used Avail Use% Mounted on
> none 7.8G 0 7.8G 0% /dev
> /dev/dm-0 234G 180G 42G 82% /
...
> Is there some other reason that Guix might think that I'm out of
> space? Is there any other command I can run that might help
> illuminate why I'm getting this error?
Maybe you've run out of inodes?
df -i
live well,
vagrant
next prev parent reply other threads:[~2020-02-10 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 17:30 Diagnosing "In procedure symlink: No space left on device" David Wilson
2020-02-10 17:53 ` Vagrant Cascadian [this message]
2020-02-10 18:07 ` David Wilson
2020-02-10 18:06 ` Julien Lepiller
2020-02-10 18:07 ` David Wilson
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=87sgjil46p.fsf@ponder \
--to=vagrant@debian.org \
--cc=david@daviwil.com \
--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).