From: Ralf G. <Ral...@ra...> - 2009-09-30 10:47:51
|
Hi, I've recently upgraded from 2.4.4 to 3.0.2. Since then I regularly get warnings about newly created volumes where the DB record exists but the disk volume was not created/labled yet. 30-Sep 12:06 VUMEM004-sd JobId 15915: User defined maximum volume capacity 5,000,000,000 exceeded on device "Toolserver-DISK" (/data/bacula-storage/toolserver). 30-Sep 12:06 VUMEM004-sd JobId 15915: End of medium on Volume "toolserver-inc-0150" Bytes=4,999,982,504 Blocks=77,510 at 30-Sep-2009 12:06. ok, volume toolserver-inc-0150 is full and a new volume will be created... 30-Sep 12:06 VUMEM004-dir JobId 15915: Created new Volume "toolserver-inc-0603" in catalog. 30-Sep 12:06 VUMEM004-sd JobId 15915: Warning: dev.c:534 dev.c:532 Could not open: /data/bacula-storage/toolserver/toolserver-inc-0603, ERR=Datei oder Verzeichnis nicht gefunden 30-Sep 12:06 VUMEM004-sd JobId 15915: Warning: dev.c:534 dev.c:532 Could not open: /data/bacula-storage/toolserver/toolserver-inc-0603, ERR=Datei oder Verzeichnis nicht gefunden "Datei oder Verzeichnis nicht gefunden" means file or directory not found. 30-Sep 12:06 VUMEM004-sd JobId 15915: Labeled new Volume "toolserver-inc-0603" on device "Toolserver-DISK" (/data/bacula-storage/toolserver). 30-Sep 12:06 VUMEM004-sd JobId 15915: Wrote label to prelabeled Volume "toolserver-inc-0603" on device "Toolserver-DISK" (/data/bacula-storage/toolserver) 30-Sep 12:06 VUMEM004-sd JobId 15915: New volume "toolserver-inc-0603" mounted on device "Toolserver-DISK" (/data/bacula-storage/toolserver) at 30-Sep-2009 12:06. I can't remember seen this warning befor upgrading to 3.0.x. Shouldn't bacula first label the volume and then check if it "exists"? I don't see a reason for this warning message. Ralf |