This newly 23.0.4 regression has already been fixed https://github.com/bareos/bareos/pull/2003 and newly build should have that fixed too. So update your binary with version 23.0.5~pre173.c77e8930c <https://download.bareos.org/current/Fedora_39/x86_64/bareos-23.0.5~pre173.c77e8930c-135.fc39.x86_64.rpm> should provided fixed binary.
On Monday 11 November 2024 at 23:25:18 UTC+1 Jon Schewe wrote: > I'm seeing the same thing when writing to disk based volume. Here is an > example of the log entries. > > 2024-10-25 21:00:11 bareos-sd JobId 189: Labeled new Volume > "Incremental-0081" on device "onsite-file1" (/mnt/onsite-file). > 2024-10-25 21:00:11 atlas.bbn.com-fd JobId 189: ACL support is enabled > 2024-10-25 21:00:11 bareos-sd JobId 189: Moving to end of data on volume > "Incremental-0081" > 2024-10-25 21:00:11 bareos-sd JobId 189: Warning: For Volume > "Incremental-0081": > The sizes do not match! Volume=248 Catalog=0 > Correcting Catalog > > On Friday, October 18, 2024 at 1:06:16 AM UTC-5 Markus Dubois wrote: > >> my log message was deleted, what should i post? >> >> Sebastian Sura schrieb am Mittwoch, 16. Oktober 2024 um 14:06:10 UTC+2: >> >>> Hi Markus, >>> >>> do you mean this message pops up whenever bareos tries to append to/read >>> from a volume ? If so this is probably caused by you not migrating over >>> your old volumes to the new server. The database still contains references >>> to those old volumes and now when the director tells the storage daemon to >>> start appending to those volumes, the storage daemon is surprised that the >>> size that it was told by the director does not match up with the actual >>> size on disk (as it was probably newly created by the storage daemon). >>> >>> Could you post some job logs here so that I can confirm my suspicion ? >>> If that is the case, then you need to keep in mind that you may not be able >>> to easily access your old backups any more. >>> >>> Kind Regards >>> Sebastian Sura >>> Am 16.10.24 um 13:33 schrieb Markus Dubois: >>> >>> we've migrated Bareos (23.05) to another server and started fresh with a >>> new db >>> >>> don't know if this is new or if we just recognized it... >>> on every backup file creation (50GB) each, we get the entry The sizes do >>> not match >>> >>> ..backup ist still running. Does seems to work though..... >>> >>> Can we ignore those messages? >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "bareos-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/bareos-users/e4dc57db-fa90-4494-9a5c-628b272af3ecn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/bareos-users/e4dc57db-fa90-4494-9a5c-628b272af3ecn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- >>> Sebastian Sura [email protected] >>> Bareos GmbH & Co. KG Phone: +49 221 630693-0 >>> https://www.bareos.com >>> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 >>> Komplementär: Bareos Verwaltungs-GmbH >>> Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz >>> >>> -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bareos-users/d734d371-e9e7-4438-b9b4-55fb266ed9d4n%40googlegroups.com.
