Ryan Novosielski wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dan Langille wrote:
>> Jason Dixon wrote:
>>> I was updating the Director configuration and reloaded while a job was
>>> running.  Unfortunately, there was a minor typo and it caused the
>>> Director to bail.
>>>
>>> After fixing the typo and restarting bacula-dir, it complained of a
>>> volume size mismatch:
>>>
>>>
>>> 15-Aug 12:02 vlad-sd JobId 925: Error: Bacula cannot write on disk
>>> Volume "Vol0013" because: The sizes do not match! Volume=11206992819
>>> Catalog=10207056909
>>> 15-Aug 12:02 vlad-sd JobId 925: Marking Volume "Vol0013" in Error in
>>> Catalog.
>> Run Update Volume.  Adjust the Catalog setting to match the actual 
>> number of files on the disk.  In almost all cases I've seen, the Volume 
>> count is correct.  The Catalog count is wrong.
> 
> Not to stick my nose in here -- is this also true for disk full
> conditions? In that case, you'll get a catalog value that is larger than
> the on disk value. I never knew if there was a safe way to fix that.

FWIW, my original advice was based on my incorrect conclusion that this 
was a file count problem.  It was not.  It was a volume size problem.

As for your original question, I don't know.  Easily tested though.


-- 
Dan Langille

BSDCan - The Technical BSD Conference : http://www.bsdcan.org/
PGCon  - The PostgreSQL Conference:     http://www.pgcon.org/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users