From: Mike Jagdis <mjagdis@eris-associates.co.uk>
To: Tim Connors <tconnors+linuxkernel1094371411@astro.swin.edu.au>
Cc: "Trond Myklebust" <trond.myklebust@fys.uio.no>,
"Sven Köhler" <skoehler@upb.de>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: why do i get "Stale NFS file handle" for hours?
Date: Sun, 05 Sep 2004 17:20:13 +0100 [thread overview]
Message-ID: <413B3CBD.1000304@eris-associates.co.uk> (raw)
In-Reply-To: <slrn-0.9.7.4-19971-22570-200409051803-tc@hexane.ssi.swin.edu.au>
Tim Connors wrote:
> I will update one directory with rsync from one host,
You mean rsync to the server and change files directly on the fs rather
than through an NFS client?
> and then try, a
> little later on, to operate on that directory from another host. Every
> now and then, from a single host only, a few files in that tree will
> get stale filehandles - an ls of that directory will mostly be fine
> apart from those files. They will also be fine from any other machine.
Yeah, that's what happens... Clients that had the file open are liable
to get ESTALE. Stale file handles stick around until unmount. As long as
they're around automount will consider the mount busy and not expire it
(but you can unmount manually or killall -USR1 automountd).
Mike
--
Mike Jagdis Web: http://www.eris-associates.co.uk
Eris Associates Limited Tel: +44 7780 608 368
Reading, England Fax: +44 118 926 6974
next prev parent reply other threads:[~2004-09-05 16:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 1:06 Sven Köhler
2004-09-05 1:39 ` Trond Myklebust
2004-09-05 1:51 ` Sven Köhler
2004-09-05 2:02 ` Trond Myklebust
2004-09-05 2:23 ` Sven Köhler
2004-09-05 3:01 ` Trond Myklebust
2004-09-05 8:17 ` Tim Connors
2004-09-05 8:59 ` Florian Weimer
2004-09-05 9:02 ` Tim Connors
2004-09-05 16:20 ` Mike Jagdis [this message]
2004-09-06 1:32 ` Tim Connors
2004-09-05 13:18 ` Sven Köhler
2004-09-05 20:10 ` Trond Myklebust
2004-09-06 7:47 ` Kalin KOZHUHAROV
2004-09-06 9:57 ` David Woodhouse
2004-09-06 15:59 ` Trond Myklebust
2004-09-07 0:55 ` [NFS] " Greg Banks
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=413B3CBD.1000304@eris-associates.co.uk \
--to=mjagdis@eris-associates.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=skoehler@upb.de \
--cc=tconnors+linuxkernel1094371411@astro.swin.edu.au \
--cc=trond.myklebust@fys.uio.no \
/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
all inboxes | Powered by JetHome®