[804] in arla-drinkers
Re: inode clashes (linux 2.2.x, arla 0.2x)
daemon@ATHENA.MIT.EDU (Magnus Ahltorp)
Sat May 1 18:44:46 1999
From owner-arla-drinkers@stacken.kth.se Sat May 01 22:44:45 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 22800 invoked from network); 1 May 1999 22:44:45 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 1 May 1999 22:44:45 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id AAA24068
for arla-drinkers-list; Sun, 2 May 1999 00:39:03 +0200 (MET DST)
Received: from turbot.pdc.kth.se (turbot.pdc.kth.se [130.237.221.42])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id AAA24064
for <arla-drinkers@stacken.kth.se>; Sun, 2 May 1999 00:38:59 +0200 (MET DST)
Received: (from d95-mah@localhost)
by turbot.pdc.kth.se (8.8.7/8.8.7) id AAA23404;
Sun, 2 May 1999 00:38:58 +0200 (MET DST)
To: Simon Josefsson <jas@pdc.kth.se>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: inode clashes (linux 2.2.x, arla 0.2x)
References: <ilur9p1u8go.fsf@xiphias.pdc.kth.se> <ixdzp3oaeoz.fsf@turbot.pdc.kth.se> <ilu7lqs7jc2.fsf@xiphias.pdc.kth.se>
From: Magnus Ahltorp <map@stacken.kth.se>
Content-Type: text/plain; charset="iso-8859-1"
Date: 02 May 1999 00:38:58 +0200
In-Reply-To: Simon Josefsson's message of "01 May 1999 20:09:33 +0200"
Message-ID: <ixdr9p0fm9p.fsf@turbot.pdc.kth.se>
Lines: 20
X-Mailer: Gnus v5.6.45/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
> I just discovered that using fully qualified file names tend to give
> every file in a directory the same inode number:
The inum is used in both readdir and stat. When doing stat, the inum
will be the pointer of the struct xnode. When doing readdir, there are
two possiblities:
* The file is in the xfs cache. The inum presented will be the same as
when doing stat.
* The file is not in the xfs cache. The inum presented will be the
inum calculated by arlad.
> Is it possible to use the same algorithm as the other major afs client
> vendor does? It seem to produce unique inodes even across platforms.
The problem with that algorithm is that (machine, inum)->file is not
guaranteed to be a function, which is a requirement for Linux.
/Magnus
map@stacken.kth.se
