From: Reid Sutherland <mofino@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Soft mounts
Date: Tue, 7 Dec 2004 19:32:55 -0500 [thread overview]
Message-ID: <6a0fc8d704120716324e11dc22@mail.gmail.com> (raw)
It seems soft mounts only work if the NFS server is alive and not
completely offline. We have some hardware issues with one of our NFS
servers. So to keep things moving we use soft mounts, but when the
server gets powered down and rebooted, soft mounts are meaningless.
The processes are not killable, until the server comes back
(regardless of timeout) From what I understand the 'intr' option is
also flawed in this same manner.
Am I just seeing things or is this a serious problem?
I also do not like the argument that NFS insists on keeping the
processes open even if the server is down for data integrity purposes.
I should be able to safely turn on that insane behaviour. I
personally need the FS error as my mail delivery method is NFS/FS
safe.
On a side note, what the hell is with NFS caching?!? Without it I get
about 700 _KB_ per second, with it I can get 88 _MB_ per second. I
have no tested this with 2.6, this was with 2.4. But on the flip
side, I have to sometimes 'touch' directories to have them re-read. I
would love to disable it.
Thanks in advance for any insight you can give me.
-reid
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2004-12-08 0:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a0fc8d704120716324e11dc22@mail.gmail.com \
--to=mofino@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=reid@vianet.ca \
/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