mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrik Carlqvist <hc8@uthyres.com>
To: linux-kernel@vger.kernel.org
Subject: ocfs2 problem with nfs v2
Date: Wed, 13 Sep 2006 22:33:20 +0200	[thread overview]
Message-ID: <20060913223320.008bdcf7.hc8@uthyres.com> (raw)

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

             reply	other threads:[~2006-09-13 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 20:33 Henrik Carlqvist [this message]
2006-09-14 18:24 ` Henrik Carlqvist
2006-10-06 20:13   ` Henrik Carlqvist

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060913223320.008bdcf7.hc8@uthyres.com \
    --to=hc8@uthyres.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome