On Tue, Feb 18, 2003 at 11:33:44AM -0600, Tiernan Hubble wrote: > I think the problem is that the index file stores references to keys relative > to the store directory. For instance, here is something from my index file: > > store/7a/1-590d753876734de39fdb18979bfa690a5ebc51480f0203 > > Before, it was relative to "store_<port>/7a/...". When the directory was > renamed, the index file no longer referenced the right directory. Deleting > the index file caused it to rebuilt with the correct directory referenced. Ouch. Hmm. > > And yes, it would probably be a good idea to rebuild the "index" file if it > cannot be loaded properly. Yes, that is why we already do. I overlooked this bit though. The node will now remove the index file if it moves the store. And the dir will fail the index load and therefore rebuild the index file if any file in the index's grandparent in the dir tree fails isDirectory(). Will be committed soon. > > On February 17, 2003 11:41 pm, Yves Lempereur wrote: > > And since the "disappearing" datastore was caused by a corrupt "index" > > file, everything is back to normal. > > > > Maybe a corrupt index file should cause a rescan instead... > > > > Yves > > > > > _______________________________________________ > devl mailing list > [EMAIL PROTECTED] > http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl >
-- Matthew Toseland [EMAIL PROTECTED][EMAIL PROTECTED] Full time freenet hacker. http://freenetproject.org/ Freenet Distribution Node (temporary) at ICTHUS.
msg06911/pgp00000.pgp
Description: PGP signature
