I meant to say File 3 has no stream 1, sorry for the confusion!
Am 23.02.24 um 13:15 schrieb Sebastian Sura:
Hi Samuel
thanks for the gathering this info. Ill look into the bscan issue as
well though i think this might be a known issue.
Regardless, regarding your actual issue: The bscan output shows that
File 3 is missing its attributes (it has no stream 3).
This confuses the director as it never got told that file 3 now
started getting backed up and this is why you get the warning
message from the director.
The same is happening during the restore: the filedaemon never got
told that now a new file was started (because it never got the
attribute stream)
so it basically merged both File 2 and File 3 into one file. Even with
this in mind, i think the restore should have caught that and issues a
warning.
Ill look into why this did not happen.
If you add up all the data records (stream=2) with fileid=2 and
fileid=3, you will get 738212473 bytes, which is exactly what the
filedaemon reported
as size for file 2. Since the log contains the size it expected i
imagine that you could manually restore file 3 by splitting file 2
into two.
Can you check which file fileid 3 corresponds to ? Is it a special
kind of file or just a normal one ?
Ill try to see if i can reproduce your issue in the copy system test.
Do you do a local copy (so copy to the same sd) or a remote one?
Kind Regards
Sebastian Sura
Am 23.02.24 um 12:56 schrieb 'Samuel' via bareos-users:
Hi Sebastian,
After looking at the logs some more I noticed that all jobs with this
warning have in common that they're using compression (LZ4) and
autoxflate on replication.
Perhaps this combination is still not entirely fixed yet. I'll try
disabling autoxflate in the coming days.
The entire result of bscan is in the attachment. However here's the
last part of it where bscan seems to abort (?):
$ sudo -u bareos bscan -b md5_digest_error_copy_only.bsr
--list-records TapeDevice2 2>&1 | tee records.txt
...
bscan: stored/bscan.cc:494-0 Record: SessId=3480 SessTim=1707222936
FileIndex=23 Stream=2 len=65536
bscan: stored/bscan.cc:494-0 Record: SessId=3480 SessTim=1707222936
FileIndex=23 Stream=2 len=65536
bscan: stored/bscan.cc:494-0 Record: SessId=3480 SessTim=1707222936
FileIndex=23 Stream=2 len=65536
bscan: stored/bscan.cc:494-0 Record: SessId=3480 SessTim=1707222936
FileIndex=23 Stream=2 len=22528
bscan: stored/bscan.cc:494-0 Record: SessId=3480 SessTim=1707222936
FileIndex=23 Stream=3 len=16
bscan: stored/bscan.cc:494-0 Record: SessId=3480 SessTim=1707222936
FileIndex=24 Stream=1 len=100
bscan: stored/bscan.cc:494-0 Record: SessId=3480 SessTim=1707222936
FileIndex=25 Stream=1 len=83
bscan: stored/bscan.cc:494-0 Record: SessId=3480 SessTim=1707222936
FileIndex=-5 Stream=94145 len=193
bscan: stored/bscan.cc:681-0 Could not find SessId=3480
SessTime=1707222936 for EOS record.
Records would have been added or updated in the catalog:
0 Media
1 Pool
0 Job
0 File
0 RestoreObject
23-Feb 12:05 bscan JobId 0: Releasing device "TapeDevice2"
(/dev/tape/by-id/scsi-35000e111c71ac0bf-nst).
I also tried restoring the copy which ends in error.
Most files are restored successfully except for one file which
happens to have FileIndex=2 (corresponding to the `attributes=2` in
the warning?):
Enter SQL query: select path,name from file,path where jobid=94146
and fileindex=2 and file.pathid=path.pathid;
+-----------------------------------+--------------------------+
| path | name |
+-----------------------------------+--------------------------+
| /var/backup/old/2024-02-07_23:30/ | backup_www_1100CC.tar.gz |
+-----------------------------------+--------------------------+
A full restore of the original non-copy backup jobs works fine, as do
restores of other copy jobs on tape of filesets that don't use
compression.
The original job that was copied (93682) doesn't exist anymore; I
think it was an always-incremental consolidated incremental backup
which got consolidated again the following day.
Best regards,
Samuel
--
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/e766e8c6-5b58-424f-816f-f7c5d7252180n%40googlegroups.com
<https://groups.google.com/d/msgid/bareos-users/e766e8c6-5b58-424f-816f-f7c5d7252180n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Sebastian [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 on the web visit
https://groups.google.com/d/msgid/bareos-users/111cecfe-d3e1-4eb9-8a0e-f053a2777d0f%40bareos.com
<https://groups.google.com/d/msgid/bareos-users/111cecfe-d3e1-4eb9-8a0e-f053a2777d0f%40bareos.com?utm_medium=email&utm_source=footer>.
--
Sebastian [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 on the web visit
https://groups.google.com/d/msgid/bareos-users/87cf855a-7f0b-474e-8775-331aa942fa85%40bareos.com.
