| So, we've had two coda servers just humming along for almost a year now, but one of the servers has hit a snag. Shortly after startup it dies off on an assertion. Looking at the source code, I *think* we hit the limit for the number of files we can have in a directory. Luckily, and for some odd reason, our other coda server was still running without problems. So we turned off the problematic coda server and pruned out the directories. Now the question is, how can we get the problematic coda server started back up? Assuming there isn't some other problem, is there a way to start up the coda server and have it wipe out its existing knowledge of what files are on what volumes and then rebuild that knowledge from the working server, similar to how we set it up in the first place (with an ls -lR or something)? Here is a sample SrvError log: Date: Fri 09/08/2006 18:02:18 Create returns 27 on esoft-snapin-xxxx.rpm 2000004.e898.16c33 Assertion failed: errorCode == 0, file "/home/pwalsh/working/coda/BUILD/coda-6.0.11/coda-src/resolution/subresphase3.cc", line 1162 EXITING! Bye! And here's a clip from SrvLog: Date: Fri 09/08/2006 17:57:43 Coda Vice, version 6.0.11 log started at Fri Sep 8 17:57:43 2006 17:57:43 RvmType is Rvm 17:57:43 Main process doing a LWP_Init() 17:57:43 Main thread just did a RVM_SET_THREAD_DATA 17:57:43 Setting Rvm Truncate threshhold to 5. ... 17:58:52 ValidateVolumes: 0x7f000001 failed! 17:58:52 ValidateVolumes: 0x7f000003 failed! 17:59:05 client_GetVenusId: got new host a.b.c.d:2435 17:59:05 Building callback conn. 17:59:05 ValidateVolumes: 0x7f000003 failed! 17:59:05 ValidateVolumes: 0x7f000003 failed! 17:59:05 ValidateVolumes: 0x7f000003 failed! ... 17:59:05 VGetVnode: vnode 2000004.5f94 is not allocated 17:59:05 VGetVnode: vnode 2000004.5f98 is not allocated 17:59:05 VGetVnode: vnode 2000004.5f9c is not allocated 17:59:05 VGetVnode: vnode 2000004.e898 is not allocated 17:59:05 VGetVnode: vnode 2000004.11cd2 is not allocated 17:59:05 VGetVnode: vnode 2000004.11cd6 is not allocated ... 18:00:31 GetAttrPlusSHA: Computing SHA 2000004.3d74.12b82, disk.inode=4f8b 18:00:31 GetAttrPlusSHA: Computing SHA 2000004.d50.3508, disk.inode=72 18:00:31 GetAttrPlusSHA: Computing SHA 2000004.122d6.12815, disk.inode=523f 18:00:31 GetAttrPlusSHA: Computing SHA 2000004.15ca.570c, disk.inode=5c 18:00:31 GetAttrPlusSHA: Computing SHA 2000004.4ca.286, disk.inode=14a4 18:00:31 GetAttrPlusSHA: Computing SHA 2000004.5b8a.3c03, disk.inode=e0 ... 18:00:46 Total operations for File Server = 4096 : time = Fri Sep 8 18:00:46 2006 18:00:46 Vice was last started at Fri Sep 8 17:57:46 2006 ... 18:02:16 GetAttrPlusSHA: Computing SHA 2000004.15cc.8e93, disk.inode=384d 18:02:16 GetVolObj: Volume (2000004) already write locked 18:02:16 RS_LockAndFetch: Error 11 during GetVolObj for 2000004.138e6.1855f 18:02:16 GetAttrPlusSHA: Computing SHA 2000004.15c0.8e90, disk.inode=3421 18:02:16 GetAttrPlusSHA: Computing SHA 2000004.9656.8dc6, disk.inode=37aa 18:02:16 GetAttrPlusSHA: Computing SHA 2000004.8188.147d6, disk.inode=6360 18:02:16 GetAttrPlusSHA: Computing SHA 2000004.13c7e.144a5, disk.inode=61c6 18:02:16 GetAttrPlusSHA: Computing SHA 2000004.7214.13fc7, disk.inode=641a 18:02:17 GetAttrPlusSHA: Computing SHA 2000004.e7ae.135fc, disk.inode=277 18:02:17 RS_ForceVV: Forcing the old version vector on 2000004.138e6.1855f. 18:02:17 GetAttrPlusSHA: Computing SHA 2000004.f928.11031, disk.inode=3600 18:02:17 GetAttrPlusSHA: Computing SHA 2000004.5990.16b1a, disk.inode=2103 18:02:17 GetAttrPlusSHA: Computing SHA 2000004.e39a.1561a, disk.inode=64ac 18:02:17 ComputeCompOps: fid(0x7f000003.9.25) 18:02:17 GetAttrPlusSHA: Computing SHA 2000004.124a2.14922, disk.inode=5853 18:02:17 GetVolObj: Volume (2000004) already write locked 18:02:17 RS_LockAndFetch: Error 11 during GetVolObj for 2000004.138e2.1855e 18:02:17 VGetVode: Only 1 entry left in lru cache - growing cache 18:02:18 GetAttrPlusSHA: Computing SHA 2000004.81a4.147dd, disk.inode=65fc 18:02:18 Create returns 27 on esoft-snapin-xxxx.rpm 2000004.e898.16c33 Thanks for the help! |
PGP.sig
Description: This is a digitally signed message part
