Linux NFS development
 help / color / mirror / Atom feed
From: David Cureton <david.cureton@catapult.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: ADV: Re: The missing link -
Date: Fri, 06 May 2005 16:50:22 +1000	[thread overview]
Message-ID: <427B13AE.1020105@catapult.com> (raw)
In-Reply-To: <1115038201.10853.1.camel@lade.trondhjem.org>

Hi Trond and List,
  =20
      It happened again today. The /server/Staff link went missing.

    "ls -l /server/Staff" explicitly specifying the missing link=20
returned an  "No such file or directory" error. =20
  =20
    "ls -l" in /server  on the effected client shows all but the=20
/server/Staff link.

        Previously I have monitored the NFS traffic where the client=20
does a getattr on the directory /server/Staff.
    Then if proceeds to getattr on the contents of the directory.=20
(Assuming it does not issue a getattr for /server/Staff. It is difficult=20
to map
the raw file handles onto the filenames. How can I do this?)

    Since the client is only doing getattr on the files and directories=20
I am assuming the client thinks that it's cache is OK  and proceeds with=20
it's local
    version of the truth. One that does not include the /server/Staff lin=
k.

    Therefore I tried the following:
       On the NFS server:  'touch test' in the /server diectory=20
therefore causing the client cache of /server to be invalid.
  =20
    On the client ls -la /server...... low and behold  the /server/Staff=20
link is back.

    Therefore it appears to be a client side issue.  It appears that the=20
client forgets about /server/Staff in it's cache?  Anyone else had this=20
issue?

Thanks,
    David





Trond Myklebust wrote:

>m=E5 den 02.05.2005 Klokka 17:49 (+1000) skreiv David Cureton:
>
> =20
>
>>However on occasion we have noticed that the /server/Staff link just
>>disappears for some SuSE9.2 clients and the user no longer has access t=
o
>>there home directory. All other clients still have the link available
>>and they are fine.
>>   =20
>>
>
>What kind of filesystem are you exporting?
>
>When this behaviour happens, what does the client report when you do an
>'ls -l' on /server/Staff?
>
>Cheers,
>  Trond
> =20
>



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, =
4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=3D20
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      parent reply	other threads:[~2005-05-06  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02  7:49 The missing link - David Cureton
2005-05-02 12:50 ` Trond Myklebust
2005-05-02 22:21   ` David Cureton
2005-05-06  6:50   ` David Cureton [this message]

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=427B13AE.1020105@catapult.com \
    --to=david.cureton@catapult.com \
    --cc=nfs@lists.sourceforge.net \
    --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