[1063] in arla-drinkers
Re: tests/hardlink1 fails
daemon@ATHENA.MIT.EDU (Simon Josefsson)
Sun Aug 8 11:10:01 1999
From owner-arla-drinkers@stacken.kth.se Sun Aug 08 15:10:00 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 9707 invoked from network); 8 Aug 1999 15:10:00 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 8 Aug 1999 15:10:00 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id RAA07081
for arla-drinkers-list; Sun, 8 Aug 1999 17:02:28 +0200 (MET DST)
Received: from xiphias.pdc.kth.se (xiphias.pdc.kth.se [130.237.221.226])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id RAA07077;
Sun, 8 Aug 1999 17:02:23 +0200 (MET DST)
Received: (from jas@localhost)
by xiphias.pdc.kth.se (8.8.5/8.8.5) id RAA01930;
Sun, 8 Aug 1999 17:02:22 +0200 (METDST)
To: Assar Westerlund <assar@stacken.kth.se>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: tests/hardlink1 fails
References: <iluk8ro7djz.fsf@xiphias.pdc.kth.se> <5ln1w45b9c.fsf@assaris.sics.se>
In-Reply-To: Assar Westerlund's message of "07 Aug 1999 08:57:03 +0200"
From: Simon Josefsson <jas@pdc.kth.se>
Date: 08 Aug 1999 17:02:21 +0200
Message-ID: <iluk8r69uyq.fsf@xiphias.pdc.kth.se>
Lines: 52
User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) Emacs/20.4
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=NORAD-Legion-of-Doom-KGB-PLO-Ft.-Meade-strategic-Noriega-Peking=arra"
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
--=NORAD-Legion-of-Doom-KGB-PLO-Ft.-Meade-strategic-Noriega-Peking=arra
Assar Westerlund <assar@stacken.kth.se> writes:
> Can you try the first appended patch and see if it solves that
> problem?
Yes, thanks!
> > Has anyone experienced problems running cpp on lots of files in afs?
>
> Sounds unlikely, the hardlink problem is keeping the link count of
> nodes up-to-date. It might however be caused by inode-number
> collision. I can think of two ways of figuring out what is going on:
> It might however be caused by inode-number collision. I can think
> of two ways of figuring out what is going on:
>
> 1. instrumenting cpp to see why it doesn't want to read a file.
For some reason cpp on my redhat linux box is CCCP (a cpp that is used
in stage1 when building gcc), and it does inode collition detection.
The real CPP in GCC has had inode stuff #ifdef'd out for ages (2.6?),
and should work, I didn't have the patience to wait for gcc to finish
building so I fixed CCCP instead, patch attached for reference if
anyone has experienced similar problems.
> 2. get the -current code and apply the second appended patch to your
> linux kernel and see if that gets rid of the problem.
I haven't tried it yet.
Why doesn't Transarc AFS exhibit this problem?
--=NORAD-Legion-of-Doom-KGB-PLO-Ft.-Meade-strategic-Noriega-Peking=arra
--- gcc-2.95/gcc/cccp.c~ Tue Jun 1 19:10:01 1999
+++ gcc-2.95/gcc/cccp.c Sun Aug 8 16:48:38 1999
@@ -5094,6 +5094,7 @@
pfatal_with_name (fname);
*phead = inc;
+#if 0
/* Look for another file with the same inode and device. */
if (lookup_ino_include (inc)
&& inc->control_macro
@@ -5101,6 +5102,7 @@
close (fd);
fd = -2;
}
+#endif
}
/* For -M, add this file to the dependencies. */
</#part>
--=NORAD-Legion-of-Doom-KGB-PLO-Ft.-Meade-strategic-Noriega-Peking=arra--
