From owner-freebsd-arch@FreeBSD.ORG  Fri Sep  2 11:05:07 2005
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 16BAD16A41F
	for <freebsd-arch@freebsd.org>; Fri,  2 Sep 2005 11:05:07 +0000 (GMT)
	(envelope-from phk@phk.freebsd.dk)
Received: from haven.freebsd.dk (haven.freebsd.dk [130.225.244.222])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9ED4243D49
	for <freebsd-arch@freebsd.org>; Fri,  2 Sep 2005 11:05:06 +0000 (GMT)
	(envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (unknown [192.168.48.2])
	by haven.freebsd.dk (Postfix) with ESMTP id 2F456BC6B;
	Fri,  2 Sep 2005 11:05:02 +0000 (UTC)
To: Bruce Evans <bde@zeta.org.au>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 01 Sep 2005 23:47:15 +1000."
	<20050901201602.X99455@delplex.bde.org> 
Date: Fri, 02 Sep 2005 13:05:02 +0200
Message-ID: <35359.1125659102@phk.freebsd.dk>
Sender: phk@phk.freebsd.dk
Cc: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>, freebsd-arch@freebsd.org
Subject: Re: kern/85503: panic: wrong dirclust using msdosfs in RELENG_6 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Sep 2005 11:05:07 -0000

In message <20050901201602.X99455@delplex.bde.org>, Bruce Evans writes:

>So all current file systems need to generate unique 32-bit inode
>numbers.  This may be difficult, but once it is done I think the inode
>number can be used as a key to pass to the hash functions.  (The key
>is bogusly named "hash" in the hash function args and in v_hash above.)

Almost, but not quite correct:  The hash and inode are not and can
not be identical for remote filesystems like NFS.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.