(Illustration by Gaich Muramatsu)
i upgraded both my backup server and my coda server to 6.0.1. after doing this, the backup failed, crashing my coda server in the process: SrvLog 00:17:13 VAttachVolumeById: vol 1000016 (sg.media.site.0.backup) attached and online 00:17:13 S_VolMakeBackups: backup (1000016) made of volume 1000006 00:17:13 GrowVnodes: growing Small list from 47104 to 47616 for volume 0x1000017 (and then it dies) SrvErr socket 5: Invalid argument socket 5: Invalid argument socket 5: Invalid argument socket 5: Invalid argument socket 5: Invalid argument Assertion failed: SRV_RVM(VolumeList[rwIndex]).data.nsmallLists == SRV_RVM(VolumeList[backupIndex]).data.nsmallLists, file "/usr/src/redhat/BUILD/coda-6.0.1/coda-src/volutil/vol-backup.cc", line 426 EXITING! Bye! dumplog: 00:17:12 Partition /backup1: 16743200K available (minfree=5%), 13735896K free. 00:17:12 VLDBLookup: VLDB_size unset. Calling VCheckVLDB() 00:17:12 7f000005: cloning 00:17:13 01000006->01000016 00:17:13 7f000004: cloning 00:17:43 VolBackup (265c) failed on replica 1000005 with RPC2_DEAD (F) 00:17:43 7f000003: cloning 00:17:43 7f000002: cloning 00:17:43 7f000001: cloning 00:17:43 7f000000: cloning 00:17:43 Dump of volume 7f000005 failed! 00:17:43 MarkAncient of 7f000005 failed! (etc) however, i was able to get the backups going again simply by purging the backup volumes. ie. volutil purge 1000016 myvolume.0.backup for each volume. while i was happy to workaround the problem, i thought i would report it as a potential bug. -- steve simitzis : /sim' - i - jees/ pala : saturn5 productions www.steve.org : 415.282.9979 hath the daemon spawn no fire?Received on 2003-06-04 03:39:24