(Illustration by Gaich Muramatsu)
Hello, I've been running coda on FC1 for some time without problems, but now I'm putting up another intranet and thought I should try to run it on FC2 (kernel 2.6.5). Well, I've tried RH9 rpm's, building from source rpm's and cvs, but I can't get any further than the below logs show. Can someone offer some advice on what might be the problem? The error comes when creating initial volume: []# createvol_rep croot E0000100 /vicepa Getting initial version of /vice/vol/BigVolumeList. V_BindToServer: binding to host scigreg.siljansnas.net GetVolumeList finished successfully V_BindToServer: binding to host scigreg.siljansnas.net Servers are (scigreg ) HexGroupId is 7f000000 creating volume croot.0 on scigreg (partition /vicepa) V_BindToServer: binding to host scigreg.siljansnas.net VolCreate failed with RPC2_DEAD (F) Failure to make volume on scigreg!. Abort.. [1]+ Done startserver === SrvErr === Assertion failed: 0, file "srv.cc", line 316 EXITING! Bye! === SrvLog === Date: Tue 06/08/2004 18:46:09 Coda Vice, version 6.0.6 log started at Tue Jun 8 18:46:09 2004 18:46:09 Resource limit on data size are set to -1 18:46:09 RvmType is Rvm 18:46:09 Main process doing a LWP_Init() 18:46:09 Main thread just did a RVM_SET_THREAD_DATA 18:46:09 Setting Rvm Truncate threshhold to 5. Partition /vicepa: inodes in use: 0, total: 2097152. 18:46:53 Partition /vicepa: 7714940K available (minfree=5%), 7714920K free. 18:46:53 The server (pid 4490) can be controlled using volutil commands 18:46:53 "volutil -help" will give you a list of these commands 18:46:53 If desperate, "kill -SIGWINCH 4490" will increase debugging level 18:46:53 "kill -SIGUSR2 4490" will set debugging level to zero 18:46:53 "kill -9 4490" will kill a runaway server 18:46:53 VCheckVLDB: bad VLDB! 18:46:53 VInitVolPackage: no VLDB! Please create a new one. 18:46:53 Vice file system salvager, version 3.0. 18:46:53 SanityCheckFreeLists: Checking RVM Vnode Free lists. 18:46:53 DestroyBadVolumes: Checking for destroyed volumes. 18:46:53 Salvaging file system partition /vicepa 18:46:53 Force salvage of all volumes on this partition 18:46:53 Scanning inodes in directory /vicepa... 18:46:53 SalvageFileSys completed on /vicepa 18:46:53 Attached 0 volumes; 0 volumes not attached lqman: Creating LockQueue Manager.....LockQueue Manager starting ..... 18:46:53 LockQueue Manager just did a rvmlib_set_thread_data() done 18:46:53 CallBackCheckLWP just did a rvmlib_set_thread_data() 18:46:53 CheckLWP just did a rvmlib_set_thread_data() 18:46:53 ServerLWP 0 just did a rvmlib_set_thread_data() 18:46:53 ServerLWP 1 just did a rvmlib_set_thread_data() 18:46:53 ServerLWP 2 just did a rvmlib_set_thread_data() 18:46:53 ServerLWP 3 just did a rvmlib_set_thread_data() 18:46:53 ServerLWP 4 just did a rvmlib_set_thread_data() 18:46:53 ServerLWP 5 just did a rvmlib_set_thread_data() 18:46:53 ResLWP-0 just did a rvmlib_set_thread_data() 18:46:53 ResLWP-1 just did a rvmlib_set_thread_data() 18:46:53 VolUtilLWP 0 just did a rvmlib_set_thread_data() 18:46:53 VolUtilLWP 1 just did a rvmlib_set_thread_data() 18:46:53 Starting SmonDaemon timer 18:46:53 File Server started Tue Jun 8 18:46:53 2004 18:47:30 ****** FILE SERVER INTERRUPTED BY SIGNAL 11 ****** 18:47:30 ****** Aborting outstanding transactions, stand by... 18:47:30 Uncommitted transactions: 1 18:47:30 Uncommitted transactions: 1 18:47:30 Committing suicide now ........ Why is server killed when creating volumes? Please help. Best regards, ChristerReceived on 2004-06-08 14:47:34