From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: ptb@it.uc3m.es
Cc: Mike Black <mblack@csihq.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8 NFS Problems
Date: Fri, 7 Sep 2001 14:36:20 +0200 [thread overview]
Message-ID: <15256.48964.101213.439253@charged.uio.no> (raw)
In-Reply-To: <200109071206.OAA24577@nbd.it.uc3m.es>
In-Reply-To: <shsae07md9d.fsf@charged.uio.no> <200109071206.OAA24577@nbd.it.uc3m.es>
>>>>> " " == Peter T Breuer <ptb@it.uc3m.es> writes:
>> Soft mount timeouts are not only due to network problems, but
>> can equally well be due to internal congestion. The rate at
>> which the network can transmit requests is usually (unless you
>> are using Gigabit) way below the rate at which your machine can
>> generate them.
> But soft mounts at least break nicely and automatically. And
> since failures are inevitable, I prefer them.
The problem is that they need careful tuning if they are to work at
all. They assume a perfect setup.
For instance most servers will drop UDP requests if they don't have a
free thread to serve them. They assume that you will automatically
retry. soft mounts do retry, but give up eventually. IOW even on an
otherwise working setup you will, every once in a blue moon, get an
EIO due to a soft timeout and you will lose data.
Cheers,
Trond
next prev parent reply other threads:[~2001-09-07 12:36 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 [this message]
2001-09-07 13:13 ` Mike Black
2001-09-07 14:42 ` Trond Myklebust
2001-09-07 15:46 ` Mike Black
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=15256.48964.101213.439253@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mblack@csihq.com \
--cc=ptb@it.uc3m.es \
/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.