[Dirvish] dirvish-locate finds nothing (Debian jessie)
keithl at kl-ic.com
Thu Oct 27 19:42:20 UTC 2016
On 2016-10-26 22:13, Matthias Bachert wrote:
> I always get no results from dirvish-locate but the index files (gz) exist.
> What am I doing wrong?
Also, read: http://catb.org/~esr/faqs/smart-questions.html
Asking specific questions is a useful skill. We want
to help, but we don't know enough yet.
1) run the command as root, of course. Ordinary users
should not have access to the index files.
2) In situations like mine, divish-locate is slow.
My main backup drive is 4TB, and as of today has 2492
images in the "/root" vault. As of right now dirvish
is still backing up a remote machine. There are 26
gigabytes of compressed index files in that vault.
As a test, I looked for one file that I added to the
machine "kao3" yesterday.
On my intel 8 core i7 backup server,
time dirvish-locate root:kao3 EarlyFile.odt
... took 30 minutes to run, 9 minutes of user time.
time dirvish-locate root EarlyFile.odt
... took 61 minutes to run, 45 minutes of user time.
( backups completed before dirvish-locate did )
So you can see that dirvish-locate may be slower than
you would like. On the other hand, it is simple and
automatic. Perhaps someday, someone will replace all
the .gz files with a mysql database to make lookups
faster (and backup postprocessing even slower ...).
3) Sometimes other "manual" tools, like "grep", may be
faster to hunt through a limited range of branches.
Matthias, I hope you continue the conversation and
provide more specific information for us, so that this
mailing list thread will lead to a helpful solution.
Otherwise, the question and answers so far will frustrate
many other people using search engines to find answers.
Keith Lofstrom keithl at keithl.com
Don't waste your vote in 2016! Give it to the Republicans
and Democrats, and they will gladly waste it for you!
More information about the Dirvish