lkml.org 
[lkml]   [2001]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: 2.4.8 NFS Problems
From
>>>>> " " == Peter T Breuer <ptb@it.uc3m.es> writes:

> It would be nice if nfs could do the a remount automatically
> when the nfs handle it has goes stale an dit discovers it. Is
> that part of v3 nfs or not?

The exact wording in RFC1813 is

NFS3ERR_STALE
Invalid file handle. The file handle given in the
arguments was invalid. The file referred to by that file
handle no longer exists or access to it has been
revoked.

The problem is with the 'access to it has been revoked'. It says
nothing about whether or not that is permanent, hence you have to be
very careful about applying this concept to the mount point.

In any case, remounting automatically is a very bad idea unless you do
it cleanly (i.e. kill all existing processes, unmount the disk, and
then start afresh). If you just do it transparently and don't clean
out the (d|i)caches, you will see some pretty odd things happening if
filehandles on the new disk don't match the filehandles on the old
disk.
This is BTW the reason why unfsd is badly broken wrt. CDROMS.

> But soft mounts at least break nicely and automatically. And
> since failures are inevitable, I prefer them.

> Come to think of it, why not have an option that does a
> hard,intr but sends a ^C automatically to all referents when a
> stale handle is detected.

See above.

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/

\
 
 \ /
  Last update: 2005-03-22 13:02    [W:0.061 / U:0.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site