From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Tim Connors <tconnors@astro.swin.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [NFS] Re: broken umount -f
Date: 16 Jan 2003 14:17:50 +0100 [thread overview]
Message-ID: <shsd6mxp729.fsf@charged.uio.no> (raw)
In-Reply-To: <200301160955.h0G9ttZ27704@hexane.ssi.swin.edu.au>
>>>>> " " == Tim Connors <tconnors@astro.swin.edu.au> writes:
> What I have never understood, is that if you are reading a
> file, or even just in a directory, and the server goes down,
> and won't come back up (say, you have taken your laptop into
> work, and forgot to turn off autofs first, after killing all
> shells that had cd'd to the nfs directory), then you still are
> destined to have to reboot. You could sever all connections to
> the nfs server safely, because nothing is being written there
> (except maybe atime information - but not in the case of a
> shell being cd'd to an nfs path). But linux won't give up on
> the connection. Come on, what harm could possibly come to an
> application that has only readonly files open, or cwd in an NFS
> path? No data loss would occur in this situation, so just drop
> the connection, and return -EIO to anything that then later
> wants to read a file.
Care to contribute the code?
Cheers,
Trond
next prev parent reply other threads:[~2003-01-16 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030114160031$24bb@gated-at.bofh.it>
2003-01-16 9:55 ` [NFS] Re: broken umount -f Tim Connors
2003-01-16 13:17 ` Trond Myklebust [this message]
2003-01-14 15:56 Lever, Charles
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=shsd6mxp729.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=tconnors@astro.swin.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).