Menu
▾
▴
[Bacula-bugs] [bacula 0001395]: After upgrade Bacula cannot write on disk Volume
|
From: Mantis B. T. <no...@bu...> - 2009-10-29 17:06:27
|
The following issue has been CLOSED ====================================================================== http://bugs.bacula.org/view.php?id=1395 ====================================================================== Reported By: gani Assigned To: kern ====================================================================== Project: bacula Issue ID: 1395 Category: Storage Daemon Reproducibility: always Severity: minor Priority: normal Status: closed Resolution: won't fix Fixed in Version: ====================================================================== Date Submitted: 2009-10-25 00:43 UTC Last Modified: 2009-10-29 17:06 UTC ====================================================================== Summary: After upgrade Bacula cannot write on disk Volume Description: After upgrade Bacula from version 1.38.11 to 3.0.1 and run Jobs I received a message: 31-maj 12:14 thinstar-dir JobId 12: Start Backup JobId 12, Job=Logowa_Praca.2009-05-31_12.13.40_04 31-maj 12:14 thinstar-dir JobId 12: Using Device "FileStorage" 31-maj 12:14 thinstar-sd JobId 12: Volume "wokandor" previously written, moving to end of data. 31-maj 12:14 thinstar-sd JobId 12: Error: Bacula cannot write on disk Volume "wokandor" because: The sizes do not match! Volume=13265860 Catalog=13265657 31-maj 12:14 thinstar-sd JobId 12: Marking Volume "wokandor" in Error in Catalog. 31-maj 12:14 thinstar-sd JobId 12: Job Logowa_Praca.2009-05-31_12.13.40_04 waiting. Cannot find any appendable volumes. Please use the "label" command to create a new Volume for: Storage: "FileStorage" (/var/UrzadzeniePlikowe) Pool: Kruszon Wielki Media type: File I canceled the backup and started another backup. I had the same situation and the same message: *messages 31-maj 12:18 thinstar-dir JobId 13: Start Backup JobId 13, Job=Dokumentacje.2009-05-31_12.18.33_07 31-maj 12:18 thinstar-dir JobId 13: Using Device "FileStorage" 31-maj 12:18 thinstar-sd JobId 13: Volume "popierkan" previously written, moving to end of data. 31-maj 12:18 thinstar-sd JobId 13: Error: Bacula cannot write on disk Volume "popierkan" because: The sizes do not match! Volume=552685397 Catalog=552685199 31-maj 12:18 thinstar-sd JobId 13: Marking Volume "popierkan" in Error in Catalog. 31-maj 12:18 thinstar-sd JobId 13: Job Dokumentacje.2009-05-31_12.18.33_07 waiting. Cannot find any appendable volumes. Please use the "label" command to create a new Volume for: Storage: "FileStorage" (/var/UrzadzeniePlikowe) Pool: Karocany Media type: File I configured all from the beginning but I had the same situation as above. ====================================================================== ---------------------------------------------------------------------- (0004727) Dan Langille (manager) - 2009-10-25 01:14 http://bugs.bacula.org/view.php?id=1395#c4727 ---------------------------------------------------------------------- The solution for getting backups running is the update volume command. Set the Catalog size to match the Volume size. ---------------------------------------------------------------------- (0004728) gani (reporter) - 2009-10-25 08:47 http://bugs.bacula.org/view.php?id=1395#c4728 ---------------------------------------------------------------------- I know that it is a solution but I cannot do it. This means that upgrade described above is impossible without a hand intervention. Is there any chance for fix it? ---------------------------------------------------------------------- (0004729) kern (administrator) - 2009-10-25 09:25 http://bugs.bacula.org/view.php?id=1395#c4729 ---------------------------------------------------------------------- Your analysis of the problem sounds correct to me. Since we no longer support version 1.38.11, and we won't fix bugs/problems with multiple DB updates, it seems to me you have three choices: 1. Manually update the volume sizes to correspond to their real size. I don't particularly like this option, and would only do it if I were 100% sure that restores work. However, in principle, it should work. 2. Mark all the old Volumes as Used or Full, and create new Volumes and use them, once the old Volumes expire and are recycled, they should work. This is my preferred option. However, I would also carefully check if I could restore from the old Volumes -- particularly the last backup on each Volume. 3. Go back to the Bacula version that started keeping the correct sizes and do at least one backup on each Volume before upgrading to the next catalog version. This will probably simulate what most of us have done -- i.e. upgrade one version at a time. I don't like this option too much because it requires building and running on each (or one or more) intermediate database version. ---------------------------------------------------------------------- (0004738) kern (administrator) - 2009-10-29 17:06 http://bugs.bacula.org/view.php?id=1395#c4738 ---------------------------------------------------------------------- Several solutions for the problem have been given. Issue History Date Modified Username Field Change ====================================================================== 2009-10-25 00:43 gani New Issue 2009-10-25 01:14 Dan Langille Note Added: 0004727 2009-10-25 08:47 gani Note Added: 0004728 2009-10-25 09:25 kern Note Added: 0004729 2009-10-25 09:25 kern Status new => feedback 2009-10-25 10:03 kern Status feedback => resolved 2009-10-25 10:03 kern Resolution open => won't fix 2009-10-25 10:03 kern Assigned To => kern 2009-10-29 17:06 kern Note Added: 0004738 2009-10-29 17:06 kern Status resolved => closed ====================================================================== |