>> I've been having a lot of problems with Bacula's disk volume management >> over time. Most issues seem to stem from cases where the catalog gets >> out of sync with the file system, like: >> >> - Volume inserted into catalog, creation of file on disk fails, volume >> remains in catalog >> >> - Write to volume fails, resulting in volume that's shorter on disk than >> the catalog thinks it should be because the catalog is updated with >> the *expected* size assuming the write is successful. Further backups >> try to use this volume and fail. Restores from this volume fail. ARgh! > > If the disk/array was full the bacula volume should have been marked > full when no space is left on the device. After the volume is marked > full then it should not have been used for additional backups. > >> >> The latest issue is another catalog<>disk discrepency. At some point >> Bacula seems to have failed to create some auto-labeled volumes, but has >> still inserted them into the catalog. This might've been due to a >> transient disk-full situation, but it's truly hard to know. >> > > You need to prevent the disk from filling up completely. >
Also is your database on the same filesystem as your disk volumes? This could cause serious problems in a disk full situation. John ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
