[218] in arla-drinkers
Re: arla, an AFS implementation
daemon@ATHENA.MIT.EDU (Magnus Ahltorp)
Thu Aug 20 21:46:54 1998
From owner-arla-drinkers@stacken.kth.se Fri Aug 21 01:46:54 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 7145 invoked from network); 21 Aug 1998 01:46:53 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 21 Aug 1998 01:46:53 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id DAA14552
for arla-drinkers-list; Fri, 21 Aug 1998 03:42:24 +0200 (MET DST)
Received: from yakko.stacken.kth.se (map@yakko.stacken.kth.se [130.237.234.52])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id DAA14547;
Fri, 21 Aug 1998 03:42:18 +0200 (MET DST)
Received: (from map@localhost)
by yakko.stacken.kth.se (8.8.8/8.8.7) id DAA04953;
Fri, 21 Aug 1998 03:41:27 +0200 (CEST)
To: Derrick J Brashear <shadow@dementia.org>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: arla, an AFS implementation
References: <Pine.LNX.3.95L.980820201215.5564A-100000@jooky.dementia.org>
From: Magnus Ahltorp <map@stacken.kth.se>
Date: 21 Aug 1998 03:41:27 +0200
In-Reply-To: Derrick J Brashear's message of Thu, 20 Aug 1998 20:14:44 -0400 (EDT)
Message-ID: <lv1emub1588.fsf@yakko.stacken.kth.se>
Lines: 25
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
> Speaking of cwd problems, I have a report from someone who wishes not to
> step forward...:
> Fresh boot of arla, 2.1.115:
> foo# mystat /afs
> File: "/afs"
> Size: 8192 Filetype: Directory
> Mode: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ wheel)
> Device: 0,2 Inode: -86972672 Links: 2
> ok so far.
> foo# ls /afs
> [...]
> foo# mystat /afs
> File: "/afs"
> Size: 8192 Filetype: Directory
> Mode: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ wheel)
> Device: 8,1 Inode: -86972672 Links: 2
>
> Notice what happens to device....
This is perfectly normal. I do a lot of magic with the inodes' device
numbers. I set the device numbers of the inode to the device numbers
of the cached inode to be able to do bmap directly.
/Magnus
map@stacken.kth.se
