You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(75) |
May
(2) |
Jun
(17) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(39) |
Feb
(22) |
Mar
(40) |
Apr
(12) |
May
(79) |
Jun
(11) |
Jul
(43) |
Aug
(25) |
Sep
(7) |
Oct
(62) |
Nov
(105) |
Dec
(114) |
| 2004 |
Jan
(109) |
Feb
(176) |
Mar
(208) |
Apr
(148) |
May
(91) |
Jun
(114) |
Jul
(47) |
Aug
(92) |
Sep
(82) |
Oct
(33) |
Nov
(221) |
Dec
(309) |
| 2005 |
Jan
(129) |
Feb
(244) |
Mar
(209) |
Apr
(194) |
May
(129) |
Jun
(267) |
Jul
(250) |
Aug
(422) |
Sep
(228) |
Oct
(141) |
Nov
(369) |
Dec
(176) |
| 2006 |
Jan
(184) |
Feb
(342) |
Mar
(296) |
Apr
(321) |
May
(225) |
Jun
(285) |
Jul
(264) |
Aug
(354) |
Sep
(279) |
Oct
(165) |
Nov
(221) |
Dec
(311) |
| 2007 |
Jan
(359) |
Feb
(194) |
Mar
(251) |
Apr
(188) |
May
(328) |
Jun
(263) |
Jul
(244) |
Aug
(339) |
Sep
(517) |
Oct
(156) |
Nov
(148) |
Dec
(158) |
| 2008 |
Jan
(158) |
Feb
(243) |
Mar
(180) |
Apr
(57) |
May
(156) |
Jun
(117) |
Jul
(189) |
Aug
(203) |
Sep
(250) |
Oct
(304) |
Nov
(130) |
Dec
(116) |
| 2009 |
Jan
(153) |
Feb
(123) |
Mar
(222) |
Apr
(171) |
May
(166) |
Jun
(127) |
Jul
(133) |
Aug
(102) |
Sep
(157) |
Oct
(191) |
Nov
(190) |
Dec
(229) |
| 2010 |
Jan
(207) |
Feb
(164) |
Mar
(125) |
Apr
(145) |
May
(139) |
Jun
(65) |
Jul
(97) |
Aug
(132) |
Sep
(87) |
Oct
(59) |
Nov
(81) |
Dec
(50) |
| 2011 |
Jan
(64) |
Feb
(41) |
Mar
(59) |
Apr
(42) |
May
(20) |
Jun
(39) |
Jul
(29) |
Aug
(59) |
Sep
(21) |
Oct
(66) |
Nov
(85) |
Dec
(45) |
| 2012 |
Jan
(25) |
Feb
(35) |
Mar
(41) |
Apr
(10) |
May
(26) |
Jun
(28) |
Jul
(32) |
Aug
(19) |
Sep
(31) |
Oct
(9) |
Nov
(21) |
Dec
(20) |
| 2013 |
Jan
(16) |
Feb
(23) |
Mar
(21) |
Apr
(16) |
May
(6) |
Jun
(2) |
Jul
(16) |
Aug
(13) |
Sep
(24) |
Oct
(28) |
Nov
(13) |
Dec
(20) |
| 2014 |
Jan
(11) |
Feb
(10) |
Mar
(51) |
Apr
(132) |
May
(9) |
Jun
(2) |
Jul
(4) |
Aug
(13) |
Sep
(3) |
Oct
(6) |
Nov
(42) |
Dec
(4) |
| 2015 |
Jan
(5) |
Feb
(11) |
Mar
(15) |
Apr
(15) |
May
(27) |
Jun
(3) |
Jul
(6) |
Aug
(10) |
Sep
(34) |
Oct
(29) |
Nov
(4) |
Dec
(1) |
| 2016 |
Jan
(29) |
Feb
(37) |
Mar
(3) |
Apr
|
May
(8) |
Jun
(8) |
Jul
(4) |
Aug
(4) |
Sep
(18) |
Oct
(13) |
Nov
(7) |
Dec
(3) |
| 2017 |
Jan
|
Feb
(10) |
Mar
(17) |
Apr
(4) |
May
(6) |
Jun
(35) |
Jul
(60) |
Aug
(57) |
Sep
(10) |
Oct
(33) |
Nov
(48) |
Dec
(2) |
| 2018 |
Jan
(5) |
Feb
(10) |
Mar
(2) |
Apr
(23) |
May
(12) |
Jun
(16) |
Jul
(10) |
Aug
(46) |
Sep
(1) |
Oct
(34) |
Nov
(12) |
Dec
(45) |
| 2019 |
Jan
(29) |
Feb
(22) |
Mar
(25) |
Apr
(13) |
May
(12) |
Jun
(8) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(30) |
| 2020 |
Jan
(5) |
Feb
(46) |
Mar
(19) |
Apr
(5) |
May
(10) |
Jun
(53) |
Jul
(34) |
Aug
(7) |
Sep
(22) |
Oct
(7) |
Nov
(9) |
Dec
(58) |
| 2021 |
Jan
(23) |
Feb
(11) |
Mar
(43) |
Apr
(7) |
May
(29) |
Jun
(10) |
Jul
|
Aug
|
Sep
|
Oct
(21) |
Nov
|
Dec
(4) |
| 2022 |
Jan
|
Feb
|
Mar
(37) |
Apr
|
May
(3) |
Jun
(6) |
Jul
(4) |
Aug
(14) |
Sep
(3) |
Oct
(1) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(20) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(10) |
Nov
(5) |
Dec
(2) |
| 2024 |
Jan
(2) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(41) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
(7) |
Nov
(9) |
Dec
(3) |
| 2025 |
Jan
(6) |
Feb
(5) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(6) |
Jul
|
Aug
(2) |
Sep
(13) |
Oct
(4) |
Nov
(1) |
Dec
(5) |
| 2026 |
Jan
(11) |
Feb
(1) |
Mar
(6) |
Apr
(2) |
May
(11) |
Jun
(5) |
Jul
|
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
|
2
|
|
3
(1) |
4
|
5
(3) |
6
(2) |
7
(1) |
8
|
9
|
|
10
(1) |
11
(2) |
12
(1) |
13
(1) |
14
|
15
(1) |
16
|
|
17
|
18
|
19
|
20
|
21
(1) |
22
(5) |
23
|
|
24
|
25
(2) |
26
|
27
|
28
|
29
|
30
|
|
31
|
|
|
|
|
|
|
|
From: Martin S. <ma...@li...> - 2021-10-25 17:13:03
|
That disk space should be OK as long as you don't have filesystem freespace limits (such as -m reserved-blocks-percentage in tune2fs) and that TB is 1099511627776 bytes and not the disk manufacturers' 1000000000000 bytes. OTOH, I don't see how the code can print the SI0202 message unless write() failed, so I still think filling the disk is the most likely reason. __Martin >>>>> On Mon, 25 Oct 2021 12:50:41 +0200, Marko Bartolić said: > > Yes, the following is set on the pool to keep the volumes manageable: > > Maximum Volume Bytes = 653197960000 > Maximum Volumes = 18 > > There are three 3.7 TB disks in that pool, I reckon this should keep the > disks from completely filling up. > > Marko Bartolić, Nimium d.o.o., email: <mar...@ni...> > Mob: +385 99 325 7180 > Zagrebačka cesta 145A/I, 10 000 Zagreb, Hrvatska > > On 22. 10. 2021. 17:06, Martin Simmons wrote: > > Ah, so the short block is part of jobid 12065 and therefore the copy of jobid > > 12068 is very likely to be complete. > > > > The "[SI0202] End of Volume" message means that write() wrote less that > > expected. The only reasons I can think of are disk space shortage, I/O error, > > some other process-specific limit (such as controlled by ulimit -f) or buggy > > filesystem. > > > > Have you set some limit on the volume size? It is interesting that those 3 > > volumes are all just slightly smaller that 653,198,000,000 bytes. > > > > __Martin > > > > > >>>>>> On Fri, 22 Oct 2021 13:53:12 +0200, Marko Bartolić said: > >> Hi, > >> > >> the backup job on 03-Oct definetly filled the volume 10, but not the > >> whole disk, it still has some free space. > >> > >> *list volume > >> > >> Automatically selected Catalog: MyCatalog > >> > >> Using Catalog "MyCatalog" > >> > >> Pool: Default > >> > >> +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+------------+ > >> > >> | mediaid | volumename | volstatus | enabled | volbytes | volfiles | volretention | recycle | slot | inchanger | mediatype | voltype | volparts | lastwritten | expiresin | > >> > >> +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+------------+ > >> > >> ... > >> > >> | 9 | volume-09 | Full | 1 | 653,197,959,321 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-09-06 23:06:04 | 11,615,551 | > >> | 10 | volume-10 | Full | 1 | 653,197,888,553 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-10-03 23:09:09 | 13,944,936 | > >> | 11 | volume-11 | Full | 1 | 653,197,958,518 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-10-05 13:11:17 | 14,081,864 | > >> > >> ... > >> > >> > >> > >> /var/log/messages or dmesg do not show any problems on 03-Oct. > >> > >> Yes, that is the complete output for jobid 12068 from bacula.log. But > >> there was another job running at approximately same time during which > >> the volume changed from 10 to 11: > >> > >> 03-Oct 23:09 backup-sd JobId 12065: [SI0202] End of Volume "volume-10" at 653197953065 on device "backup-device-data1" (/data1). Write of 64512 bytes got 42967. > >> > >> 03-Oct 23:09 backup-sd JobId 12065: End of medium on Volume "volume-10" Bytes=653,197,888,553 Blocks=10,125,619 at 03-Oct-2021 23:09. > >> > >> 03-Oct 23:09 backup-dir JobId 12065: There are no more Jobs associated with Volume "volume-11". Marking it purged. > >> > >> 03-Oct 23:09 backup-dir JobId 12065: All records pruned from Volume "volume-11"; marking it "Purged" > >> > >> 03-Oct 23:09 backup-dir JobId 12065: Recycled volume "volume-11" > >> > >> 03-Oct 23:09 backup-sd JobId 12065: Recycled volume "volume-11" on File device "backup-device-data1" (/data1), all previous data lost. > >> > >> 03-Oct 23:09 backup-sd JobId 12065: New volume "volume-11" mounted on device "backup-device-data1" (/data1) at 03-Oct-2021 23:09. > >> > >> > >> > >> Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> > >> > >> On 22. 10. 2021. 13:18, Martin Simmons wrote: > >>> Did the backup job on 03-Oct fill the disk? Did you check for syslog messages > >>> for that date too? > >>> > >>> Also, did you include the complete output below from the backup jobid 12068? > >>> I would expect more information to be printed between 03-Oct 23:06 and 03-Oct > >>> 23:19 about the volumes being used and the reason for changing from volume-10 > >>> to volume-11. > >>> > >>> __Martin > >>> > >>> > >>>>>>>> On Thu, 21 Oct 2021 16:27:13 +0200, Marko Bartolić said: > >>>> Hello, > >>>> > >>>> I hope this is the right place to ask. > >>>> > >>>> We have Bacula version 9.6.5. on a RHEL 8.2 physical server. We use copy > >>>> job that runs every 6 months and copies the last full backup of 22 > >>>> clients to a separate SCSI disk which is then pulled out from the server > >>>> for offsite backup. So both the backup disks and disk on which the > >>>> backups are later copied are local, physical disks in the machine. This > >>>> was working fine every time up to now. During last run of the copy job, > >>>> we noticed the following error on one of the copy jobs: > >>>> > >>>> 21-Oct 04:00 backup-dir JobId 12612: Copying using JobId=12068 Job=websrv.2021-10-03_23.05.00_12 > >>>> 21-Oct 05:45 backup-dir JobId 12612: Start Copying JobId 12612, Job=Copy-to-offsite-disk.2021-10-21_04.00.01_36 > >>>> 21-Oct 05:45 backup-dir JobId 12612: Using Device "backup-device-data1" to read. > >>>> 21-Oct 05:45 backup-sd JobId 12612: Ready to read from volume "volume-10" on File device "backup-device-data1" (/data1). > >>>> 21-Oct 05:45 backup-sd JobId 12612: Forward spacing Volume "volume-10" to addr=641829209227 > >>>> *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. ** > >>>> **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. * > >>>> 21-Oct 05:46 backup-sd JobId 12612: End of Volume "volume-10" at addr=653197996032 on device "backup-device-data1" (/data1). > >>>> 21-Oct 05:46 backup-sd JobId 12612: Ready to read from volume "volume-11" on File device "backup-device-data1" (/data1). > >>>> 21-Oct 05:46 backup-sd JobId 12612: Forward spacing Volume "volume-11" to addr=64742 > >>>> 21-Oct 05:50 backup-sd JobId 12612: End of Volume "volume-11" at addr=49666111453 on device "backup-device-data1" (/data1). > >>>> 21-Oct 05:50 backup-sd JobId 12612: Elapsed time=00:05:02, Transfer rate=16.65 M Bytes/second > >>>> 21-Oct 05:50 backup-dir JobId 12612: Error: Bacula backup-dir 9.6.5 (11Jun20): > >>>> Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) > >>>> Prev Backup JobId: 12068 > >>>> Prev Backup Job: websrv.2021-10-03_23.05.00_12 > >>>> New Backup JobId: 12613 > >>>> Current JobId: 12612 > >>>> Current Job: Copy-to-offsite-disk.2021-10-21_04.00.01_36 > >>>> Backup Level: Full > >>>> Client: backup-fd > >>>> FileSet: "backup" 2020-09-17 21:53:08 > >>>> Read Pool: "Default" (From Command input) > >>>> Read Storage: "backup-storage-data1" (From Pool resource) > >>>> Write Pool: "Offsite" (From Command input) > >>>> Write Storage: "backup-storage-data2" (From Command input) > >>>> Catalog: "MyCatalog" (From Client resource) > >>>> Start time: 21-Oct-2021 05:45:32 > >>>> End time: 21-Oct-2021 05:50:42 > >>>> Elapsed time: 5 mins 10 secs > >>>> Priority: 10 > >>>> * SD Files Written: 200,038 ** > >>>> ** SD Bytes Written: 5,029,190,722 (5.029 GB) * > >>>> Rate: 16223.2 KB/s > >>>> Volume name(s): vol-01 > >>>> Volume Session Id: 5353 > >>>> Volume Session Time: 1619097903 > >>>> Last Volume Bytes: 573,628,844,941 (573.6 GB) > >>>> SD Errors: 1 > >>>> SD termination status: OK > >>>> Termination: *** Copying Error *** > >>>> > >>>> > >>>> > >>>> Job ends with error, but upon checking the backup size and number of > >>>> files of the original "websrv" backup job (which was successful), we see > >>>> that the number of files and bytes written are the same as is in the > >>>> copy job: > >>>> > >>>> 03-Oct 23:06 backup-dir JobId 12068: Start Backup JobId 12068, Job=websrv.2021-10-03_23.05.00_12 > >>>> 03-Oct 23:06 backup-dir JobId 12068: Using Device "backup-device-data1" to write. > >>>> 03-Oct 23:06 websrv-fd JobId 12068: shell command: run ClientBeforeJob "/etc/bacula/scripts/mariadb-backup.sh" > >>>> 03-Oct 23:10 websrv-fd JobId 12068: /srv/cpap is a different filesystem. Will not descend from / into it. > >>>> 03-Oct 23:19 backup-sd JobId 12068: Elapsed time=00:13:26, Transfer rate=6.239 M Bytes/second > >>>> 03-Oct 23:19 backup-sd JobId 12068: Sending spooled attrs to the Director. Despooling 53,043,158 bytes ... > >>>> 03-Oct 23:19 backup-dir JobId 12068: Bacula backup-dir 9.6.5 (11Jun20): > >>>> Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) > >>>> JobId: 12068 > >>>> Job: websrv.2021-10-03_23.05.00_12 > >>>> Backup Level: Full > >>>> Client: "websrv-fd" 9.0.6 (20Nov17) x86_64-redhat-linux-gnu,redhat,Enterprise 8.1 > >>>> FileSet: "websrv" 2020-09-17 23:05:00 > >>>> Pool: "Default" (From Job resource) > >>>> Catalog: "MyCatalog" (From Client resource) > >>>> Storage: "backup-storage-data1" (From Pool resource) > >>>> Scheduled time: 03-Oct-2021 23:05:00 > >>>> Start time: 03-Oct-2021 23:06:04 > >>>> End time: 03-Oct-2021 23:19:37 > >>>> Elapsed time: 13 mins 33 secs > >>>> Priority: 10 > >>>> *FD Files Written: 200,038 SD Files Written: 200,038 FD Bytes Written: > >>>> 4,996,564,202 (4.996 GB) SD Bytes Written: 5,029,190,722 (5.029 GB)* > >>>> Rate: 6145.8 KB/s > >>>> Software Compression: 40.9% 1.7:1 > >>>> Comm Line Compression: 16.7% 1.2:1 > >>>> Snapshot/VSS: no > >>>> Encryption: no > >>>> Accurate: no > >>>> Volume name(s): volume-10|volume-11 > >>>> Volume Session Id: 4812 > >>>> Volume Session Time: 1619097903 > >>>> Last Volume Bytes: 49,996,799,959 (49.99 GB) > >>>> Non-fatal FD errors: 0 > >>>> SD Errors: 0 > >>>> FD termination status: OK > >>>> SD termination status: OK > >>>> Termination: Backup OK > >>>> > >>>> 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Jobs older than 6 months . > >>>> 03-Oct 23:19 backup-dir JobId 12068: Pruned 1 Job for client websrv-fd from catalog. > >>>> 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Files. > >>>> 03-Oct 23:19 backup-dir JobId 12068: Pruned Files from 1 Jobs for client websrv-fd from catalog. > >>>> 03-Oct 23:19 backup-dir JobId 12068: End auto prune. > >>>> > >>>> > >>>> I also don't see any errors in messages or dmesg output. > >>>> > >>>> From what I gathered from an older thread: > >>>> https://marc.info/?l=bacula-devel&m=123237957307571&w=2 > >>>> <https://marc.info/?l=bacula-devel&m=123237957307571&w=2> , this points > >>>> that copying completed successfully. Also mentioned in the thread is > >>>> that "Maximium Block Size" could be the problem, but we haven't defined > >>>> that property. > >>>> > >>>> Does anyone know what could cause this? > >>>> > >>>> > >>>> BR > >>>> > >>>> -- > >>>> Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> > >>>> > > > > > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel > |
|
From: Marko B. <mar...@ni...> - 2021-10-25 10:50:56
|
Yes, the following is set on the pool to keep the volumes manageable: Maximum Volume Bytes = 653197960000 Maximum Volumes = 18 There are three 3.7 TB disks in that pool, I reckon this should keep the disks from completely filling up. Marko Bartolić, Nimium d.o.o., email: <mar...@ni...> Mob: +385 99 325 7180 Zagrebačka cesta 145A/I, 10 000 Zagreb, Hrvatska On 22. 10. 2021. 17:06, Martin Simmons wrote: > Ah, so the short block is part of jobid 12065 and therefore the copy of jobid > 12068 is very likely to be complete. > > The "[SI0202] End of Volume" message means that write() wrote less that > expected. The only reasons I can think of are disk space shortage, I/O error, > some other process-specific limit (such as controlled by ulimit -f) or buggy > filesystem. > > Have you set some limit on the volume size? It is interesting that those 3 > volumes are all just slightly smaller that 653,198,000,000 bytes. > > __Martin > > >>>>>> On Fri, 22 Oct 2021 13:53:12 +0200, Marko Bartolić said: >> Hi, >> >> the backup job on 03-Oct definetly filled the volume 10, but not the >> whole disk, it still has some free space. >> >> *list volume >> >> Automatically selected Catalog: MyCatalog >> >> Using Catalog "MyCatalog" >> >> Pool: Default >> >> +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+------------+ >> >> | mediaid | volumename | volstatus | enabled | volbytes | volfiles | volretention | recycle | slot | inchanger | mediatype | voltype | volparts | lastwritten | expiresin | >> >> +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+------------+ >> >> ... >> >> | 9 | volume-09 | Full | 1 | 653,197,959,321 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-09-06 23:06:04 | 11,615,551 | >> | 10 | volume-10 | Full | 1 | 653,197,888,553 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-10-03 23:09:09 | 13,944,936 | >> | 11 | volume-11 | Full | 1 | 653,197,958,518 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-10-05 13:11:17 | 14,081,864 | >> >> ... >> >> >> >> /var/log/messages or dmesg do not show any problems on 03-Oct. >> >> Yes, that is the complete output for jobid 12068 from bacula.log. But >> there was another job running at approximately same time during which >> the volume changed from 10 to 11: >> >> 03-Oct 23:09 backup-sd JobId 12065: [SI0202] End of Volume "volume-10" at 653197953065 on device "backup-device-data1" (/data1). Write of 64512 bytes got 42967. >> >> 03-Oct 23:09 backup-sd JobId 12065: End of medium on Volume "volume-10" Bytes=653,197,888,553 Blocks=10,125,619 at 03-Oct-2021 23:09. >> >> 03-Oct 23:09 backup-dir JobId 12065: There are no more Jobs associated with Volume "volume-11". Marking it purged. >> >> 03-Oct 23:09 backup-dir JobId 12065: All records pruned from Volume "volume-11"; marking it "Purged" >> >> 03-Oct 23:09 backup-dir JobId 12065: Recycled volume "volume-11" >> >> 03-Oct 23:09 backup-sd JobId 12065: Recycled volume "volume-11" on File device "backup-device-data1" (/data1), all previous data lost. >> >> 03-Oct 23:09 backup-sd JobId 12065: New volume "volume-11" mounted on device "backup-device-data1" (/data1) at 03-Oct-2021 23:09. >> >> >> >> Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> >> >> On 22. 10. 2021. 13:18, Martin Simmons wrote: >>> Did the backup job on 03-Oct fill the disk? Did you check for syslog messages >>> for that date too? >>> >>> Also, did you include the complete output below from the backup jobid 12068? >>> I would expect more information to be printed between 03-Oct 23:06 and 03-Oct >>> 23:19 about the volumes being used and the reason for changing from volume-10 >>> to volume-11. >>> >>> __Martin >>> >>> >>>>>>>> On Thu, 21 Oct 2021 16:27:13 +0200, Marko Bartolić said: >>>> Hello, >>>> >>>> I hope this is the right place to ask. >>>> >>>> We have Bacula version 9.6.5. on a RHEL 8.2 physical server. We use copy >>>> job that runs every 6 months and copies the last full backup of 22 >>>> clients to a separate SCSI disk which is then pulled out from the server >>>> for offsite backup. So both the backup disks and disk on which the >>>> backups are later copied are local, physical disks in the machine. This >>>> was working fine every time up to now. During last run of the copy job, >>>> we noticed the following error on one of the copy jobs: >>>> >>>> 21-Oct 04:00 backup-dir JobId 12612: Copying using JobId=12068 Job=websrv.2021-10-03_23.05.00_12 >>>> 21-Oct 05:45 backup-dir JobId 12612: Start Copying JobId 12612, Job=Copy-to-offsite-disk.2021-10-21_04.00.01_36 >>>> 21-Oct 05:45 backup-dir JobId 12612: Using Device "backup-device-data1" to read. >>>> 21-Oct 05:45 backup-sd JobId 12612: Ready to read from volume "volume-10" on File device "backup-device-data1" (/data1). >>>> 21-Oct 05:45 backup-sd JobId 12612: Forward spacing Volume "volume-10" to addr=641829209227 >>>> *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. ** >>>> **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. * >>>> 21-Oct 05:46 backup-sd JobId 12612: End of Volume "volume-10" at addr=653197996032 on device "backup-device-data1" (/data1). >>>> 21-Oct 05:46 backup-sd JobId 12612: Ready to read from volume "volume-11" on File device "backup-device-data1" (/data1). >>>> 21-Oct 05:46 backup-sd JobId 12612: Forward spacing Volume "volume-11" to addr=64742 >>>> 21-Oct 05:50 backup-sd JobId 12612: End of Volume "volume-11" at addr=49666111453 on device "backup-device-data1" (/data1). >>>> 21-Oct 05:50 backup-sd JobId 12612: Elapsed time=00:05:02, Transfer rate=16.65 M Bytes/second >>>> 21-Oct 05:50 backup-dir JobId 12612: Error: Bacula backup-dir 9.6.5 (11Jun20): >>>> Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) >>>> Prev Backup JobId: 12068 >>>> Prev Backup Job: websrv.2021-10-03_23.05.00_12 >>>> New Backup JobId: 12613 >>>> Current JobId: 12612 >>>> Current Job: Copy-to-offsite-disk.2021-10-21_04.00.01_36 >>>> Backup Level: Full >>>> Client: backup-fd >>>> FileSet: "backup" 2020-09-17 21:53:08 >>>> Read Pool: "Default" (From Command input) >>>> Read Storage: "backup-storage-data1" (From Pool resource) >>>> Write Pool: "Offsite" (From Command input) >>>> Write Storage: "backup-storage-data2" (From Command input) >>>> Catalog: "MyCatalog" (From Client resource) >>>> Start time: 21-Oct-2021 05:45:32 >>>> End time: 21-Oct-2021 05:50:42 >>>> Elapsed time: 5 mins 10 secs >>>> Priority: 10 >>>> * SD Files Written: 200,038 ** >>>> ** SD Bytes Written: 5,029,190,722 (5.029 GB) * >>>> Rate: 16223.2 KB/s >>>> Volume name(s): vol-01 >>>> Volume Session Id: 5353 >>>> Volume Session Time: 1619097903 >>>> Last Volume Bytes: 573,628,844,941 (573.6 GB) >>>> SD Errors: 1 >>>> SD termination status: OK >>>> Termination: *** Copying Error *** >>>> >>>> >>>> >>>> Job ends with error, but upon checking the backup size and number of >>>> files of the original "websrv" backup job (which was successful), we see >>>> that the number of files and bytes written are the same as is in the >>>> copy job: >>>> >>>> 03-Oct 23:06 backup-dir JobId 12068: Start Backup JobId 12068, Job=websrv.2021-10-03_23.05.00_12 >>>> 03-Oct 23:06 backup-dir JobId 12068: Using Device "backup-device-data1" to write. >>>> 03-Oct 23:06 websrv-fd JobId 12068: shell command: run ClientBeforeJob "/etc/bacula/scripts/mariadb-backup.sh" >>>> 03-Oct 23:10 websrv-fd JobId 12068: /srv/cpap is a different filesystem. Will not descend from / into it. >>>> 03-Oct 23:19 backup-sd JobId 12068: Elapsed time=00:13:26, Transfer rate=6.239 M Bytes/second >>>> 03-Oct 23:19 backup-sd JobId 12068: Sending spooled attrs to the Director. Despooling 53,043,158 bytes ... >>>> 03-Oct 23:19 backup-dir JobId 12068: Bacula backup-dir 9.6.5 (11Jun20): >>>> Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) >>>> JobId: 12068 >>>> Job: websrv.2021-10-03_23.05.00_12 >>>> Backup Level: Full >>>> Client: "websrv-fd" 9.0.6 (20Nov17) x86_64-redhat-linux-gnu,redhat,Enterprise 8.1 >>>> FileSet: "websrv" 2020-09-17 23:05:00 >>>> Pool: "Default" (From Job resource) >>>> Catalog: "MyCatalog" (From Client resource) >>>> Storage: "backup-storage-data1" (From Pool resource) >>>> Scheduled time: 03-Oct-2021 23:05:00 >>>> Start time: 03-Oct-2021 23:06:04 >>>> End time: 03-Oct-2021 23:19:37 >>>> Elapsed time: 13 mins 33 secs >>>> Priority: 10 >>>> *FD Files Written: 200,038 SD Files Written: 200,038 FD Bytes Written: >>>> 4,996,564,202 (4.996 GB) SD Bytes Written: 5,029,190,722 (5.029 GB)* >>>> Rate: 6145.8 KB/s >>>> Software Compression: 40.9% 1.7:1 >>>> Comm Line Compression: 16.7% 1.2:1 >>>> Snapshot/VSS: no >>>> Encryption: no >>>> Accurate: no >>>> Volume name(s): volume-10|volume-11 >>>> Volume Session Id: 4812 >>>> Volume Session Time: 1619097903 >>>> Last Volume Bytes: 49,996,799,959 (49.99 GB) >>>> Non-fatal FD errors: 0 >>>> SD Errors: 0 >>>> FD termination status: OK >>>> SD termination status: OK >>>> Termination: Backup OK >>>> >>>> 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Jobs older than 6 months . >>>> 03-Oct 23:19 backup-dir JobId 12068: Pruned 1 Job for client websrv-fd from catalog. >>>> 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Files. >>>> 03-Oct 23:19 backup-dir JobId 12068: Pruned Files from 1 Jobs for client websrv-fd from catalog. >>>> 03-Oct 23:19 backup-dir JobId 12068: End auto prune. >>>> >>>> >>>> I also don't see any errors in messages or dmesg output. >>>> >>>> From what I gathered from an older thread: >>>> https://marc.info/?l=bacula-devel&m=123237957307571&w=2 >>>> <https://marc.info/?l=bacula-devel&m=123237957307571&w=2> , this points >>>> that copying completed successfully. Also mentioned in the thread is >>>> that "Maximium Block Size" could be the problem, but we haven't defined >>>> that property. >>>> >>>> Does anyone know what could cause this? >>>> >>>> >>>> BR >>>> >>>> -- >>>> Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> >>>> |
|
From: Martin S. <ma...@li...> - 2021-10-22 15:06:23
|
Ah, so the short block is part of jobid 12065 and therefore the copy of jobid 12068 is very likely to be complete. The "[SI0202] End of Volume" message means that write() wrote less that expected. The only reasons I can think of are disk space shortage, I/O error, some other process-specific limit (such as controlled by ulimit -f) or buggy filesystem. Have you set some limit on the volume size? It is interesting that those 3 volumes are all just slightly smaller that 653,198,000,000 bytes. __Martin >>>>> On Fri, 22 Oct 2021 13:53:12 +0200, Marko Bartolić said: > > Hi, > > the backup job on 03-Oct definetly filled the volume 10, but not the > whole disk, it still has some free space. > > *list volume > > Automatically selected Catalog: MyCatalog > > Using Catalog "MyCatalog" > > Pool: Default > > +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+------------+ > > | mediaid | volumename | volstatus | enabled | volbytes | volfiles | volretention | recycle | slot | inchanger | mediatype | voltype | volparts | lastwritten | expiresin | > > +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+------------+ > > ... > > | 9 | volume-09 | Full | 1 | 653,197,959,321 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-09-06 23:06:04 | 11,615,551 | > | 10 | volume-10 | Full | 1 | 653,197,888,553 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-10-03 23:09:09 | 13,944,936 | > | 11 | volume-11 | Full | 1 | 653,197,958,518 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-10-05 13:11:17 | 14,081,864 | > > ... > > > > /var/log/messages or dmesg do not show any problems on 03-Oct. > > Yes, that is the complete output for jobid 12068 from bacula.log. But > there was another job running at approximately same time during which > the volume changed from 10 to 11: > > 03-Oct 23:09 backup-sd JobId 12065: [SI0202] End of Volume "volume-10" at 653197953065 on device "backup-device-data1" (/data1). Write of 64512 bytes got 42967. > > 03-Oct 23:09 backup-sd JobId 12065: End of medium on Volume "volume-10" Bytes=653,197,888,553 Blocks=10,125,619 at 03-Oct-2021 23:09. > > 03-Oct 23:09 backup-dir JobId 12065: There are no more Jobs associated with Volume "volume-11". Marking it purged. > > 03-Oct 23:09 backup-dir JobId 12065: All records pruned from Volume "volume-11"; marking it "Purged" > > 03-Oct 23:09 backup-dir JobId 12065: Recycled volume "volume-11" > > 03-Oct 23:09 backup-sd JobId 12065: Recycled volume "volume-11" on File device "backup-device-data1" (/data1), all previous data lost. > > 03-Oct 23:09 backup-sd JobId 12065: New volume "volume-11" mounted on device "backup-device-data1" (/data1) at 03-Oct-2021 23:09. > > > > Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> > > On 22. 10. 2021. 13:18, Martin Simmons wrote: > > Did the backup job on 03-Oct fill the disk? Did you check for syslog messages > > for that date too? > > > > Also, did you include the complete output below from the backup jobid 12068? > > I would expect more information to be printed between 03-Oct 23:06 and 03-Oct > > 23:19 about the volumes being used and the reason for changing from volume-10 > > to volume-11. > > > > __Martin > > > > > >>>>>> On Thu, 21 Oct 2021 16:27:13 +0200, Marko Bartolić said: > >> Hello, > >> > >> I hope this is the right place to ask. > >> > >> We have Bacula version 9.6.5. on a RHEL 8.2 physical server. We use copy > >> job that runs every 6 months and copies the last full backup of 22 > >> clients to a separate SCSI disk which is then pulled out from the server > >> for offsite backup. So both the backup disks and disk on which the > >> backups are later copied are local, physical disks in the machine. This > >> was working fine every time up to now. During last run of the copy job, > >> we noticed the following error on one of the copy jobs: > >> > >> 21-Oct 04:00 backup-dir JobId 12612: Copying using JobId=12068 Job=websrv.2021-10-03_23.05.00_12 > >> 21-Oct 05:45 backup-dir JobId 12612: Start Copying JobId 12612, Job=Copy-to-offsite-disk.2021-10-21_04.00.01_36 > >> 21-Oct 05:45 backup-dir JobId 12612: Using Device "backup-device-data1" to read. > >> 21-Oct 05:45 backup-sd JobId 12612: Ready to read from volume "volume-10" on File device "backup-device-data1" (/data1). > >> 21-Oct 05:45 backup-sd JobId 12612: Forward spacing Volume "volume-10" to addr=641829209227 > >> *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. ** > >> **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. * > >> 21-Oct 05:46 backup-sd JobId 12612: End of Volume "volume-10" at addr=653197996032 on device "backup-device-data1" (/data1). > >> 21-Oct 05:46 backup-sd JobId 12612: Ready to read from volume "volume-11" on File device "backup-device-data1" (/data1). > >> 21-Oct 05:46 backup-sd JobId 12612: Forward spacing Volume "volume-11" to addr=64742 > >> 21-Oct 05:50 backup-sd JobId 12612: End of Volume "volume-11" at addr=49666111453 on device "backup-device-data1" (/data1). > >> 21-Oct 05:50 backup-sd JobId 12612: Elapsed time=00:05:02, Transfer rate=16.65 M Bytes/second > >> 21-Oct 05:50 backup-dir JobId 12612: Error: Bacula backup-dir 9.6.5 (11Jun20): > >> Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) > >> Prev Backup JobId: 12068 > >> Prev Backup Job: websrv.2021-10-03_23.05.00_12 > >> New Backup JobId: 12613 > >> Current JobId: 12612 > >> Current Job: Copy-to-offsite-disk.2021-10-21_04.00.01_36 > >> Backup Level: Full > >> Client: backup-fd > >> FileSet: "backup" 2020-09-17 21:53:08 > >> Read Pool: "Default" (From Command input) > >> Read Storage: "backup-storage-data1" (From Pool resource) > >> Write Pool: "Offsite" (From Command input) > >> Write Storage: "backup-storage-data2" (From Command input) > >> Catalog: "MyCatalog" (From Client resource) > >> Start time: 21-Oct-2021 05:45:32 > >> End time: 21-Oct-2021 05:50:42 > >> Elapsed time: 5 mins 10 secs > >> Priority: 10 > >> * SD Files Written: 200,038 ** > >> ** SD Bytes Written: 5,029,190,722 (5.029 GB) * > >> Rate: 16223.2 KB/s > >> Volume name(s): vol-01 > >> Volume Session Id: 5353 > >> Volume Session Time: 1619097903 > >> Last Volume Bytes: 573,628,844,941 (573.6 GB) > >> SD Errors: 1 > >> SD termination status: OK > >> Termination: *** Copying Error *** > >> > >> > >> > >> Job ends with error, but upon checking the backup size and number of > >> files of the original "websrv" backup job (which was successful), we see > >> that the number of files and bytes written are the same as is in the > >> copy job: > >> > >> 03-Oct 23:06 backup-dir JobId 12068: Start Backup JobId 12068, Job=websrv.2021-10-03_23.05.00_12 > >> 03-Oct 23:06 backup-dir JobId 12068: Using Device "backup-device-data1" to write. > >> 03-Oct 23:06 websrv-fd JobId 12068: shell command: run ClientBeforeJob "/etc/bacula/scripts/mariadb-backup.sh" > >> 03-Oct 23:10 websrv-fd JobId 12068: /srv/cpap is a different filesystem. Will not descend from / into it. > >> 03-Oct 23:19 backup-sd JobId 12068: Elapsed time=00:13:26, Transfer rate=6.239 M Bytes/second > >> 03-Oct 23:19 backup-sd JobId 12068: Sending spooled attrs to the Director. Despooling 53,043,158 bytes ... > >> 03-Oct 23:19 backup-dir JobId 12068: Bacula backup-dir 9.6.5 (11Jun20): > >> Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) > >> JobId: 12068 > >> Job: websrv.2021-10-03_23.05.00_12 > >> Backup Level: Full > >> Client: "websrv-fd" 9.0.6 (20Nov17) x86_64-redhat-linux-gnu,redhat,Enterprise 8.1 > >> FileSet: "websrv" 2020-09-17 23:05:00 > >> Pool: "Default" (From Job resource) > >> Catalog: "MyCatalog" (From Client resource) > >> Storage: "backup-storage-data1" (From Pool resource) > >> Scheduled time: 03-Oct-2021 23:05:00 > >> Start time: 03-Oct-2021 23:06:04 > >> End time: 03-Oct-2021 23:19:37 > >> Elapsed time: 13 mins 33 secs > >> Priority: 10 > >> *FD Files Written: 200,038 SD Files Written: 200,038 FD Bytes Written: > >> 4,996,564,202 (4.996 GB) SD Bytes Written: 5,029,190,722 (5.029 GB)* > >> Rate: 6145.8 KB/s > >> Software Compression: 40.9% 1.7:1 > >> Comm Line Compression: 16.7% 1.2:1 > >> Snapshot/VSS: no > >> Encryption: no > >> Accurate: no > >> Volume name(s): volume-10|volume-11 > >> Volume Session Id: 4812 > >> Volume Session Time: 1619097903 > >> Last Volume Bytes: 49,996,799,959 (49.99 GB) > >> Non-fatal FD errors: 0 > >> SD Errors: 0 > >> FD termination status: OK > >> SD termination status: OK > >> Termination: Backup OK > >> > >> 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Jobs older than 6 months . > >> 03-Oct 23:19 backup-dir JobId 12068: Pruned 1 Job for client websrv-fd from catalog. > >> 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Files. > >> 03-Oct 23:19 backup-dir JobId 12068: Pruned Files from 1 Jobs for client websrv-fd from catalog. > >> 03-Oct 23:19 backup-dir JobId 12068: End auto prune. > >> > >> > >> I also don't see any errors in messages or dmesg output. > >> > >> From what I gathered from an older thread: > >> https://marc.info/?l=bacula-devel&m=123237957307571&w=2 > >> <https://marc.info/?l=bacula-devel&m=123237957307571&w=2> , this points > >> that copying completed successfully. Also mentioned in the thread is > >> that "Maximium Block Size" could be the problem, but we haven't defined > >> that property. > >> > >> Does anyone know what could cause this? > >> > >> > >> BR > >> > >> -- > >> Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> > >> > |
|
From: Marko B. <mar...@ni...> - 2021-10-22 12:13:07
|
Hi, the backup job on 03-Oct definetly filled the volume 10, but not the whole disk, it still has some free space. *list volume Automatically selected Catalog: MyCatalog Using Catalog "MyCatalog" Pool: Default +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+------------+ | mediaid | volumename | volstatus | enabled | volbytes | volfiles | volretention | recycle | slot | inchanger | mediatype | voltype | volparts | lastwritten | expiresin | +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+------------+ ... | 9 | volume-09 | Full | 1 | 653,197,959,321 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-09-06 23:06:04 | 11,615,551 | | 10 | volume-10 | Full | 1 | 653,197,888,553 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-10-03 23:09:09 | 13,944,936 | | 11 | volume-11 | Full | 1 | 653,197,958,518 | 152 | 15,552,000 | 1 | 0 | 0 | data1 | 1 | 0 | 2021-10-05 13:11:17 | 14,081,864 | ... /var/log/messages or dmesg do not show any problems on 03-Oct. Yes, that is the complete output for jobid 12068 from bacula.log. But there was another job running at approximately same time during which the volume changed from 10 to 11: 03-Oct 23:09 backup-sd JobId 12065: [SI0202] End of Volume "volume-10" at 653197953065 on device "backup-device-data1" (/data1). Write of 64512 bytes got 42967. 03-Oct 23:09 backup-sd JobId 12065: End of medium on Volume "volume-10" Bytes=653,197,888,553 Blocks=10,125,619 at 03-Oct-2021 23:09. 03-Oct 23:09 backup-dir JobId 12065: There are no more Jobs associated with Volume "volume-11". Marking it purged. 03-Oct 23:09 backup-dir JobId 12065: All records pruned from Volume "volume-11"; marking it "Purged" 03-Oct 23:09 backup-dir JobId 12065: Recycled volume "volume-11" 03-Oct 23:09 backup-sd JobId 12065: Recycled volume "volume-11" on File device "backup-device-data1" (/data1), all previous data lost. 03-Oct 23:09 backup-sd JobId 12065: New volume "volume-11" mounted on device "backup-device-data1" (/data1) at 03-Oct-2021 23:09. Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> On 22. 10. 2021. 13:18, Martin Simmons wrote: > Did the backup job on 03-Oct fill the disk? Did you check for syslog messages > for that date too? > > Also, did you include the complete output below from the backup jobid 12068? > I would expect more information to be printed between 03-Oct 23:06 and 03-Oct > 23:19 about the volumes being used and the reason for changing from volume-10 > to volume-11. > > __Martin > > >>>>>> On Thu, 21 Oct 2021 16:27:13 +0200, Marko Bartolić said: >> Hello, >> >> I hope this is the right place to ask. >> >> We have Bacula version 9.6.5. on a RHEL 8.2 physical server. We use copy >> job that runs every 6 months and copies the last full backup of 22 >> clients to a separate SCSI disk which is then pulled out from the server >> for offsite backup. So both the backup disks and disk on which the >> backups are later copied are local, physical disks in the machine. This >> was working fine every time up to now. During last run of the copy job, >> we noticed the following error on one of the copy jobs: >> >> 21-Oct 04:00 backup-dir JobId 12612: Copying using JobId=12068 Job=websrv.2021-10-03_23.05.00_12 >> 21-Oct 05:45 backup-dir JobId 12612: Start Copying JobId 12612, Job=Copy-to-offsite-disk.2021-10-21_04.00.01_36 >> 21-Oct 05:45 backup-dir JobId 12612: Using Device "backup-device-data1" to read. >> 21-Oct 05:45 backup-sd JobId 12612: Ready to read from volume "volume-10" on File device "backup-device-data1" (/data1). >> 21-Oct 05:45 backup-sd JobId 12612: Forward spacing Volume "volume-10" to addr=641829209227 >> *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. ** >> **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. * >> 21-Oct 05:46 backup-sd JobId 12612: End of Volume "volume-10" at addr=653197996032 on device "backup-device-data1" (/data1). >> 21-Oct 05:46 backup-sd JobId 12612: Ready to read from volume "volume-11" on File device "backup-device-data1" (/data1). >> 21-Oct 05:46 backup-sd JobId 12612: Forward spacing Volume "volume-11" to addr=64742 >> 21-Oct 05:50 backup-sd JobId 12612: End of Volume "volume-11" at addr=49666111453 on device "backup-device-data1" (/data1). >> 21-Oct 05:50 backup-sd JobId 12612: Elapsed time=00:05:02, Transfer rate=16.65 M Bytes/second >> 21-Oct 05:50 backup-dir JobId 12612: Error: Bacula backup-dir 9.6.5 (11Jun20): >> Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) >> Prev Backup JobId: 12068 >> Prev Backup Job: websrv.2021-10-03_23.05.00_12 >> New Backup JobId: 12613 >> Current JobId: 12612 >> Current Job: Copy-to-offsite-disk.2021-10-21_04.00.01_36 >> Backup Level: Full >> Client: backup-fd >> FileSet: "backup" 2020-09-17 21:53:08 >> Read Pool: "Default" (From Command input) >> Read Storage: "backup-storage-data1" (From Pool resource) >> Write Pool: "Offsite" (From Command input) >> Write Storage: "backup-storage-data2" (From Command input) >> Catalog: "MyCatalog" (From Client resource) >> Start time: 21-Oct-2021 05:45:32 >> End time: 21-Oct-2021 05:50:42 >> Elapsed time: 5 mins 10 secs >> Priority: 10 >> * SD Files Written: 200,038 ** >> ** SD Bytes Written: 5,029,190,722 (5.029 GB) * >> Rate: 16223.2 KB/s >> Volume name(s): vol-01 >> Volume Session Id: 5353 >> Volume Session Time: 1619097903 >> Last Volume Bytes: 573,628,844,941 (573.6 GB) >> SD Errors: 1 >> SD termination status: OK >> Termination: *** Copying Error *** >> >> >> >> Job ends with error, but upon checking the backup size and number of >> files of the original "websrv" backup job (which was successful), we see >> that the number of files and bytes written are the same as is in the >> copy job: >> >> 03-Oct 23:06 backup-dir JobId 12068: Start Backup JobId 12068, Job=websrv.2021-10-03_23.05.00_12 >> 03-Oct 23:06 backup-dir JobId 12068: Using Device "backup-device-data1" to write. >> 03-Oct 23:06 websrv-fd JobId 12068: shell command: run ClientBeforeJob "/etc/bacula/scripts/mariadb-backup.sh" >> 03-Oct 23:10 websrv-fd JobId 12068: /srv/cpap is a different filesystem. Will not descend from / into it. >> 03-Oct 23:19 backup-sd JobId 12068: Elapsed time=00:13:26, Transfer rate=6.239 M Bytes/second >> 03-Oct 23:19 backup-sd JobId 12068: Sending spooled attrs to the Director. Despooling 53,043,158 bytes ... >> 03-Oct 23:19 backup-dir JobId 12068: Bacula backup-dir 9.6.5 (11Jun20): >> Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) >> JobId: 12068 >> Job: websrv.2021-10-03_23.05.00_12 >> Backup Level: Full >> Client: "websrv-fd" 9.0.6 (20Nov17) x86_64-redhat-linux-gnu,redhat,Enterprise 8.1 >> FileSet: "websrv" 2020-09-17 23:05:00 >> Pool: "Default" (From Job resource) >> Catalog: "MyCatalog" (From Client resource) >> Storage: "backup-storage-data1" (From Pool resource) >> Scheduled time: 03-Oct-2021 23:05:00 >> Start time: 03-Oct-2021 23:06:04 >> End time: 03-Oct-2021 23:19:37 >> Elapsed time: 13 mins 33 secs >> Priority: 10 >> *FD Files Written: 200,038 SD Files Written: 200,038 FD Bytes Written: >> 4,996,564,202 (4.996 GB) SD Bytes Written: 5,029,190,722 (5.029 GB)* >> Rate: 6145.8 KB/s >> Software Compression: 40.9% 1.7:1 >> Comm Line Compression: 16.7% 1.2:1 >> Snapshot/VSS: no >> Encryption: no >> Accurate: no >> Volume name(s): volume-10|volume-11 >> Volume Session Id: 4812 >> Volume Session Time: 1619097903 >> Last Volume Bytes: 49,996,799,959 (49.99 GB) >> Non-fatal FD errors: 0 >> SD Errors: 0 >> FD termination status: OK >> SD termination status: OK >> Termination: Backup OK >> >> 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Jobs older than 6 months . >> 03-Oct 23:19 backup-dir JobId 12068: Pruned 1 Job for client websrv-fd from catalog. >> 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Files. >> 03-Oct 23:19 backup-dir JobId 12068: Pruned Files from 1 Jobs for client websrv-fd from catalog. >> 03-Oct 23:19 backup-dir JobId 12068: End auto prune. >> >> >> I also don't see any errors in messages or dmesg output. >> >> From what I gathered from an older thread: >> https://marc.info/?l=bacula-devel&m=123237957307571&w=2 >> <https://marc.info/?l=bacula-devel&m=123237957307571&w=2> , this points >> that copying completed successfully. Also mentioned in the thread is >> that "Maximium Block Size" could be the problem, but we haven't defined >> that property. >> >> Does anyone know what could cause this? >> >> >> BR >> >> -- >> Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> >> |
|
From: Heitor F. <he...@ba...> - 2021-10-22 11:52:11
|
Just in time... >>> *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume data >>> error at 0:0! Short block of 42967 bytes on device "backup-device-data1" >>> (/data1) discarded. ** >>> **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682 >>> [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device >>> "backup-device-data1" (/data1) discarded. * > > IMHO Bacula is very straightforward when reading and writing volumes, so this is > probably an underlying issue. > I would try to retry the operation, while checking the dmesg for disk access > problems. Sorry about that. According to the following thread <https://sourceforge.net/p/bacula/mailman/message/36958416/> this is possibly a bug. I advise you to upgrade to the 11.0.5 with the packages from bacula.org, and verify if the problem persists. Regards, -- MSc Heitor Faria (Miami/USA) Bacula LATAM CEO mobile1: + 1 909 655-8971 mobile2: + 55 61 98268-4220 [ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] [ http://www.bacula.com.br/ ] América Latina [ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | bacula.com.br ] |
|
From: Heitor F. <he...@ba...> - 2021-10-22 11:43:45
|
Hello Marko, >> *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume data >> error at 0:0! Short block of 42967 bytes on device "backup-device-data1" >> (/data1) discarded. ** >> **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682 >> [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device >> "backup-device-data1" (/data1) discarded. * IMHO Bacula is very straightforward when reading and writing volumes, so this is probably an underlying issue. I would try to retry the operation, while checking the dmesg for disk access problems. Atte. -- MSc Heitor Faria (Miami/USA) Bacula LATAM CEO mobile1: + 1 909 655-8971 mobile2: + 55 61 98268-4220 [ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] [ http://www.bacula.com.br/ ] América Latina [ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | bacula.com.br ] |
|
From: Martin S. <ma...@li...> - 2021-10-22 11:19:03
|
Did the backup job on 03-Oct fill the disk? Did you check for syslog messages for that date too? Also, did you include the complete output below from the backup jobid 12068? I would expect more information to be printed between 03-Oct 23:06 and 03-Oct 23:19 about the volumes being used and the reason for changing from volume-10 to volume-11. __Martin >>>>> On Thu, 21 Oct 2021 16:27:13 +0200, Marko Bartolić said: > > Hello, > > I hope this is the right place to ask. > > We have Bacula version 9.6.5. on a RHEL 8.2 physical server. We use copy > job that runs every 6 months and copies the last full backup of 22 > clients to a separate SCSI disk which is then pulled out from the server > for offsite backup. So both the backup disks and disk on which the > backups are later copied are local, physical disks in the machine. This > was working fine every time up to now. During last run of the copy job, > we noticed the following error on one of the copy jobs: > > 21-Oct 04:00 backup-dir JobId 12612: Copying using JobId=12068 Job=websrv.2021-10-03_23.05.00_12 > 21-Oct 05:45 backup-dir JobId 12612: Start Copying JobId 12612, Job=Copy-to-offsite-disk.2021-10-21_04.00.01_36 > 21-Oct 05:45 backup-dir JobId 12612: Using Device "backup-device-data1" to read. > 21-Oct 05:45 backup-sd JobId 12612: Ready to read from volume "volume-10" on File device "backup-device-data1" (/data1). > 21-Oct 05:45 backup-sd JobId 12612: Forward spacing Volume "volume-10" to addr=641829209227 > *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. ** > **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. * > 21-Oct 05:46 backup-sd JobId 12612: End of Volume "volume-10" at addr=653197996032 on device "backup-device-data1" (/data1). > 21-Oct 05:46 backup-sd JobId 12612: Ready to read from volume "volume-11" on File device "backup-device-data1" (/data1). > 21-Oct 05:46 backup-sd JobId 12612: Forward spacing Volume "volume-11" to addr=64742 > 21-Oct 05:50 backup-sd JobId 12612: End of Volume "volume-11" at addr=49666111453 on device "backup-device-data1" (/data1). > 21-Oct 05:50 backup-sd JobId 12612: Elapsed time=00:05:02, Transfer rate=16.65 M Bytes/second > 21-Oct 05:50 backup-dir JobId 12612: Error: Bacula backup-dir 9.6.5 (11Jun20): > Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) > Prev Backup JobId: 12068 > Prev Backup Job: websrv.2021-10-03_23.05.00_12 > New Backup JobId: 12613 > Current JobId: 12612 > Current Job: Copy-to-offsite-disk.2021-10-21_04.00.01_36 > Backup Level: Full > Client: backup-fd > FileSet: "backup" 2020-09-17 21:53:08 > Read Pool: "Default" (From Command input) > Read Storage: "backup-storage-data1" (From Pool resource) > Write Pool: "Offsite" (From Command input) > Write Storage: "backup-storage-data2" (From Command input) > Catalog: "MyCatalog" (From Client resource) > Start time: 21-Oct-2021 05:45:32 > End time: 21-Oct-2021 05:50:42 > Elapsed time: 5 mins 10 secs > Priority: 10 > * SD Files Written: 200,038 ** > ** SD Bytes Written: 5,029,190,722 (5.029 GB) * > Rate: 16223.2 KB/s > Volume name(s): vol-01 > Volume Session Id: 5353 > Volume Session Time: 1619097903 > Last Volume Bytes: 573,628,844,941 (573.6 GB) > SD Errors: 1 > SD termination status: OK > Termination: *** Copying Error *** > > > > Job ends with error, but upon checking the backup size and number of > files of the original "websrv" backup job (which was successful), we see > that the number of files and bytes written are the same as is in the > copy job: > > 03-Oct 23:06 backup-dir JobId 12068: Start Backup JobId 12068, Job=websrv.2021-10-03_23.05.00_12 > 03-Oct 23:06 backup-dir JobId 12068: Using Device "backup-device-data1" to write. > 03-Oct 23:06 websrv-fd JobId 12068: shell command: run ClientBeforeJob "/etc/bacula/scripts/mariadb-backup.sh" > 03-Oct 23:10 websrv-fd JobId 12068: /srv/cpap is a different filesystem. Will not descend from / into it. > 03-Oct 23:19 backup-sd JobId 12068: Elapsed time=00:13:26, Transfer rate=6.239 M Bytes/second > 03-Oct 23:19 backup-sd JobId 12068: Sending spooled attrs to the Director. Despooling 53,043,158 bytes ... > 03-Oct 23:19 backup-dir JobId 12068: Bacula backup-dir 9.6.5 (11Jun20): > Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) > JobId: 12068 > Job: websrv.2021-10-03_23.05.00_12 > Backup Level: Full > Client: "websrv-fd" 9.0.6 (20Nov17) x86_64-redhat-linux-gnu,redhat,Enterprise 8.1 > FileSet: "websrv" 2020-09-17 23:05:00 > Pool: "Default" (From Job resource) > Catalog: "MyCatalog" (From Client resource) > Storage: "backup-storage-data1" (From Pool resource) > Scheduled time: 03-Oct-2021 23:05:00 > Start time: 03-Oct-2021 23:06:04 > End time: 03-Oct-2021 23:19:37 > Elapsed time: 13 mins 33 secs > Priority: 10 > *FD Files Written: 200,038 SD Files Written: 200,038 FD Bytes Written: > 4,996,564,202 (4.996 GB) SD Bytes Written: 5,029,190,722 (5.029 GB)* > Rate: 6145.8 KB/s > Software Compression: 40.9% 1.7:1 > Comm Line Compression: 16.7% 1.2:1 > Snapshot/VSS: no > Encryption: no > Accurate: no > Volume name(s): volume-10|volume-11 > Volume Session Id: 4812 > Volume Session Time: 1619097903 > Last Volume Bytes: 49,996,799,959 (49.99 GB) > Non-fatal FD errors: 0 > SD Errors: 0 > FD termination status: OK > SD termination status: OK > Termination: Backup OK > > 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Jobs older than 6 months . > 03-Oct 23:19 backup-dir JobId 12068: Pruned 1 Job for client websrv-fd from catalog. > 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Files. > 03-Oct 23:19 backup-dir JobId 12068: Pruned Files from 1 Jobs for client websrv-fd from catalog. > 03-Oct 23:19 backup-dir JobId 12068: End auto prune. > > > I also don't see any errors in messages or dmesg output. > > From what I gathered from an older thread: > https://marc.info/?l=bacula-devel&m=123237957307571&w=2 > <https://marc.info/?l=bacula-devel&m=123237957307571&w=2> , this points > that copying completed successfully. Also mentioned in the thread is > that "Maximium Block Size" could be the problem, but we haven't defined > that property. > > Does anyone know what could cause this? > > > BR > > -- > Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> > |
|
From: Marko B. <mar...@ni...> - 2021-10-21 14:42:58
|
Hello, I hope this is the right place to ask. We have Bacula version 9.6.5. on a RHEL 8.2 physical server. We use copy job that runs every 6 months and copies the last full backup of 22 clients to a separate SCSI disk which is then pulled out from the server for offsite backup. So both the backup disks and disk on which the backups are later copied are local, physical disks in the machine. This was working fine every time up to now. During last run of the copy job, we noticed the following error on one of the copy jobs: 21-Oct 04:00 backup-dir JobId 12612: Copying using JobId=12068 Job=websrv.2021-10-03_23.05.00_12 21-Oct 05:45 backup-dir JobId 12612: Start Copying JobId 12612, Job=Copy-to-offsite-disk.2021-10-21_04.00.01_36 21-Oct 05:45 backup-dir JobId 12612: Using Device "backup-device-data1" to read. 21-Oct 05:45 backup-sd JobId 12612: Ready to read from volume "volume-10" on File device "backup-device-data1" (/data1). 21-Oct 05:45 backup-sd JobId 12612: Forward spacing Volume "volume-10" to addr=641829209227 *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. ** **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682 [SE0208] Volume data error at 0:0! Short block of 42967 bytes on device "backup-device-data1" (/data1) discarded. * 21-Oct 05:46 backup-sd JobId 12612: End of Volume "volume-10" at addr=653197996032 on device "backup-device-data1" (/data1). 21-Oct 05:46 backup-sd JobId 12612: Ready to read from volume "volume-11" on File device "backup-device-data1" (/data1). 21-Oct 05:46 backup-sd JobId 12612: Forward spacing Volume "volume-11" to addr=64742 21-Oct 05:50 backup-sd JobId 12612: End of Volume "volume-11" at addr=49666111453 on device "backup-device-data1" (/data1). 21-Oct 05:50 backup-sd JobId 12612: Elapsed time=00:05:02, Transfer rate=16.65 M Bytes/second 21-Oct 05:50 backup-dir JobId 12612: Error: Bacula backup-dir 9.6.5 (11Jun20): Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) Prev Backup JobId: 12068 Prev Backup Job: websrv.2021-10-03_23.05.00_12 New Backup JobId: 12613 Current JobId: 12612 Current Job: Copy-to-offsite-disk.2021-10-21_04.00.01_36 Backup Level: Full Client: backup-fd FileSet: "backup" 2020-09-17 21:53:08 Read Pool: "Default" (From Command input) Read Storage: "backup-storage-data1" (From Pool resource) Write Pool: "Offsite" (From Command input) Write Storage: "backup-storage-data2" (From Command input) Catalog: "MyCatalog" (From Client resource) Start time: 21-Oct-2021 05:45:32 End time: 21-Oct-2021 05:50:42 Elapsed time: 5 mins 10 secs Priority: 10 * SD Files Written: 200,038 ** ** SD Bytes Written: 5,029,190,722 (5.029 GB) * Rate: 16223.2 KB/s Volume name(s): vol-01 Volume Session Id: 5353 Volume Session Time: 1619097903 Last Volume Bytes: 573,628,844,941 (573.6 GB) SD Errors: 1 SD termination status: OK Termination: *** Copying Error *** Job ends with error, but upon checking the backup size and number of files of the original "websrv" backup job (which was successful), we see that the number of files and bytes written are the same as is in the copy job: 03-Oct 23:06 backup-dir JobId 12068: Start Backup JobId 12068, Job=websrv.2021-10-03_23.05.00_12 03-Oct 23:06 backup-dir JobId 12068: Using Device "backup-device-data1" to write. 03-Oct 23:06 websrv-fd JobId 12068: shell command: run ClientBeforeJob "/etc/bacula/scripts/mariadb-backup.sh" 03-Oct 23:10 websrv-fd JobId 12068: /srv/cpap is a different filesystem. Will not descend from / into it. 03-Oct 23:19 backup-sd JobId 12068: Elapsed time=00:13:26, Transfer rate=6.239 M Bytes/second 03-Oct 23:19 backup-sd JobId 12068: Sending spooled attrs to the Director. Despooling 53,043,158 bytes ... 03-Oct 23:19 backup-dir JobId 12068: Bacula backup-dir 9.6.5 (11Jun20): Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) JobId: 12068 Job: websrv.2021-10-03_23.05.00_12 Backup Level: Full Client: "websrv-fd" 9.0.6 (20Nov17) x86_64-redhat-linux-gnu,redhat,Enterprise 8.1 FileSet: "websrv" 2020-09-17 23:05:00 Pool: "Default" (From Job resource) Catalog: "MyCatalog" (From Client resource) Storage: "backup-storage-data1" (From Pool resource) Scheduled time: 03-Oct-2021 23:05:00 Start time: 03-Oct-2021 23:06:04 End time: 03-Oct-2021 23:19:37 Elapsed time: 13 mins 33 secs Priority: 10 *FD Files Written: 200,038 SD Files Written: 200,038 FD Bytes Written: 4,996,564,202 (4.996 GB) SD Bytes Written: 5,029,190,722 (5.029 GB)* Rate: 6145.8 KB/s Software Compression: 40.9% 1.7:1 Comm Line Compression: 16.7% 1.2:1 Snapshot/VSS: no Encryption: no Accurate: no Volume name(s): volume-10|volume-11 Volume Session Id: 4812 Volume Session Time: 1619097903 Last Volume Bytes: 49,996,799,959 (49.99 GB) Non-fatal FD errors: 0 SD Errors: 0 FD termination status: OK SD termination status: OK Termination: Backup OK 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Jobs older than 6 months . 03-Oct 23:19 backup-dir JobId 12068: Pruned 1 Job for client websrv-fd from catalog. 03-Oct 23:19 backup-dir JobId 12068: Begin pruning Files. 03-Oct 23:19 backup-dir JobId 12068: Pruned Files from 1 Jobs for client websrv-fd from catalog. 03-Oct 23:19 backup-dir JobId 12068: End auto prune. I also don't see any errors in messages or dmesg output. From what I gathered from an older thread: https://marc.info/?l=bacula-devel&m=123237957307571&w=2 <https://marc.info/?l=bacula-devel&m=123237957307571&w=2> , this points that copying completed successfully. Also mentioned in the thread is that "Maximium Block Size" could be the problem, but we haven't defined that property. Does anyone know what could cause this? BR -- Marko Bartolić, Nimium d.o.o., email:<mar...@ni...> |
|
From: christopher t. <web...@fi...> - 2021-10-15 19:18:49
|
hello Im new to this list. I recently i noticed an issue with amazon S3 when Object Lock is enabled see issue 2643 <https://bugs.bacula.org/view.php?id=2643> and from that a related issue with the MD5 calculation in md5.c see issue 2644 <https://bugs.bacula.org/view.php?id=2644> i have possible fixes for both at https://github.com/firebladed/bacula/tree/firebladed-md5-patch-1 as no one has responded to the issues on bugs.bacula.org i joined this list Im wondering if there is anything else i need to consider for these fixes christopher tyerman |
|
From: Radosław K. <rad...@ko...> - 2021-10-13 08:55:43
|
Hello Dan, wt., 12 paź 2021 o 03:30 Dan Langille <da...@la...> napisał(a): > Radosław Korzeniewski wrote on 10/11/21 2:31 AM: > > Hello Dan, > > niedz., 10 paź 2021 o 22:40 Dan Langille <da...@la...> napisał(a): > >> > I'm happy to send in pull requests soon. >> My pull request is here:https://github.com/dlangille/bacula/pull/1 >> >> > Thanks for your patch. I have a question about it: Why did you remove > "debugging information" from regress/tests/runscript-test in one patch and > add it again in another? > > > I think you are reading the commits in reverse chronological order. > > OK, it is plausible. best regards -- Radosław Korzeniewski rad...@ko... |
|
From: Dan L. <da...@la...> - 2021-10-12 01:30:30
|
Radosław Korzeniewski wrote on 10/11/21 2:31 AM: > Hello Dan, > > niedz., 10 paź 2021 o 22:40 Dan Langille <da...@la... > <mailto:da...@la...>> napisał(a): > > > I'm happy to send in pull requests soon. > My pull request is here:https://github.com/dlangille/bacula/pull/1 > > > Thanks for your patch. I have a question about it: Why did you remove > "debugging information" from regress/tests/runscript-test in one patch > and add it again in another? I think you are reading the commits in reverse chronological order. The commits got added in during my first commit. They were there as part of the debugging I added. Then I removed them. > > I don't know how to create a pull request directly to the repo. > > > The main Bacula git repository is not managed by github or gitlab, so > I'm not sure if we can use pull requests directly (so correct me if > I'm wrong). But we can use your branch to manually pull commits from. Good. -- Dan Langille - da...@la... https://langille.org/ |
|
From: Eric B. <er...@ba...> - 2021-10-11 09:24:26
|
Hello Dan, Thanks for your pull request, sounds good to me, I will merge it soon. Best Regards, Eric On 10.10.21 22:39, Dan Langille wrote: > Dan Langille wrote on 10/5/21 11:21 AM: >> >> Dan Langille wrote: >>> >>> Hello, >>> >>> Is it time to update the regression tests from Python 2 to Python3? >>> >>> e.g. >>> >>> [pg14 dan ~/src/bacula/regress] % grep -r python2 * 14:25:49 >>> build/release/bgit.py:#!/usr/bin/env python2 >>> test_duration:#!/usr/bin/env python2 >>> ^C >>> >>> This is not a complete list. >>> >> >> >> I have started moving my regression testing hosts from 9.x to 11.x and I'm >> finding things which need improvement. >> >> Following on from this, I am finding other things which are breaking >> regression testing on non-Linux systems. >> >> The first: do not assume /bin/bash exists >> >> [pg14 dan ~/src/bacula/regress] % git diff >> scripts/cleanup 15:11:00 >> diff --git a/regress/scripts/cleanup b/regress/scripts/cleanup >> index 6cc332a16..fbeb28025 100755 >> --- a/regress/scripts/cleanup >> +++ b/regress/scripts/cleanup >> @@ -1,4 +1,4 @@ >> -#!/bin/bash >> +#!/usr/bin/env bash >> # >> # Copyright (C) 2000-2020 Kern Sibbald >> # License: BSD 2-Clause; see file LICENSE-FOSS >> [pg14 dan ~/src/bacula/regress] % 15:11:07 >> >> This same problem also affects regress/scripts/regress-utils.sh >> >> Next, do not assume /bin/bash is the bash you are using. On some systems, it >> is /usr/local/bin/bash. >> >> Deeper into regress/scripts/regress-utils.sh, is found: >> >> # now check if we are running under a proper shell >> if test "x$SHELL" != "x/bin/bash" >> then >> echo "Regression script must use BASH for this utilities!" >> exit 1 >> fi >> >> This will fail on my system for sure and others I'm sure. I think for two >> reasons: >> >> 1 - $SHELL is an environment variable - it is not the shell running this script >> 2 - bash is not always /bin/bash >> >> Must I be running the bash shell to invoke regression testing? If so, why? >> >> Regression testing is vital to the project. At present, regression will work >> only on a limited number of operating systems. >> >> I'm hoping we can change that soon. >> >> I'm happy to send in pull requests soon. > My pull request is here:https://github.com/dlangille/bacula/pull/1 > > I don't know how to create a pull request directly to the repo. > > Always happy to have my commit bit restored. It went away when the repo was > moved to git. > > Thank you. > |
|
From: Radosław K. <rad...@ko...> - 2021-10-11 06:32:10
|
Hello Dan, niedz., 10 paź 2021 o 22:40 Dan Langille <da...@la...> napisał(a): > > I'm happy to send in pull requests soon. > My pull request is here:https://github.com/dlangille/bacula/pull/1 > > Thanks for your patch. I have a question about it: Why did you remove "debugging information" from regress/tests/runscript-test in one patch and add it again in another? I don't know how to create a pull request directly to the repo. > The main Bacula git repository is not managed by github or gitlab, so I'm not sure if we can use pull requests directly (so correct me if I'm wrong). But we can use your branch to manually pull commits from. best regards -- Radosław Korzeniewski rad...@ko... |
|
From: Dan L. <da...@la...> - 2021-10-10 20:39:35
|
Dan Langille wrote on 10/5/21 11:21 AM: > > Dan Langille wrote: >> >> Hello, >> >> Is it time to update the regression tests from Python 2 to Python3? >> >> e.g. >> >> [pg14 dan ~/src/bacula/regress] % grep -r python2 * 14:25:49 >> build/release/bgit.py:#!/usr/bin/env python2 >> test_duration:#!/usr/bin/env python2 >> ^C >> >> This is not a complete list. >> > > > I have started moving my regression testing hosts from 9.x to 11.x and > I'm finding things which need improvement. > > Following on from this, I am finding other things which are breaking > regression testing on non-Linux systems. > > The first: do not assume /bin/bash exists > > [pg14 dan ~/src/bacula/regress] % git diff > scripts/cleanup 15:11:00 > diff --git a/regress/scripts/cleanup b/regress/scripts/cleanup > index 6cc332a16..fbeb28025 100755 > --- a/regress/scripts/cleanup > +++ b/regress/scripts/cleanup > @@ -1,4 +1,4 @@ > -#!/bin/bash > +#!/usr/bin/env bash > # > # Copyright (C) 2000-2020 Kern Sibbald > # License: BSD 2-Clause; see file LICENSE-FOSS > [pg14 dan ~/src/bacula/regress] % 15:11:07 > > This same problem also affects regress/scripts/regress-utils.sh > > Next, do not assume /bin/bash is the bash you are using. On some > systems, it is /usr/local/bin/bash. > > Deeper into regress/scripts/regress-utils.sh, is found: > > # now check if we are running under a proper shell > if test "x$SHELL" != "x/bin/bash" > then > echo "Regression script must use BASH for this utilities!" > exit 1 > fi > > This will fail on my system for sure and others I'm sure. I think for > two reasons: > > 1 - $SHELL is an environment variable - it is not the shell running > this script > 2 - bash is not always /bin/bash > > Must I be running the bash shell to invoke regression testing? If so, why? > > Regression testing is vital to the project. At present, regression > will work only on a limited number of operating systems. > > I'm hoping we can change that soon. > > I'm happy to send in pull requests soon. My pull request is here:https://github.com/dlangille/bacula/pull/1 I don't know how to create a pull request directly to the repo. Always happy to have my commit bit restored. It went away when the repo was moved to git. Thank you. -- Dan Langille - da...@la... https://langille.org/ |
|
From: Martin S. <ma...@li...> - 2021-10-07 13:52:35
|
>>>>> On Wed, 6 Oct 2021 16:40:14 -0400, Dan Langille said: > > Martin Simmons wrote on 10/6/21 3:39 PM: > >>>>>> On Tue, 5 Oct 2021 11:21:46 -0400, Dan Langille said: > >> Must I be running the bash shell to invoke regression testing? > > You don't have to be running bash yourself -- the #! makes it run bash. > > Yes, but $SHELL is not necessary the shell currently executing. It is an > environment variable: > > [pro02 dan ~] % echo $SHELL 16:38:28 > /bin/zsh > [pro02 dan ~] % bash 16:38:32 > [dan@pro02:~] $ echo $SHELL > /bin/zsh Oops :-( __Martin |
|
From: Dan L. <da...@la...> - 2021-10-06 20:40:27
|
Martin Simmons wrote on 10/6/21 3:39 PM:
>>>>>> On Tue, 5 Oct 2021 11:21:46 -0400, Dan Langille said:
>> Must I be running the bash shell to invoke regression testing?
> You don't have to be running bash yourself -- the #! makes it run bash.
Yes, but $SHELL is not necessary the shell currently executing. It is an
environment variable:
[pro02 dan ~] % echo $SHELL 16:38:28
/bin/zsh
[pro02 dan ~] % bash 16:38:32
[dan@pro02:~] $ echo $SHELL
/bin/zsh
>
>> If so, why?
> It is because the script uses some bash extensions. Two that I can see are
>
> ((JOBID++))
>
> and
>
> ERRS=$((`grep "joberrors: " ${tmp}/blog${ltest}.out | awk '{print $2}'`+0))
>
I'm not asking why the script requires bash. My answer above shows why.
--
Dan Langille
da...@la... : https://langille.org/
|
|
From: Martin S. <ma...@li...> - 2021-10-06 19:39:53
|
>>>>> On Tue, 5 Oct 2021 11:21:46 -0400, Dan Langille said:
>
> Must I be running the bash shell to invoke regression testing?
You don't have to be running bash yourself -- the #! makes it run bash.
> If so, why?
It is because the script uses some bash extensions. Two that I can see are
((JOBID++))
and
ERRS=$((`grep "joberrors: " ${tmp}/blog${ltest}.out | awk '{print $2}'`+0))
__Martin
|
|
From: Radosław K. <rad...@ko...> - 2021-10-05 17:43:01
|
Hello, wt., 5 paź 2021 o 18:34 Radosław Korzeniewski <rad...@ko...> napisał(a): > Hello Dan, > > wt., 5 paź 2021 o 17:41 Dan Langille <da...@la...> napisał(a): > >> >> Dan Langille wrote: >> >> >> Hello, >> >> Is it time to update the regression tests from Python 2 to Python3? >> >> e.g. >> >> [pg14 dan ~/src/bacula/regress] % grep -r python2 * 14:25:49 >> build/release/bgit.py:#!/usr/bin/env python2 >> test_duration:#!/usr/bin/env python2 >> ^C >> >> This is not a complete list. >> >> >> >> I have started moving my regression testing hosts from 9.x to 11.x and >> I'm finding things which need improvement. >> >> Following on from this, I am finding other things which are breaking >> regression testing on non-Linux systems. >> >> The first: do not assume /bin/bash exists >> >> [pg14 dan ~/src/bacula/regress] % git diff >> scripts/cleanup 15:11:00 >> diff --git a/regress/scripts/cleanup b/regress/scripts/cleanup >> index 6cc332a16..fbeb28025 100755 >> --- a/regress/scripts/cleanup >> +++ b/regress/scripts/cleanup >> @@ -1,4 +1,4 @@ >> -#!/bin/bash >> +#!/usr/bin/env bash >> # >> # Copyright (C) 2000-2020 Kern Sibbald >> # License: BSD 2-Clause; see file LICENSE-FOSS >> [pg14 dan ~/src/bacula/regress] >> % 15:11:07 >> >> This same problem also affects regress/scripts/regress-utils.sh >> >> Next, do not assume /bin/bash is the bash you are using. On some systems, >> it is /usr/local/bin/bash. >> >> Deeper into regress/scripts/regress-utils.sh, is found: >> >> # now check if we are running under a proper shell >> if test "x$SHELL" != "x/bin/bash" >> then >> echo "Regression script must use BASH for this utilities!" >> exit 1 >> fi >> >> This will fail on my system for sure and others I'm sure. I think for >> two reasons: >> >> 1 - $SHELL is an environment variable - it is not the shell running this >> script >> > > For bash it is a shell running the script. > I was wrong about the above statements. Do not take it in the discussion. Sorry. -- Radosław Korzeniewski rad...@ko... |
|
From: Radosław K. <rad...@ko...> - 2021-10-05 17:06:47
|
Hello Dan, wt., 5 paź 2021 o 17:41 Dan Langille <da...@la...> napisał(a): > > Dan Langille wrote: > > > Hello, > > Is it time to update the regression tests from Python 2 to Python3? > > e.g. > > [pg14 dan ~/src/bacula/regress] % grep -r python2 * 14:25:49 > build/release/bgit.py:#!/usr/bin/env python2 > test_duration:#!/usr/bin/env python2 > ^C > > This is not a complete list. > > > > I have started moving my regression testing hosts from 9.x to 11.x and I'm > finding things which need improvement. > > Following on from this, I am finding other things which are breaking > regression testing on non-Linux systems. > > The first: do not assume /bin/bash exists > > [pg14 dan ~/src/bacula/regress] % git diff > scripts/cleanup 15:11:00 > diff --git a/regress/scripts/cleanup b/regress/scripts/cleanup > index 6cc332a16..fbeb28025 100755 > --- a/regress/scripts/cleanup > +++ b/regress/scripts/cleanup > @@ -1,4 +1,4 @@ > -#!/bin/bash > +#!/usr/bin/env bash > # > # Copyright (C) 2000-2020 Kern Sibbald > # License: BSD 2-Clause; see file LICENSE-FOSS > [pg14 dan ~/src/bacula/regress] > % 15:11:07 > > This same problem also affects regress/scripts/regress-utils.sh > > Next, do not assume /bin/bash is the bash you are using. On some systems, > it is /usr/local/bin/bash. > > Deeper into regress/scripts/regress-utils.sh, is found: > > # now check if we are running under a proper shell > if test "x$SHELL" != "x/bin/bash" > then > echo "Regression script must use BASH for this utilities!" > exit 1 > fi > > This will fail on my system for sure and others I'm sure. I think for two > reasons: > > 1 - $SHELL is an environment variable - it is not the shell running this > script > For bash it is a shell running the script. > 2 - bash is not always /bin/bash > ??? > > Must I be running the bash shell to invoke regression testing? If so, why? > I do not understand your question. Regression testing requires some special configuration of the system where you perform tests and are not expected to be executed on the production system or distributed with the package manager of your choice. So if you want to perform regression testing you have to correctly setup your environment, right? It is not a secret that the main Bacula development is done on Linux systems, so the regressions. > Regression testing is vital to the project. At present, regression will > work only on a limited number of operating systems. > As long as regression testing will be the mix of shell (different brands), perl, sed, awk and python scripts then it won't change. A few years ago regression tests won't run when the source directory name contains a dot. :) I'm hoping we can change that soon. > I'm happy to send in pull requests soon. > Great! Can't wait! best regards -- Radosław Korzeniewski rad...@ko... |
|
From: Dan L. <da...@la...> - 2021-10-05 15:41:14
|
Dan Langille wrote: > > Hello, > > Is it time to update the regression tests from Python 2 to Python3? > > e.g. > > [pg14 dan ~/src/bacula/regress] % grep -r python2 * 14:25:49 > build/release/bgit.py:#!/usr/bin/env python2 > test_duration:#!/usr/bin/env python2 > ^C > > This is not a complete list. > I have started moving my regression testing hosts from 9.x to 11.x and I'm finding things which need improvement. Following on from this, I am finding other things which are breaking regression testing on non-Linux systems. The first: do not assume /bin/bash exists [pg14 dan ~/src/bacula/regress] % git diff scripts/cleanup 15:11:00 diff --git a/regress/scripts/cleanup b/regress/scripts/cleanup index 6cc332a16..fbeb28025 100755 --- a/regress/scripts/cleanup +++ b/regress/scripts/cleanup @@ -1,4 +1,4 @@ -#!/bin/bash +#!/usr/bin/env bash # # Copyright (C) 2000-2020 Kern Sibbald # License: BSD 2-Clause; see file LICENSE-FOSS [pg14 dan ~/src/bacula/regress] % 15:11:07 This same problem also affects regress/scripts/regress-utils.sh Next, do not assume /bin/bash is the bash you are using. On some systems, it is /usr/local/bin/bash. Deeper into regress/scripts/regress-utils.sh, is found: # now check if we are running under a proper shell if test "x$SHELL" != "x/bin/bash" then echo "Regression script must use BASH for this utilities!" exit 1 fi This will fail on my system for sure and others I'm sure. I think for two reasons: 1 - $SHELL is an environment variable - it is not the shell running this script 2 - bash is not always /bin/bash Must I be running the bash shell to invoke regression testing? If so, why? Regression testing is vital to the project. At present, regression will work only on a limited number of operating systems. I'm hoping we can change that soon. I'm happy to send in pull requests soon. |
|
From: Dan L. <da...@la...> - 2021-10-03 14:45:58
|
Hello, Is it time to update the regression tests from Python 2 to Python3? e.g. [pg14 dan ~/src/bacula/regress] % grep -r python2 * 14:25:49 build/release/bgit.py:#!/usr/bin/env python2 test_duration:#!/usr/bin/env python2 ^C This is not a complete list. -- Dan Langille - da...@la... https://langille.org/ |