From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Brent Clements <bclem@rice.edu>
Cc: NFS@lists.sourceforge.net
Subject: Re: input/output error
Date: 07 Mar 2003 18:00:34 +0100 [thread overview]
Message-ID: <shs65qv6ril.fsf@charged.uio.no> (raw)
In-Reply-To: <1047055047.30015.18.camel@batman.ece.rice.edu>
>>>>> " " == Brent Clements <bclem@rice.edu> write
> rtcfiler:/users/users /users nfs
> rw,v3,rsize=32768,wsize=32768,soft,udp,lock,addr=rtcfiler 0 0
^^^^
Read up on the 'soft' mount option in 'man 5 nfs'.
Cheers,
Trond
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-03-07 17:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 16:37 input/output error Brent Clements
2003-03-07 17:00 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-22 15:44 Input/Output error Srinivasan T
2011-02-22 20:21 ` Eric Sandeen
2011-02-23 6:33 ` Srinivasan T
2011-02-23 16:32 ` Eric Sandeen
2011-02-23 21:55 ` Dave Chinner
2011-02-23 0:47 ` Dave Chinner
2002-09-20 14:06 Input/output error Kenneth Johansson
2001-11-22 13:04 Marcus Grando
2001-11-22 13:17 ` Rasmus Bøg Hansen
2001-11-23 15:43 ` Hartmut Holz
2001-11-23 18:29 ` Andreas Dilger
2001-11-23 18:50 ` Marcus Grando
2001-11-23 20:20 ` Hartmut Holz
2001-11-23 19:10 ` Tom Eastep
2001-11-25 22:50 ` Horst von Brand
2001-11-26 0:05 ` Russell King
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=shs65qv6ril.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=NFS@lists.sourceforge.net \
--cc=bclem@rice.edu \
/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.