All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Terry Bates <tbates@mainframe.ca>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs_stat_to_errno: bad nfs status return value: 151
Date: 06 Apr 2002 03:00:59 +0200	[thread overview]
Message-ID: <shs7knld4j8.fsf@charged.uio.no> (raw)
In-Reply-To: <3CAE187B.EF7CF412@mainframe.ca>

>>>>> " " == Terry Bates <tbates@mainframe.ca> writes:

     > We're runing RedHat 7.1 and 7.2 on various machines, and they
     > all seem to be getting the same errors.  It was also happening
     > with 6.2.  Here''s a sample from the mesages file:

     > Apr 5 11:55:02 rfl0002 kernel: nfs_stat_to_errno: bad nfs
     > status return value: 151 Apr 5 11:56:19 rfl0002 kernel:
     > nfs_stat_to_errno: bad nfs status return value: 151 Apr 5
     > 11:56:19 rfl0002 kernel: nfs_stat_to_errno: bad nfs status
     > return value: 151

     > This particular machine is running RH7.1 kernel-2.4.2-2

     > Does anyone know what this 151 value means?

It is neither documented in RFC1813 nor in RFC1094. Looks like your
server is sending over its own internal error value instead of a bona
fide NFS error value. This is a server bug.

Cheers,
  Trond

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2002-04-06  1:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 21:34 nfs_stat_to_errno: bad nfs status return value: 151 Terry Bates
2002-04-06  1:00 ` Trond Myklebust [this message]

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=shs7knld4j8.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=nfs@lists.sourceforge.net \
    --cc=tbates@mainframe.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.