Homepage > Man Pages > Category > General Commands
Homepage > Man Pages > Name > D

dbd

man page of dbd

dbd: CNID database maintanance

NAME
dbd - CNID database maintanance
SYNOPSIS
dbd [-evx] {-d [-i] | -s [-c|-n] | -r [-c|-f] | -u} volumepath

DESCRIPTION

dbd can dump, scan, reindex and rebuild Netatalk dbd CNID databases. It must be run with appropiate permissions i.e. as root.

COMMANDS

-d Dump CNID database. With -i dump indexes too. -s Scan volume: o Compare CNIDs in database with volume o Test if .AppleDouble directories exist o Test if AppleDouble files exist o Report orphaned AppleDouble files o Report directories inside .AppleDouble directories o Check name encoding by roundtripping, log on error o Check for orphaned CNIDs in database (requires -e) o Open and close adouble files Options: -c Don't check .AppleDouble stuff, only check orphaned. -n Don't open CNID database, skip CNID checks, only traverse filesystem -r Rebuild volume. With -f wipe database and rebuild from CNIIDs stored in AppleDouble files. o Sync CNIDSs from database with volume o Ensure .AppleDouble directories exist o Ensure AppleDouble files exist o Delete orphaned AppleDouble files o Report directories inside .AppleDouble directories o Check name encoding by roundtripping, log on error o Delete orphaned CNIDs in database (requires -e) o Open and close adouble files Options: -c Don't create .AppleDouble stuff, only cleanup orphaned. -f Wipe database and rebuild from IDs stored in AppleDouble files, only available for volumes without nocnidcache option. Implies -e. -u Prepare upgrade: Before installing an upgraded version of Netatalk that is linked against a newer BerkeleyDB lib, run 'dbd -u ...' from the OLD Netatalk pior to upgrading on all volumes. This removes the BerkleyDB environment. On exit cnid_dbd does this automatically, so normally calling dbd -u should not be necessary !

OPTIONS

-e Only work on inactive volumes and lock them (exclusive) -x Rebuild indexes (just for completeness, mostly useless!) -v verbose

WARNING

In order to be able to run -rf reconstructing the CNIDs in the database from the AppleDouble files, make sure you've run a -r rebuild sometimes before, where the CNIDs then would have been synched between database and AppleDouble files. Also be careful about the option nocnidcache. Avoid this option if at all possible, because if prevents you from being able to use -f.
CNID BACKGROUND
The CNID backends maintains name to ID mappings. If you change a filename outside afpd(8) (shell, samba), the CNID db will not know and not reflect that change. Netatalk tries to recover from such inconsistencies as gracefully as possible. The mechanisms to resolve such inconsistencies may fail sometimes, though, as this is not an easy task to accomplish. E.g. if several names in the path to the file or directory have changed, things may go wrong. If you change a lot of filenames at once, chances are higher that the afpds fallback mechanisms fail, i.e. files will be assigned new IDs, even though the file hasn't changed.
SEE ALSO
cnid_metad(8), DBD(1)
 
 
 

Copyright © 2011–2018 by topics-of-interest.com . All rights reserved. Hosted by all-inkl.
Contact · Imprint · Privacy

Page generated in 13.75ms.

N├╝tzliche Versicherungen | Ist die Versicherung XYZ notwendig? | brieftaubenversteigerung.com