[Top] [All Lists]

CVS 2.4.1-XFS module support broken?

To: <linux-xfs@xxxxxxxxxxx>
Subject: CVS 2.4.1-XFS module support broken?
From: "J. Maynard Gelinas" <gelinas@xxxxxxxxxxx>
Date: Fri, 2 Feb 2001 15:43:12 -0500 (EST)
Sender: owner-linux-xfs@xxxxxxxxxxx
   Hello folks,

   I CVS'd down the source to your XFS 2.4.1 kernel last night and built a
kernel and tools under RH-6.2 for a RAID that I'm setting up to export
home directories. The system isn't production -- yet -- so I'm willing to
experiment for the moment. However, I've run into a few problems:

a) The kernel build environment demands kgcc. Simple fix.

b) The tools build fails at the end with an error to the effect that one
needs linux-2.4.1.tar.bz2 in <build>/SOURCES ... adding the tarball
doesn't fix the error. Fortunately, it appears that critical tools such as
mkfs.xfs et all are already installed by that point.

c) With modutils-2.4.2 installed I'm getting:

[root@ctpraid1 /etc]# insmod autofs
Using /lib/modules/2.4.1-XFS/kernel/fs/autofs/autofs.o
/lib/modules/2.4.1-XFS/kernel/fs/autofs/autofs.o: unresolved symbol dput
/lib/modules/2.4.1-XFS/kernel/fs/autofs/autofs.o: unresolved symbol


/lib/modules/2.4.1-XFS/kernel/fs/autofs/autofs.o: unresolved symbol printk
/lib/modules/2.4.1-XFS/kernel/fs/autofs/autofs.o: unresolved symbol
[root@ctpraid1 /etc]# uname -a
Linux ctpraid1 2.4.1-XFS #3 Fri Feb 2 12:11:17 EST 2001 i686 unknown
root@ctpraid1 /etc]# rpm -qa | grep modutils
[root@ctpraid1 /etc]#

Module and versioning support is compiled into the kernel.

   Finally, a question: I know that reiserfs has had problems in the past
with file corruption on NFS exported volumes. Should I expect similar
issues with XFS? (Hope not!).


<Prev in Thread] Current Thread [Next in Thread>