[406] in arla-drinkers
bad inode number: 0 / xfs_syscall returns error: 0
daemon@ATHENA.MIT.EDU (Chris Chiappa)
Thu Dec 3 16:02:09 1998
From owner-arla-drinkers@stacken.kth.se Thu Dec 03 21:02:08 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 10441 invoked from network); 3 Dec 1998 21:02:07 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 3 Dec 1998 21:02:07 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id VAA24407
for arla-drinkers-list; Thu, 3 Dec 1998 21:56:29 +0100 (MET)
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 VAA24403
for <arla-drinkers@stacken.kth.se>; Thu, 3 Dec 1998 21:56:25 +0100 (MET)
Received: (from assar@localhost) by assaris.sics.se (8.9.1/8.7.3) id VAA05228; Thu, 3 Dec 1998 21:57:29 +0100 (CET)
Date: Thu, 3 Dec 1998 14:42:46 -0500
From: Chris Chiappa <griffon+arla-drinkers@lumberjack.snurgle.org>
To: arla-drinkers@stacken.kth.se
Subject: bad inode number: 0 / xfs_syscall returns error: 0
Message-ID: <19981203144246.A11466@lumberjack.snurgle.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.15i
Lines: 41
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Trying to get Arla running on a fairly generic Redhat 5.2 box, kernel
2.1.130(non-SMP), and I'm having a problem that doesn't seem to be mentioned
anywhere in the arla-drinkers archive. Kernel and Arla are both built with
gcc 2.7.2.3, arlad -t works fine, I can walk afs trees etc just fine. 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?
Only flags on the configure line are --prefix=/opt/arla and
--with-kerberos=/usr/local . I don't think I'm doing anything particularly
stupid, but it's always a possibility. The behavior is in both Arla 0.15
and 0.16, haven't tried others.
Dec 2 18:23:22 KeyserSoze kernel: EXT2-fs error (device 08:12):
ext2_read_inode: bad inode number: 0
If I enable debugging what I see if a whole slew of these errors:
Dec 3 09:35:12 KeyserSoze kernel: xfs_syscall returns error: 0
Dec 3 09:35:12 KeyserSoze kernel: sys_afs operation: 20 a_pathP: 0810afec
a_opcode: 1074550324 a_paramsP: 0810afac a_followSymlinks: 0
Dec 3 09:35:12 KeyserSoze kernel: xfs_pioctl
Dec 3 09:35:12 KeyserSoze kernel: xfs_syscall: looking up: 0810afec
Dec 3 09:35:12 KeyserSoze kernel: xfs_syscall: inode: c753453c inodenum: df3ec
Dec 3 09:35:12 KeyserSoze kernel: fhget_call: dev: 0 inode: 914412
Dec 3 09:35:12 KeyserSoze kernel: xfs_syscall returns error: 0
Dec 3 09:35:12 KeyserSoze kernel: sys_afs operation: 20 a_pathP: 0810afec
a_opcode: 1074550324 a_paramsP: 0810afac a_followSymlinks: 0
Dec 3 09:35:12 KeyserSoze kernel: xfs_pioctl
Dec 3 09:35:12 KeyserSoze kernel: xfs_syscall: looking up: 0810afec
Dec 3 09:35:12 KeyserSoze kernel: xfs_syscall: inode: c741bea8 inodenum: df3ed
Dec 3 09:35:12 KeyserSoze kernel: fhget_call: dev: 0 inode: 914413
Dec 3 09:35:12 KeyserSoze kernel: xfs_syscall returns error: 0
Dec 3 09:35:12 KeyserSoze kernel: sys_afs operation: 20 a_pathP: 0810afec
a_opcode: 1074550324 a_paramsP: 0810afac a_followSymlinks: 0
--
+------- --- -- -- -
| griffon@snurgle.N0-SPAM.org / My opinions represent snurgle.org :
! Unspoilt by progress / http://www.snurgle.org/~griffon |
- -- -- --- -------+
