(Illustration by Gaich Muramatsu)
This was with a ppc client, and a replicated volume on two ppc servers. (coda 6.0.6 release debian packages rebuilt for ppc) I was attempting to copy my maildir into a coda volume. At the same time, I had my laptop untarring the linux kernel into a different volume. 03:01:16 Reintegrate: u.hozer.mail, 100/1007 records, result = SUCCESS 03:01:18 fatal error -- fsobj::dir_Create: (1087644725.M331486P22611V0000000000000900I0011D52C_1.kalmia.hozed.org,S=2832, 6f558048.7f000005.cbf0.339d) Create failed! 03:01:23 RecovTerminate: dirty shutdown (1 uncommitted transactions) Is there something I should look for in the server logs as to why this failed? When I came back and checked the progress of tar jxvf linux-2.6.7, I had a 'Local inconsisten object at ???/testrep/linux-2.6.7/drivers/ide/pci/aec62xx.h, please check' message in the venus log, and when I attempt to do any repair operations, I see messages like the following on the servers: server1 (kalmia) 11:08:36 VGetVnode: vnode 29000003.406a is not allocated 11:08:36 VGetVnode: vnode 29000003.406a is not allocated 11:08:36 RS_LockAndFetch: GetFsObj for 29000003.406a.1dd3 returned error 102 11:08:36 PutVolObj: Couldn't find entry 29000003 on lock queue 11:10:26 GetTime: Destroying callback conn for 209.234.73.38:55935 11:10:26 GetTime: Building callback conn to 209.234.73.38:55935. 11:10:31 RPC2_Bind to 209.234.73.38 port 55935 for callback failed RPC2_NOBINDIN G (F) server2 (narn) 11:07:35 ViceResolve:Couldnt lock volume 7f000003 at all accessible servers 11:07:35 CheckRetCodes: server 209.234.73.41 returned error 102 11:07:35 ViceResolve:Couldnt lock volume 7f000003 at all accessible servers 11:08:36 GetAttrPlusSHA: Computing SHA 27000003.406a.1dd3, disk.inode=0 11:08:36 CheckRetCodes: server 209.234.73.41 returned error 102 11:08:36 ViceResolve:Couldnt lock volume 7f000003 at all accessible serversReceived on 2004-07-16 12:23:22