Hi folks,

each time I cancel a backup job, the next job bound for that volume on
which the cancelled job ran Bacula marks the volume in error with a
"file count mismatch". 

I don't recall bad behaviour like this from previous versions (mainly
2.4 and 3.0.x), so is this a bug or a feature? Is it safe to "repair"
the volume by upping the file count in the catalog and setting it to
status "full"? 

All the best, 

Uwe 

-- 
uwe.schuerkamp AT nionex DOT net fon: [+49] 5242.91 - 4740, fax:-69 72
Hauptsitz: Avenwedder Str. 55, D-33311 Gütersloh, Germany
Registergericht Gütersloh HRB 4196, Geschäftsführer: H. Gosewehr, D. Suda
NIONEX ist ein Unternehmen der DirectGroup Germany www.directgroupgermany.de

------------------------------------------------------------------------------

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users