xfs
[Top] [All Lists]

Problems With 2.4 XFS-NFS CVS Tree/Linux 2.6.15.1 Client

To: linux-xfs@xxxxxxxxxxx
Subject: Problems With 2.4 XFS-NFS CVS Tree/Linux 2.6.15.1 Client
From: "Sean P. Elble" <elbles@xxxxxxxxxx>
Date: Mon, 23 Jan 2006 11:06:20 -0500 (EST)
Sender: linux-xfs-bounce@xxxxxxxxxxx
Hi,

I have 2 servers setup, one is strictly a file server with a 100 GB drive formatted with XFS (with the operating system residing on another drive formatted as ext2), exporting shares via NFS from both the XFS partition and the ext2 partitions. The ext2 partitions export fine, and can be read fine on the "client" (really, the server that does most of the work, which is running the 2.6.15.1 kernel), but there are major issues with the XFS partition. It seems to export fine, and I can run an ls at the top of the NFS mount, but nothing else works, and I mean nothing else. What follows is the output of the mount, pwd, and ls commands on the client:

/dev/md0 on / type ext3 (rw)
/dev/proc on /proc type proc (rw)
/dev/sys on /sys type sysfs (rw)
/dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
/dev/shm on /dev/shm type tmpfs (rw)
/dev/md1 on /usr type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/proc on /var/named/chroot/proc type none (rw,bind)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
intranet:/ on /mnt/intranet type nfs (rw,addr=192.168.0.1)
intranet:/home on /mnt/intranet_home type nfs (rw,addr=192.168.0.1)
/mnt/intranet_home
ls: cannot read symbolic link ftp: Input/output error
total 24K
drwxr-xr-x    6 root   root    68 Jan 17 13:14 .
drwxr-xr-x    4 root   root  4.0K Jan 14 01:58 ..
lrwxrwxrwx    1 root   root    25 Jul 23  2005 ftp
drwxr-xr-x    6 elbles admin   57 Jan 14 21:07 httpd
drwxr-xr-x  380 elbles admin  12K Dec 15 13:32 mp3s
drwxr-xr-x    2 root   root    22 Dec 17 02:04 netlogon
drwxr-xr-x    9 root   root    98 Jul 23  2005 network
$[elbles@zeus intranet_home]$ cd mp3s/
-bash: cd: mp3s/: Stale NFS file handle

That same message occurs for any instance of file access on the client, on that NFS export. Normally, I'd think a NFS problem, but since this only happens on the XFS file system, I'm thinking it's a bug in the XFS code. The NFS server is running a CVS checkout of the 2.4 XFS tree from sometime around 11:00 PM EST on January 19th. And yes, I know it is not wise to run a CVS tree of a kernel on a machine, but this machine needs to run a recent 2.4 kernel, and I also need POSIX ACL support (in addition to XFS) support. Also, some quick output from the NFS server from nfsstat:

Server rpc stats:
calls      badcalls   badauth    badclnt    xdrcall
457        4          4          0          0
Server nfs v2:
null       getattr    setattr    root       lookup     readlink
0       0% 0       0% 0       0% 0       0% 0       0% 0       0%
read       wrcache    write      create     remove     rename
0       0% 0       0% 0       0% 0       0% 0       0% 0       0%
link       symlink    mkdir      rmdir      readdir    fsstat
0       0% 0       0% 0       0% 0       0% 0       0% 0       0%

Server nfs v3:
null       getattr    setattr    lookup     access     readlink
8       1% 49     10% 0       0% 32      7% 24      5% 11      2%
read       write      create     mkdir      symlink    mknod
0       0% 0       0% 0       0% 0       0% 0       0% 0       0%
remove     rmdir      rename     link       readdir    readdirplus
0       0% 0       0% 0       0% 0       0% 0       0% 11      2%
fsstat     fsinfo     pathconf   commit
318    69% 4       0% 0       0% 0       0%

There are *NO* messages in the dmesg log or /var/log/messages about NFS. If anyone needs more information, I will gladly post it ASAP. If anyone can help me with this issue, I'd really appreciate it. Thanks, in advance.

-Sean Elble


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