Re: [Bacula-users] 800, 000+ orphaned paths entries cannot be pruned when using bvfs

2019-01-26 Thread Kern Sibbald
Hello Radek, The code has been there since 2011.  I now have a patch that makes the error message very clear. Yes, I am aware how bvfs works and why the cache is there.  I was just surprised that the existence of the cache would disable a dbcheck

Re: [Bacula-users] 800, 000+ orphaned paths entries cannot be pruned when using bvfs

2019-01-25 Thread Radosław Korzeniewski
Hello Kern, pt., 25 sty 2019 o 17:06 Kern Sibbald napisał(a): > Hello, > > I find the error message very cryptic, and I really don't like just giving > up, so I have asked the author > of that particular code to supply a fix. > >From what I understand here bvfs is using a special cache tables

Re: [Bacula-users] 800, 000+ orphaned paths entries cannot be pruned when using bvfs

2019-01-25 Thread Kern Sibbald
Hello, I find the error message very cryptic, and I really don't like just giving up, so I have asked the author of that particular code to supply a fix. Best regards, Kern On 1/23/19 11:03 AM, Radosław Korzeniewski wrote:

Re: [Bacula-users] 800, 000+ orphaned paths entries cannot be pruned when using bvfs

2019-01-23 Thread Stefan Muenkner
Am 23.01.19 um 11:03 schrieb Radosław Korzeniewski: > Hello, Hi, > wt., 22 sty 2019 o 14:39 Stefan Muenkner > napisał(a): > > (...) > Searching for hascache in the rest of the source I found that hascache in > the job table seems to be only

Re: [Bacula-users] 800, 000+ orphaned paths entries cannot be pruned when using bvfs

2019-01-23 Thread Radosław Korzeniewski
Hello, wt., 22 sty 2019 o 14:39 Stefan Muenkner napisał(a): > (...) > Searching for hascache in the rest of the source I found that hascache in > the job table seems to be only reset in ".bvfs_clear_cache". > Great! > >> > >> 9) Check for orphaned Path records > >> > >>

Re: [Bacula-users] 800, 000+ orphaned paths entries cannot be pruned when using bvfs

2019-01-22 Thread Stefan Muenkner
Hello Kern, thanks for the answer. I'll do. But for the time being I found a workaround. Digging in the source, I found, that dbcheck only tests whether any entry in the job table has "hascache" <>0. Even if there is just one entry, dbcheck declines to celar up the orphaned path entries.

Re: [Bacula-users] 800, 000+ orphaned paths entries cannot be pruned when using bvfs

2019-01-20 Thread Kern Sibbald
Hello Stefan, Please submit a bug report on this.  When running dbcheck, it is my opinion that we should not be relying on .bvfs.  If this is true (as it seems from your output) then I must see why and make sure it is justified.  dbcheck should always be able to prune. Best regards, Kern On

[Bacula-users] 800, 000+ orphaned paths entries cannot be pruned when using bvfs

2019-01-17 Thread Stefan Muenkner
Hi, I have an almost 9 years running Bacula installation that accumulated more than 800,000 orphaned paths entries in the database (around 5% of all entries in the path table). dbcheck claims it cannot prune those when BVFS is used. 9) Check for orphaned Path records Select