Messages in this thread | | | Subject | Re: [NFS] Re: broken umount -f | From | Trond Myklebust <> | Date | 16 Jan 2003 14:17:50 +0100 |
| |
>>>>> " " == 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |