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 16:10:00 -0500 [thread overview]
Message-ID: <4797AD28.8020306@bnl.gov> (raw)
In-Reply-To: <4797A592.4080903-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
Steve Dickson wrote:
> Sev Binello wrote:
>
>> The problem doesn't seem to occur on WS3 clients, but does on WS4
>> clients ?
>>
> Again, I'm pretty sure this problem was identified and fixed in
> an later update release... you could try updating to the latest
> and greatest (U7).
>
I just want to make sure I'm clear on this point...
The problem *appears on the * *WS4 U5* clients running2.6.9-55.0.9.ELsmp
*NOT* with the *WS3 U8* servers.
Are you saying a problem on WS3 servers is causing this error to appear
on the WS4 clients,
but not on the WS3 clients ?
>> Can you provide any more details ?
>>
> An a bzip2 tethereal network trace something similar to
> tethereal -w /tmp/data.pcap host <server> and host <server;
> bzip2 /tmp/data.pcap
>
> should shed some light on whats going on...
>
> Note: so as not to fill up everybody's inbox with tethereal
> data, either open a bug report on bugzilla.redhat.com or
> set the data to me in a private email.
>
>
Okay will do 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 21:11 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
[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 [this message]
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=4797AD28.8020306@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