This is a good example of a Coda feature: Coda has cached your directory
file so "ls" can list the files in it. 

However, ls -l needs the attributes of the file, which might still be on
the server.  In this case your connection to the server is down or too
slow and you are timing out. 

Your other example also happens because of this: you have cached your
stuff, not that of others.

To shut down: vutil -shutdown, umount /coda, rmmod coda (if you wish). If
you can't restart Venus easily let me know then I'll try to fix that. 

If you do venus -init you whack out your persistent cache.  In that case
Coda can only come up if you can mount the root volume on /coda.

Peter 


On Mon, 14 Jul 1997 thoth_at_purplefrog.com wrote:

> 
>   So, I decide to exercise coda again.
> 
> ls -lRa gives me a listing of all my stuff, but nobody else's:
> 
> ls: playground/catfish: Connection timed out
> ls: playground/peter-braam: Connection timed out
> ls: playground/sand_pants: Connection timed out
> ls: playground/sopwith: Connection timed out
> 
> 
>   find . -ls gives me a list of the top-level directory but doesn't
> recurse ?!
> 
>  frop:30 $ find . -ls
>      0    2 drwxrwxrwx   2 root     65534        2048 Apr 10 18:09 .
> 7409699    1 -rw-r--r--   1 65435    65534         506 Apr 10 18:09 ./README
> 7342082    2 drwxrwxrwx   7 root     65534        2048 Jul 14 12:56 ./playground
> 7344131    2 drwxrwxrwx   2 root     65534        2048 Apr 10 18:10 ./pub
> 
> 
>   And these strange warnings show up in the log after the ls -lRa:
> 
> [ W(18) : 0000 : 14:51:12 ] ADMON STATS:  DMQ Advice NOT valid. (uid = 100)
> [ W(18) : 0000 : 14:51:12 ] ADMON STATS:  DMQ Advice NOT valid. (uid = 100)
> [ W(18) : 0000 : 14:51:12 ] ADMON STATS:  DMQ Advice NOT valid. (uid = 100)
> [ W(18) : 0000 : 14:51:12 ] ADMON STATS:  DMQ Advice NOT valid. (uid = 100)
> [ W(18) : 0000 : 14:51:12 ] ADMON STATS:  DMQ Advice NOT valid. (uid = 100)
> [ W(18) : 0000 : 14:51:12 ] ADMON STATS:  DMQ Advice NOT valid.. (uid = 100)
> 
>   A later ls -lR comes up with:
> 
> ls: playground/thoth/netpipes4.0: Connection timed out
> 
>   in addition to the others.  Even a normal ls doesn't work on these
> other directories.
> 
>  frop:44 $ ls -l /coda/playground/catfish/
> ls: /coda/playground/catfish/: Connection timed out
> 
> 
>   And, can anyone tell me how to shut down venus so that the machine will
> not get all wacky, and so I can restart it later (and would I provide the
> -init to venus when restarting?  would I provide -init after a reboot?)
> This all belongs in the readme.  Heck, it's probably all in the enormous
> .ps file, but I'm feeling lazy.
> 
>   What's the procedure for shutting down as soon as the cache is flushed
> and the writes are committed to the server?
> 
>   Anyway, if you developer guys are feeling masochistic, I'd suggest you
> install a serial link (115.2Kbit) between two of your servers and set up
> a PPP channel through it.  This way two of your servers will be
> abominably connected and you'll get to see lots of wacky problems :)
> 
> -- 
> Bob Forsman                                   thoth_at_gainesville.fl.us
>            http://www.gainesville.fl.us/~thoth/
>