[Help-gnunet] Database corrupted

[Ludovic Courtès]

Hi,

I'm using GNUnet 0.6.1d (from Debian unstable), with a gdbm database.
Since I upgraded from GNUnet 0.6.1b, my database since to be corrupted
(maybe this has nothing to do with the upgrade, though), ie. `gnunetd'
logs lots of things like:

  WARNING: pIdx database corrupt (could not unlink 5A9EED9B3297D1C
  27EFD6545760F8C025E6EBBCE from low DB (69199, 4940, 26))

Most of the time, gnunetd "disappears" (it does not dump core so maybe
that is "normal" behaviour) a few minutes after it started.  More
precisely, it seems to stop after an initial high disk activity (I guess
gnunetd starts by "browsing" the database or so and then normally stops
doing lots of disk accesses and starts doing "the real job", right?).

Anyway, I thought I might clean the database since running
`gnunet-check -a' did not fix the problem.  However, I noticed that
`gnunet-directory -A', for instance, does nothing, and `gnunet-directory
-a' doesn't show any entry.  Am I missing something?  Is entirely
removing the `data' directory and then re-inserting content a relevant
option?

BTW, unlike stated by the help message, `gnunet-directory' does not
support the `-V' and `--verbose' options.

Sorry for not being more specific...

Thanks,
Ludovic.