From: "Mike Black" <mblack@csihq.com>
To: <trond.myklebust@fys.uio.no>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8 NFS Problems
Date: Fri, 7 Sep 2001 11:46:05 -0400 [thread overview]
Message-ID: <04c301c137b4$34604590$e1de11cc@csihq.com> (raw)
In-Reply-To: LINKIFYHCafaAeICHGcEFFbHadBaFcAHHebFeDGdaGcCJGdLINKIFYIHIGdeFGGHCecEHeaIJCbJCDbCHaBHcEFFCHGDCfLINKIFYGEdBcGEJCbdCHGEfbeJGBFAceAcDfebJHeDBIcAB <15256.56528.460569.700469@charged.uio.no>
But did you notice the network log:
07:02:07.481323 yeti.csihq.com.686186576 > picard.csihq.com.nfs: 1472 write
[|nfs] (frag 28948:1480@0+)
07:02:07.481446 yeti.csihq.com > picard.csihq.com: (frag 28948:1480@1480+)
07:02:07.481569 yeti.csihq.com > picard.csihq.com: (frag 28948:1480@2960+)
07:02:07.481692 yeti.csihq.com > picard.csihq.com: (frag 28948:1480@4440+)
07:02:07.481814 yeti.csihq.com > picard.csihq.com: (frag 28948:1480@5920+)
07:02:07.481886 yeti.csihq.com > picard.csihq.com: (frag 28948:916@7400)
07:02:07.482321 picard.csihq.com.nfs > yeti.csihq.com.686186576: reply ok
136 write [|nfs] (DF)
07:02:07.482511 yeti.csihq.com.702963792 > picard.csihq.com.nfs: 108 commit
[|nfs] (DF)
07:02:07.482642 picard.csihq.com.nfs > yeti.csihq.com.702963792: reply ok
128 commit (DF)
The file is being copied from yeti to picard. Last packet seen is picard
telling yeti "OK" after the commit.
If soft timeouts were occurring shouldn't we be seeing packets from yeti
again with no response from picard?
________________________________________
Michael D. Black Principal Engineer
mblack@csihq.com 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page
FAX 321-676-2355
----- Original Message -----
From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
To: "Mike Black" <mblack@csihq.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Sent: Friday, September 07, 2001 10:42 AM
Subject: Re: 2.4.8 NFS Problems
>>>>> " " == Mike Black <mblack@csihq.com> writes:
> But my timeouts were only 10 seconds -- well below the timeo
> and retrans timeout periods. And my network traffic shows that
According to the 'nfs' manpage, the default timeo on the mount in
util-linux is usually 0.7 seconds. retrans is 3.
0.7 + 1.4 + 2.8 = 4.9 seconds < 10...
> this is the client causing the problem NOT the server. It's
> the read() that pauses for 10 seconds and then the NFS write
> immediately returns EIO. So...I don't think soft mounts has
> anything to do with it.
I think it does.
Cheers,
Trond
next prev parent reply other threads:[~2001-09-07 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 11:56 2.4.8 NFS Problems Mike Black
2001-09-07 11:49 ` Trond Myklebust
2001-09-07 12:05 ` Peter T. Breuer
2001-09-07 12:27 ` Trond Myklebust
2001-09-07 12:36 ` Trond Myklebust
2001-09-07 13:13 ` Mike Black
2001-09-07 14:42 ` Trond Myklebust
2001-09-07 15:46 ` Mike Black [this message]
2001-09-08 10:53 ` Trond Myklebust
2001-09-08 11:53 ` Mike Black
-- strict thread matches above, loose matches on Subject: below --
2001-12-20 9:44 Steffen Persvold
2001-12-20 11:10 ` Trond Myklebust
2001-12-20 14:40 ` Steffen Persvold
2001-12-20 20:27 ` Trond Myklebust
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='04c301c137b4$34604590$e1de11cc@csihq.com' \
--to=mblack@csihq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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