I have several Linux coda clients on a fast Ethernet and one client on
a slow wireless Ethernet (about 1.5 Mbps actual bandwidth available).

There's a process on the slow client creating log files (in a Coda
volume served by a third machine on the fast network) that are to be
analyzed by a process on the fast client.

Everybody's clocks are synced by xntp. 

I ran my codes and found that the log files were never appearing on
the fast client (or, more precisely, appeared but were empty), even
though the slow client issued a 'cfs strong'. 

Even now, more than half an hour later, the files somehow have not
been propagated to the other clients, despite my typing various things
including 'cfs wr' on all clients.

$ date
Fri Aug 13 14:28:14 CDT 1999

On the slow client: 

$ cfs listvol .
  Status of volume 0x7f000003 (2130706435) named "glare-grib"
  Volume type is ReadWrite
  Connection State is Connected
  Minimum quota is 0, maximum quota is unlimited
  Current blocks used are 578136
  The partition has 3584743 blocks available out of 4385244

$ ls -l 
-rw-rw-r--   1 grib     nogroup      9531 Aug 13 13:51 tmcontroller-actual.log
-rw-rw-r--   1 grib     nogroup      5431 Aug 13 13:51 tmcontroller-motor.log
-rw-rw-r--   1 grib     nogroup      9720 Aug 13 13:51 tmcontroller-target.log


On the fast client: 

$ cfs listvol .
  Status of volume 0x7f000003 (2130706435) named "glare-grib"
  Volume type is ReadWrite
  Connection State is Connected
  Minimum quota is 0, maximum quota is unlimited
  Current blocks used are 578136
  The partition has 3584743 blocks available out of 4385244

$ ls -l
-rw-rw-r--   1 grib     nogroup         0 Aug 13 13:50 tmcontroller-actual.log
-rw-rw-r--   1 grib     nogroup         0 Aug 13 13:50 tmcontroller-motor.log
-rw-rw-r--   1 grib     nogroup         0 Aug 13 13:50 tmcontroller-target.log

This is coda client and server v.5.2.7, Linux kernel 2.2.10, 
and kernel module version 5.2.3 (glibc-2.1). 

Thanks for any advice,
Bill Gribble