[1064] in arla-drinkers
Re: tests/hardlink1 fails
daemon@ATHENA.MIT.EDU (Assar Westerlund)
Sun Aug 8 11:18:50 1999
From owner-arla-drinkers@stacken.kth.se Sun Aug 08 15:18:49 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 9730 invoked from network); 8 Aug 1999 15:18:48 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 8 Aug 1999 15:18:48 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id RAA07362
for arla-drinkers-list; Sun, 8 Aug 1999 17:13:00 +0200 (MET DST)
Received: from assaris.sics.se (assaris.sics.se [193.10.66.108])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id RAA07358
for <arla-drinkers@stacken.kth.se>; Sun, 8 Aug 1999 17:12:56 +0200 (MET DST)
Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id RAA71457; Sun, 8 Aug 1999 17:13:50 +0200 (CEST)
From: Assar Westerlund <assar@stacken.kth.se>
To: Simon Josefsson <jas@pdc.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> <iluk8r69uyq.fsf@xiphias.pdc.kth.se>
Mime-Version: 1.0 (generated by tm-edit 7.68)
Content-Type: text/plain; charset=US-ASCII
Date: 08 Aug 1999 17:13:50 +0200
In-Reply-To: Simon Josefsson's message of "08 Aug 1999 17:02:21 +0200"
Message-ID: <5lpv0ye24x.fsf@assaris.sics.se>
Lines: 27
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Simon Josefsson <jas@pdc.kth.se> writes:
> Assar Westerlund <assar@stacken.kth.se> writes:
>
> > Can you try the first appended patch and see if it solves that
> > problem?
>
> Yes, thanks!
Good, I have commited that code.
> 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.
It would still be good to know if we solved the problem, there might
be other programs that do inode caching stuff.
> Why doesn't Transarc AFS exhibit this problem?
To my understanding, Transarc AFS always use the normal hash algoritm
for fabricating inode numbers, which would mean that once you got two
files that hash to the same inode number the kernel would consider
them the same file. It would be good to try to fabricate a test case
for this, but I haven't done so yet.
/assar
