Hi Philippe
from what i can tell your volume is fine. I assume there is an issue in
your database however. You probably have a jobmedia id on that volume
with startblock 256 when it should be 255.
As you were consolidating the jobs 42340,41536,41594, it is safe to
assume that the problem is one of these jobs. I assume that the mediaid
of the affected volume is 525 (but double check this), so try checking
all jobmedia entries from those jobs on this volume and see if this is
indeed the case.
One thing i find weird is that to me it looks like the first record on
the volume is a StartOfSession record for jobid 40548, so maybe there
was a mixup somehow ?
You can check the records on a volume with "bscan -r/--list-records".
Maybe this can help you figure out what happened.
Kind Regards
Sebastian Sura
Am 18.06.24 um 19:57 schrieb 'Philippe' via bareos-users:
Hi Sebastian,
thanks for your reply.
Sure - here are the first 304 bytes:
$ dd if=AI-Incremental-0525 bs=304 count=1 status=none | xxd
00000000: c75d 2e97 0000 00ff 0000 0000 4242 3032 .]..........BB02
00000010: 0000 0030 6640 9701 ffff fffe 0000 0000 ...0f@..........
00000020: 0000 00db 4261 7265 6f73 2032 2e30 2069 ....Bareos 2.0 i
00000030: 6d6d 6f72 7461 6c0a 0000 0000 1400 05f2 mmortal.........
00000040: 2d86 4318 e000 0618 3f24 27be 9700 0000 -.C.....?$'.....
00000050: 0000 0000 0000 0000 0000 0000 0041 492d .............AI-
00000060: 496e 6372 656d 656e 7461 6c2d 3035 3235 Incremental-0525
00000070: 0000 4149 2d49 6e63 7265 6d65 6e74 616c ..AI-Incremental
00000080: 0042 6163 6b75 7000 4669 6c65 0073 6372 .Backup.File.scr
00000090: 6174 6368 792e 696e 7472 616e 6574 2e75 atchy.intranet.u
000000a0: 6e69 7861 646d 2e6f 7267 0073 6372 6174 nixadm.org.scrat
000000b0: 6368 792e 696e 7472 616e 6574 2e75 6e69 chy.intranet.uni
000000c0: 7861 646d 2e6f 7267 0056 6572 2e20 3232 xadm.org.Ver. 22
000000d0: 2e30 2e31 2030 3220 4a61 6e75 6172 7920 .0.1 02 January
000000e0: 3230 3233 0042 7569 6c64 2032 3032 332d 2023.Build 2023-
000000f0: 3031 2d30 3220 3135 3a35 393a 3335 0040 01-02 15:59:35.@
00000100: 5ae0 9300 1000 0000 0000 0042 4230 3200 Z..........BB02.
00000110: 0000 3066 4097 01ff ffff fc00 009e 6400 ..0f@.........d.
00000120: 0000 f042 6172 656f 7320 322e 3020 696d ...Bareos 2.0 im
As I read a suspicious "Bareos 22.0.1" in there I reckon it might have
something to do with what I read earler at
https://groups.google.com/g/bareos-users/c/HNEG3fSuCtk/m/eE9pJRA1BgAJ
Kind regards,
Philippe
On 18.06.24 16:12, Sebastian Sura wrote:
Hi Philippe
Looks like i misread your joblog. I missed that its forwarding the
volume to 0:256 (i.e. it skips the first 256 bytes [0, 255]).
That means that the first 256 bytes (the volume label) are read
correctly (as you verified).
Could you instead post the bytes [256, 280] (or to make off-by-ones
more unlikely, the first 300 bytes) ?
Sorry for the inconvenience!
Kind Regards
Sebastian Sura
Am 18.06.24 um 11:14 schrieb 'Philippe' via bareos-users:
Hi Sebastian,
thanks for your answer!
Here's what I get from the disk:
$ dd if=AI-Incremental-0525 bs=24 count=1 status=none | xxd
00000000: c75d 2e97 0000 00ff 0000 0000 4242 3032 .]..........BB02
00000010: 0000 0030 6640 9701 ...0f@..
comparing this with another file it doesn't look that bad for me:
$ dd if=AI-Incremental-0526 bs=24 count=1 status=none | xxd
00000000: d5fa 7af2 0000 00ff 0000 0000 4242 3032 ..z.........BB02
00000010: 0000 0030 6659 a382 ...0fY..
fwiw: the data resides on a zfs (scrubbed, verified) and the sd
machine powers up before the backups start and shuts down when
completed.
Kind regards,
Philippe
On 18.06.24 09:25, Sebastian Sura wrote:
Hi Philippe
It looks like the first block header of your volume somehow got
corrupted.
Could you try to read the first 24 bytes of that volume and send
them here ?
The block header is supposed to look like this:
https://docs.bareos.org/DeveloperGuide/mediaformat.html#block-header
While its probably not possible repair the block header ourselves,
we might be able to identify which byte was not written
and try to put it into a state where bareos will accept it.
Kind Regards
Sebastian Sura
Am 17.06.24 um 16:48 schrieb 'Philippe' via bareos-users:
(re-sending to list)
Hi Andreas,
thanks for clarifying this. So, probably at least after Bareos
throwing the "does not exists" error the file shows up with a size
of 61GiB.
Taking a closer look this report seem to have two errors, one
"non-fatal" error saying
Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer
discarded.
and the "fatal" error related to the non-existing file at some
point of time.
I don't know what's broken here but since the errors are refering
to different files every day regarding the fatal error but not the
"non-fatal" error, I believe the AI-Incremental-0525 file (which
exists for a month now and is 530M of size) might be corrupted.
12-Jun 12:52 storage JobId 42456: Forward spacing Volume
"AI-Incremental-0525" to file:block 0:256.
12-Jun 12:52 storage JobId 42456: Error: stored/block.cc:291
Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer
discarded.
12-Jun 12:52 storage JobId 42456: Fatal error: stored/mac.cc:696
Fatal append error on device "File-Consolidated-storage"
(/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could
not open: /backup/bareos-consolidated-tape/AI-Consolidated-0577,
ERR=No such file or directory
13-Jun 12:54 storage JobId 42515: Forward spacing Volume
"AI-Incremental-0525" to file:block 0:256.
13-Jun 12:54 storage JobId 42515: Error: stored/block.cc:291
Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer
discarded.
13-Jun 12:54 storage JobId 42515: Fatal error: stored/mac.cc:696
Fatal append error on device "File-Consolidated-storage"
(/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could
not open: /backup/bareos-consolidated-tape/AI-Consolidated-0578,
ERR=No such file or directory
14-Jun 12:54 storage JobId 42574: Forward spacing Volume
"AI-Incremental-0525" to file:block 0:256.
14-Jun 12:54 storage JobId 42574: Error: stored/block.cc:291
Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer
discarded.
14-Jun 12:54 storage JobId 42574: Fatal error: stored/mac.cc:696
Fatal append error on device "File-Consolidated-storage"
(/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could
not open: /backup/bareos-consolidated-tape/AI-Consolidated-0579,
ERR=No such file or directory
15-Jun 13:03 storage JobId 42633: Forward spacing Volume
"AI-Incremental-0525" to file:block 0:256.
15-Jun 13:03 storage JobId 42633: Error: stored/block.cc:291
Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer
discarded.
15-Jun 13:03 storage JobId 42633: Fatal error: stored/mac.cc:696
Fatal append error on device "File-Consolidated-storage"
(/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could
not open: /backup/bareos-consolidated-tape/AI-Consolidated-0581,
ERR=No such file or directory
16-Jun 12:51 storage JobId 42692: Forward spacing Volume
"AI-Incremental-0525" to file:block 0:256.
16-Jun 12:51 storage JobId 42692: Error: stored/block.cc:291
Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer
discarded.
16-Jun 12:51 storage JobId 42692: Fatal error: stored/mac.cc:696
Fatal append error on device "File-Consolidated-storage"
(/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could
not open: /backup/bareos-consolidated-tape/AI-Consolidated-0583,
ERR=No such file or directory
17-Jun 12:53 storage JobId 42751: Forward spacing Volume
"AI-Incremental-0525" to file:block 0:256.
17-Jun 12:53 storage JobId 42751: Error: stored/block.cc:291
Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer
discarded.
17-Jun 12:53 storage JobId 42751: Fatal error: stored/mac.cc:696
Fatal append error on device "File-Consolidated-storage"
(/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could
not open: /backup/bareos-consolidated-tape/AI-Consolidated-0585,
ERR=No such file or directory
So, are some of my backups lost? What can I do here - remove the
nextcloud-jobs and all previous backups and start from scratch?
Kind regards,
Philippe
--
Sebastian Sura sebastian.s...@bareos.com
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 bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/d46000f2-648c-49f8-bae5-059ae552f8b0%40bareos.com.
