bad inode number: 0 / xfs_syscall returns error: 0

[Magnus Ahltorp]

> 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