Reference

gnunet-check(1)

a tool to check gnunetd's storage for consistency

NAME

gnunet-check - a tool to check gnunetd's storage for consistency

SYNOPSIS

gnunet-check [OPTIONS]

DESCRIPTION

gnunet-check checks gnunetd's AFS databases for consistency. This includes verifying that the different lookup methods used by GNUnet (index list, database buckets, bloomfilters, etc) are consistent with each other. In some cases the only solution available is to remove the problematic data entry.

gnunet-check can only be run at a time where gnunetd is not running. Otherwise gnunet-check will die with an error on startup. gnunet-check is a tool that should not be needed by most users.

Note that by default each problematic but fixable, nonindexed content block will be restored with priority 0. This means that as the database gets full, the restored content is among the first to flush out. You need to specify a non-zero priority on the command line if you want to avoid this problem.

-h, --help

print help page

-c FILENAME, --config=FILENAME

load config file (default: /etc/gnunet.conf)

-v, --version

print the version number

-u, --update

update AFS databases from one version of GNUnet to another (if possible)

-a --all

check everything

-f --files

check only the file list database (re-inserts all indexed files and checks if the database is consistent with that)

-d --data

check the block database (walks over all blocks in the database and checks if they make sense)

-p PRIORITY, --prio=PRIORITY

priority for the restored, non-indexed content. For indexed content, the config file value GNUNET-INSERT/CONTENT-PRIORITY will be used. NOTE: priority defaults to 0 which will cause the restored content to flush out when the disk gets full.

-n --nofix

check but do not fix problems

-V --verbose

Be verbose.

-q --quiet

Be quiet.

-L LOGLEVEL, --loglevel=LOGLEVEL

change the loglevel. Possible values for LOGLEVEL are NOTHING, FATAL, ERROR, FAILURE, WARNING, MESSAGE, INFO, DEBUG, CRON and EVERYTHING.

NOTES

gnunet-check can run for a long, long time, depending on how much content you are sharing. You should also expect to see some heavy disk activity.

FILES

~/.gnunet/gnunet.conf

Used GNUnet configuration file

~/.gnunet/data/afs/*

AFS database related files.

~/.gnunet/data/afs/database*

Indexing database files.

REPORTING BUGS

Report bugs by using mantis <http://www.ovmj.org/~mantis/> or by sending electronic mail to <[email protected]>

SEE ALSO

gnunet-search(1), gnunet-insert(1), gnunet-gtk(1), gnunet-search(1), gnunet-download(1), gnunet.conf(5), gnunetd(1)