From: Sev Binello <sev-IGkKxAqZmp0@public.gmane.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] nfs_statfs: statfs error = 512 ?
Date: Wed, 23 Jan 2008 11:27:49 -0500 [thread overview]
Message-ID: <47976B05.60408@bnl.gov> (raw)
In-Reply-To: <4797699C.2020100-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
Steve Dickson wrote:
> Sev Binello wrote:
>
>> Hi -
>>
>> Can anyone explain the following error message...
>>
>> Jan 22 11:03:28 acnmcr5s kernel: nfs_statfs: statfs error = 512
>>
>> We seem to be getting it way too frequently,
>> and was wondering if it was correlated to systems becoming
>> unresponsive at times.
>>
>> Out clients are running 2.6.9-55.0.9.ELsmp, Redhat WS4 U5
>> while nfs servers are still at 2.4.21-47.ELsmp Rhat WS 3 U8
>> We are using UDP.
>>
> I *think* do recognize this problem... I believe it has to do
> with the fact the mount command can not talk to either the NFS
> server or the server daemons mountd or portmapper.
>
>
Any idea why it wouldn't be able to communicate ?
The server and daemons are up and running.
> I also believe this problem has been fixed later kernels, but
> that fix may not have made it into RHEL 3...
>
>
The problem doesn't seem to occur on WS3 clients, but does on WS4
clients ?
Can you provide any more details ?
Thanks
-Sev
> steved.
>
>
>
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
sev-IGkKxAqZmp0@public.gmane.org
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-01-23 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 15:57 [NFS] nfs_statfs: statfs error = 512 ? Sev Binello
[not found] ` <479763EC.3090601-IGkKxAqZmp0@public.gmane.org>
2008-01-23 16:21 ` Steve Dickson
[not found] ` <4797699C.2020100-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-01-23 16:27 ` Sev Binello [this message]
[not found] ` <47976B05.60408-IGkKxAqZmp0@public.gmane.org>
2008-01-23 20:37 ` Steve Dickson
[not found] ` <4797A592.4080903-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-01-23 21:10 ` Sev Binello
2009-04-24 9:35 ` rishi_nandedkar-/E1597aS9LQxFYw1CcD5bw
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=47976B05.60408@bnl.gov \
--to=sev-igkkxaqzmp0@public.gmane.org \
--cc=SteveD@redhat.com \
--cc=nfs@lists.sourceforge.net \
/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