linux-kernel - ocfs2 problem with nfs v2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060913223320.008bdcf7.hc8@uthyres.com>
Date:	Wed, 13 Sep 2006 22:33:20 +0200
From:	Henrik Carlqvist <hc8@...yres.com>
To:	linux-kernel@...r.kernel.org
Subject: ocfs2 problem with nfs v2

I am trying to setup a redundant NFS server using ocfs2 on a shared disk
between two servers. So far I have only configured ocfs2 on one server,
but I have already seen a problem.

The NFS server works fine for Solaris and Linux NFS v3 clients, but old
linux boxes using NFS v2 have problems with the server.

The NFS clients which are able to reproduce the problem have Slackware 4
installed, this is what things look like on a problematic NFS v2 client:

$ uname -sr
Linux 2.2.6
$ ls ~henhi
/bin/ls: /home/aphus/22/henhi: Operation not supported on transport
endpoint 
$ cat /proc/mounts | grep aphus/22
svinapa:/export/aphus22 /home/aphus/22 nfs rw,intr,addr=svinapa 0 0

At the same time that the NFS client says "Operation not supported..." I
get the following in the logs on the NFS server:
Sep 13 15:50:20 kattapa kernel: (5385,0):ocfs2_encode_fh:155 ERROR: fh
buffer is too small for encoding

The NFS server has Red Hat Enterprise Linux ES release 4 installed with
kernel 2.6.9-42.ELsmp and ocfs2-2.6.9-42.ELsmp-1.2.3-1.i686.rpm was
downloaded from Oracles web.

Red Hat 4 and Slackware 4 might sound as releases that should match each
other, but Slackware 4 was released 1999. As the old 2.2.6 kernel does not
have support for NFS v3 but only NFS v2 my guess is that this might
trigger the bug. I have tried to increase rsize and wsize to 8192, but it
didn't help.

Does anybody know what causes "fh buffer is too small for encoding"?

regards Henrik
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/