> " " == Patrick J LoPresti <[EMAIL PROTECTED]> writes:
> Trond Myklebust <[EMAIL PROTECTED]> writes:
>> OK. We need the patch I sent last night plus a 1-liner in
>> nfs_inode_is_stale(). That should cover both pathologies. It'll
>> probably clean up the other cases in which
> " " == David Fries <[EMAIL PROTECTED]> writes:
> If I didn't make it clear /home/david directory is the stale
> NFS filehandle and server:/home is mounted on /home so it isn't
> the root directory inode here that is having the problem.
Ah. Sorry... Neil's argumentation made
> " " == Neil Brown <[EMAIL PROTECTED]> writes:
> In short, I really don't think that NFS_INO_STALE (or any other
> item if information received from the server) should be
> considered to be permanent and never rechecked.
There are 2 problems of inode corruption if you allow i
On February 28, [EMAIL PROTECTED] wrote:
> > " " == Neil Brown <[EMAIL PROTECTED]> writes:
>
> > So... you can access things under /home/david, but you cannot
> > access /home/david itself? So, supposing that "fred" were some
> > file that you happen to know is in /home/david
> " " == Neil Brown <[EMAIL PROTECTED]> writes:
> So... you can access things under /home/david, but you cannot
> access /home/david itself? So, supposing that "fred" were some
> file that you happen to know is in /home/david, then
> ls /home/david fails with ESTALE
On Sunday February 25, [EMAIL PROTECTED] wrote:
> On Sun, Feb 25, 2001 at 08:25:10PM +1100, Neil Brown wrote:
> > On Saturday February 24, [EMAIL PROTECTED] wrote:
> > Verrry odd. I can see why you were suspecting a cache.
> > I'm probably going to have to palm this off to Trond, the NFS client
>
On Mon, Feb 26, 2001 at 10:54:02AM +0100, Lennert Buytenhek wrote:
> A trick that works for me is mounting the NFS filesystem on another mount
> point and unmounting it there. This usually makes the mount on the
> original mount point magically work again.
Thinks, but I've tried it and it didn't
On 25 Feb 2001, Trond Myklebust wrote:
> > I was hopping to avoid unmounting, as I would have to shut
> > about everything down to do that.
>
> It looks as if you'll have to do that. 'mount -oremount' does not
> really cause the root filehandle to get updated. The only thing it
> does
On Sun, Feb 25, 2001 at 08:25:10PM +1100, Neil Brown wrote:
> On Saturday February 24, [EMAIL PROTECTED] wrote:
> Verrry odd. I can see why you were suspecting a cache.
> I'm probably going to have to palm this off to Trond, the NFS client
> maintainer (are you listening Trond?) but could please
> " " == David Fries <[EMAIL PROTECTED]> writes:
> I'ved tried `mount /home -o remount`, and reading lots of other
> directories to flush out that entry if it was in cache without
> any results.
> I was hopping to avoid unmounting, as I would have to shut
> about eve
On Saturday February 24, [EMAIL PROTECTED] wrote:
[problem summary: After restarting knfsd server on 2.4.2, client
reports Stale NFS file handle]
> On Sun, Feb 25, 2001 at 04:43:46PM +1100, Neil Brown wrote:
> > So check that /etc/exports contains the right info.
> > Check that
On Sun, Feb 25, 2001 at 04:43:46PM +1100, Neil Brown wrote:
> On Saturday February 24, [EMAIL PROTECTED] wrote:
> > I have my home directory mounted on one computer from another. I
> > rebooted the server and now the client is saying Stale NFS file handle
> > anytime something goes to read my hom
On Saturday February 24, [EMAIL PROTECTED] wrote:
> I have my home directory mounted on one computer from another. I
> rebooted the server and now the client is saying Stale NFS file handle
> anytime something goes to read my home directory. It has been this
> way for about a day. Shouldn't a
I have my home directory mounted on one computer from another. I
rebooted the server and now the client is saying Stale NFS file handle
anytime something goes to read my home directory. It has been this
way for about a day. Shouldn't any caches expire by now?
Both server and client are runni
14 matches
Mail list logo
