[408] in arla-drinkers
Re: bad inode number: 0 / xfs_syscall returns error: 0
daemon@ATHENA.MIT.EDU (Magnus Ahltorp)
Thu Dec 3 18:53:47 1998
From owner-arla-drinkers@stacken.kth.se Thu Dec 03 23:53:47 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 12648 invoked from network); 3 Dec 1998 23:53:46 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 3 Dec 1998 23:53:46 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id AAA25830
for arla-drinkers-list; Fri, 4 Dec 1998 00:46:44 +0100 (MET)
Received: (from map@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id AAA25824;
Fri, 4 Dec 1998 00:46:38 +0100 (MET)
To: Chris Chiappa <griffon+arla-drinkers@lumberjack.snurgle.org>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: bad inode number: 0 / xfs_syscall returns error: 0
References: <19981203144246.A11466@lumberjack.snurgle.org>
From: Magnus Ahltorp <map@stacken.kth.se>
Date: 04 Dec 1998 00:46:38 +0100
In-Reply-To: Chris Chiappa's message of Thu, 3 Dec 1998 14:42:46 -0500
Message-ID: <lv14srcyejl.fsf@sundance.stacken.kth.se>
Lines: 17
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
> But if I do an insmod xfs.o, run arlad and then 'mount -t xfs arla
> /afs', any operations on /afs simply cause the kernel to spit out
> the attached error messages(and many more, but they're all
> essentially similar). Any ideas?
What happens with the operations you do on /afs? Do they succeed, fail
or hang?
> Dec 2 18:23:22 KeyserSoze kernel: EXT2-fs error (device 08:12):
> ext2_read_inode: bad inode number: 0
This is not very good, but should not cause any big problems. You
might have to switch to normal filehandling instead of xfs file
handles. But, I need more information from you on the above question
first.
/Magnus
