All of lore.kernel.org
 help / color / mirror / Atom feed
From: "martin.knoblauch " <"martin.knoblauch "@mscsoftware.com>
To: linux-kernel@vger.kernel.org
Subject: nfs_statfs: statfs error = 116
Date: Thu, 13 Nov 2003 15:15:24 +0100	[thread overview]
Message-ID: <3FB391FC.2090406@mscsoftware.com> (raw)

Hi,

  sorry if OT, but what is above message trying to tell me? Where can I 
find a translation of the numbers? We are seeing 116 very frequently, 
512 and 5 on occasion.


  We have a bunch of Linux clients (Dual P4, RH7.3, 2.4.20-18.7smp 
errata kernel) hanging off two Sun NFS Servers (Solaris 8) in a 
Veritas/VCS HA configuration. All of the clients show the 116 messages, 
while some of them show the 512 in addition. Those with the 512s seem to 
"hang" for some periods of time.

  The mounts are "vers=3,proto=tcp,hard,intr,bg". Some of them mounted 
at boottime, quite a few via "amd".

  Any ideas are welcome.

Thanks
Martin



             reply	other threads:[~2003-11-13 14:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13 14:15 martin.knoblauch  [this message]
2003-11-13 14:39 ` nfs_statfs: statfs error = 116 Richard B. Johnson
2003-11-13 14:52   ` Martin.Knoblauch
2003-11-13 20:26     ` Jesse Pollard
2003-11-13 20:34       ` Trond Myklebust
2003-11-14  8:43         ` Martin.Knoblauch
2003-11-14 13:49           ` Trond Myklebust
2003-11-14 14:22             ` Martin.Knoblauch
2003-11-13 15:27   ` Trond Myklebust
2003-11-13 16:00     ` Richard B. Johnson
2003-11-13 17:03       ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2003-09-18  9:56 Marc Schmitt
2003-09-18 13:49 ` Steve Dickson
2003-09-18 19:24   ` Bernd Schubert
2003-09-18 19:31     ` Marc Schmitt
2003-09-18 19:49       ` Bernd Schubert
2003-11-14 14:57         ` Marc Schmitt
2003-09-18 19:26   ` Marc Schmitt
2003-09-19  0:22     ` Neil Brown
2003-09-19  9:27       ` Marc Schmitt
2003-09-21 13:38   ` Marc Schmitt

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=3FB391FC.2090406@mscsoftware.com \
    --to="martin.knoblauch "@mscsoftware.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 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.