On Friday 03 July 2009 21:03:47 Dennis Nezic wrote: > On Fri, 3 Jul 2009 19:25:26 +0100, Matthew Toseland wrote: > > On Friday 03 July 2009 15:35:09 Dennis Nezic wrote: > > > On Fri, 03 Jul 2009 13:53:53 +0100, VolodyA! V Anarhist wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hash: SHA1 > > > > > > > > - From Frost (since nobody seems to be using Freenet from > > > > development team): > > > > > > > > - ----- Anonymous ----- 2009.06.30 - 08:18:42GMT ----- > > > > > > > > I had message "internal error" in download/upload queue > > > > I moved file "node.db4o" to backup directory - and now everything > > > > works. But i lost all my download/upload keys. Anybody knows if > > > > there is any chance to get them back? just keys or filenames... > > > > i tried some tools for db4o database but don't work. is it > > > > encrypted or something? > > > > > > This (node.db4o corruption) should be a known bug. (I mentioned it > > > here on June 12th). It's kind of hard to duplicate -- for me it > > > usually occurs when I have more than an average amount of > > > data/items in my queues and my node.db4o is unusually large (200+ > > > MB vs. a more normal 50MB). > > > > It is caused by either flaky hardware or bugs in db4o itself. Either > > way there is little we can do about it apart from regular automated > > backups. We will implement that eventually. > > I will have to humbly disagree :P. I'm running on top of Software Raid5 > (and LVM), so any disk-io bugs (hardware or otherwise) would have been > handled gracefully. (And my smartd daemon would have picked up on it > too.)
Does RAID5 always check the checksums on any read? Mirroring e.g. certainly does not. > > And I don't think a corruption bug this serious would still be in the > wild in something as big and popular as db4o :P. > > (*cough*.) You'd be surprised. :|
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
