Coda File System

Re: venus errors, problems connecting to server / reintegrating changes after disconnect

From: Sebastian Kügler <>
Date: Wed, 28 Apr 2004 15:31:17 +0200

Sorry for bothering you again, but after having my notebook resumed this 
morning, it seems that some problems reintegrating volumes are back, in yet 
another fashion:

sebas_at_neo coda $ cfs cs
Contacting servers .....
All servers up
sebas_at_neo coda $ cfs reconnect
sebas_at_neo coda $ cfs lv /coda/marvin
  Status of volume 0x7f000000 (2130706432) named "codashare"
  Volume type is ReadWrite
  Connection State is WriteDisconnected
  Minimum quota is 0, maximum quota is unlimited
  Current blocks used are 75083
  The partition has 2423784 blocks available out of 14356564
  Write-back is disabled
  There are 1 CML entries pending for reintegration

This seems odd, as if I connect and are authenticated, it should automatically 
read/write connect and reintegrate my changes, shouldn't it? I did issue a 
hoard walk before suspending, but no cfs disconnect. The server is up, two 
other clients (which I reinit'ed also yesterday are still connected.) Here's 
some output, which may clarify the problems some more:

sebas_at_neo bash $ cfs fr /coda/marvin
VIOC_SYNCCACHE: Invalid argument
  VIOC_SYNCCACHE returns -1
cfs wbauto /coda/marvin is going to hang, if I control+C it, the following is 
issued to dmesg:
coda_pioctl: Venus returns: -4 for (0x7f000000.0x1.0x1)
AuthLog on the server seems clear:
14:16:02        vid = 500
14:16:02 AuthNewConn(0x1f5, 0, 66, 2, 500)
codacon on the client after a reconnect:
ValidateVols codashare [1] ( 14:56:12 )
GetRootVolume @marvin ( 14:56:12 )
GetVolumeInfo codashare_at_marvin ( 14:56:12 )
NewConnectFS ( 14:56:12 )
BackProbe ( 14:56:12 )
bandwidth 124223 186011 370096 ( 14:56:12 )
GetVolStat codashare ( 14:56:12 )
bandwidth 128865 181752 308261 ( 14:56:17 )
GetVolStat codashare ( 14:57:49 )
bandwidth 129668 176242 275027 ( 14:57:54 )
dmesg on the client (right after restarting venus):
Coda: Bye bye.
coda_read_super: device index: 0
coda_read_super: rootfid is (0xff000001.0x1.0x1)
coda_read_super: rootinode is 1375275913 dev 0
coda_pioctl: Venus returns: -22 for (0x7f000000.0x1.0x1)

Is there a list with all errorcodes? How can I get this client back into 
'normal' mode, what can I do to prevent these problems? What could be the 

Btw: The 'problematic' client is a notebook, I use it with swsusp and had ik 
hibernated in the meantime. It's connected via a WLAN connection and on the 
same subnet as the server, also the server is mentioned in all hosts files. 
The kernel module on the client (neo) is: Coda Kernel/Venus communications, 
v5.3.18,, according to dmesg. (2.4.26). Some config and 
logfiles are here:

Hope this makes sense to you ... 
It is now proved beyond doubt that smoking is one of the leading causes of 
statistics. - Knebel's Law
Received on 2004-04-28 09:33:58