From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org, David Pirotte <david@altosw.be>
Subject: Re: Guile build failure
Date: Mon, 21 Jan 2013 10:26:54 +0100 [thread overview]
Message-ID: <87622q999d.fsf@pobox.com> (raw)
In-Reply-To: <874nocw4lr.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 09 Aug 2012 15:57:04 +0200")
On Thu 09 Aug 2012 15:57, ludo@gnu.org (Ludovic Courtès) writes:
> Hi David, and sorry for the delay,
>
> David Pirotte <david@altosw.be> skribis:
>
>> ;;; (remaining "/mnt/galia/linux/64/local/src/guile/guile-2.0.6/load-test.dir" ("." ".." ".nfs00000000121e01b200000019" ".nfs00000000121e01b30000001a"))
>
> Aaah, those hidden files are the culprit.
From http://www.redhat.com/archives/rhelv5-list/2008-May/msg00156.html:
.nfs000* are the ghosts of departed files. For example, if you have a
file handle for /home/user/foo open on an nfs client and the file gets
removed somewhere else, then the .nfs* file shows up/is used by the
original process until it closes the file handle.
Use "fuser .nfs*" to see which process is using it.
Could Guile be keeping a handle open to these files?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-01-21 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 17:02 GNU Guile 2.0.6 released David Pirotte
2012-07-10 8:18 ` Guile build failure Ludovic Courtès
2012-07-10 15:50 ` David Pirotte
2012-07-11 9:43 ` Ludovic Courtès
2012-07-19 13:59 ` David Pirotte
2012-07-19 16:02 ` Ludovic Courtès
2012-07-19 16:45 ` David Pirotte
2012-07-21 11:15 ` Ludovic Courtès
2012-07-28 15:55 ` David Pirotte
2012-08-09 13:57 ` Ludovic Courtès
2013-01-21 9:26 ` Andy Wingo [this message]
2013-01-21 10:47 ` Ludovic Courtès
2013-01-21 11:39 ` Andy Wingo
2013-01-22 16:43 ` David Pirotte
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87622q999d.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=ludo@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).