View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001426 | bareos-core | director | public | 2022-02-07 10:37 | 2024-05-15 15:52 |
| Reporter | mschiff | Assigned To | stephand | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | suspended | ||
| Platform | Linux | OS | any | OS Version | 3 |
| Product Version | 21.0.0 | ||||
| Summary | 0001426: bareos send useless operator "mount" messages | ||||
| Description | The default configuration has messages/Standard.conf which contains: operator = <email> = mount which shouldsend an email if an operator is required for a job to continue. But these mails will also be triggered on a busy bareos-sd with multiple virtual drives and multiple jobs running, when a job just needs to wait a bit for a volume to become available. Every month, when our systems are doing virtual full backups at night, we get lots of mails like: 06-Feb 23:37 kilo-sd JobId 58793: Please mount read Volume "VolIncr-0034" for: Job: BackupIndia.2022-02-06_23.15.01_31 Storage: "MultiFileStorage0001" (/srv/backup/bareos) Pool: Incr Media type: File But in the morning, all jobs are finished successsfully. So when one job is reading a volume and another job is waiting for the same volume, an email is triggered. But after waiting a couple of minutes, this "issue" solves itself. It should be possible to set some timeout, after which such messages are being sent, so that they will only be sent on really hanging jobs. This is part of the joblog: 2022-02-06 23:25:38 kilo-dir JobId 58793: Start Virtual Backup JobId 58793, Job=BackupIndia.2022-02-06_23.15.01_31 2022-02-06 23:25:38 kilo-dir JobId 58793: Consolidating JobIds 58147,58164,58182,58200,58218,58236,58254,58272,58290,58308,58326,58344,58362,58380,58398,58416,58434,58452,58470,58488,58506 ,58524,58542,58560,58578,58596,58614,58632,58650,58668,58686,58704,58722,58740,58758,58764 2022-02-06 23:25:40 kilo-dir JobId 58793: Bootstrap records written to /var/lib/bareos/kilo-dir.restore.16.bsr 2022-02-06 23:25:40 kilo-dir JobId 58793: Connected Storage daemon at kilo.sys4.de:9103, encryption: TLS_AES_256_GCM_SHA384 TLSv1.3 2022-02-06 23:26:42 kilo-dir JobId 58793: Using Device "MultiFileStorage0001" to read. 2022-02-06 23:26:42 kilo-dir JobId 58793: Using Device "MultiFileStorage0002" to write. 2022-02-06 23:26:42 kilo-sd JobId 58793: Ready to read from volume "VolFull-0165" on device "MultiFileStorage0001" (/srv/backup/bareos). 2022-02-06 23:26:42 kilo-sd JobId 58793: Forward spacing Volume "VolFull-0165" to file:block 0:3367481982. 2022-02-06 23:26:53 kilo-sd JobId 58793: End of Volume at file 1 on device "MultiFileStorage0001" (/srv/backup/bareos), Volume "VolFull-0165" 2022-02-06 23:26:53 kilo-sd JobId 58793: Ready to read from volume "VolFull-0168" on device "MultiFileStorage0001" (/srv/backup/bareos). 2022-02-06 23:26:53 kilo-sd JobId 58793: Forward spacing Volume "VolFull-0168" to file:block 2:1033779909. 2022-02-06 23:26:54 kilo-sd JobId 58793: End of Volume at file 2 on device "MultiFileStorage0001" (/srv/backup/bareos), Volume "VolFull-0168" 2022-02-06 23:26:54 kilo-sd JobId 58793: Ready to read from volume "VolFull-0169" on device "MultiFileStorage0001" (/srv/backup/bareos). 2022-02-06 23:26:54 kilo-sd JobId 58793: Forward spacing Volume "VolFull-0169" to file:block 0:64702. 2022-02-06 23:27:03 kilo-sd JobId 58793: End of Volume at file 1 on device "MultiFileStorage0001" (/srv/backup/bareos), Volume "VolFull-0169" 2022-02-06 23:27:03 kilo-sd JobId 58793: Warning: stored/vol_mgr.cc:542 Need volume from other drive, but swap not possible. Status: read=1 num_writers=0 num_reserve=0 swap=0 vol=VolIncr-0 022 from dev="MultiFileStorage0004" (/srv/backup/bareos) to "MultiFileStorage0001" (/srv/backup/bareos) 2022-02-06 23:27:03 kilo-sd JobId 58793: Warning: stored/acquire.cc:348 Read acquire: stored/label.cc:268 Could not reserve volume VolIncr-0022 on "MultiFileStorage0001" (/srv/backup/bareo s) 2022-02-06 23:27:03 kilo-sd JobId 58793: Please mount read Volume "VolIncr-0022" for: Job: BackupIndia.2022-02-06_23.15.01_31 Storage: "MultiFileStorage0001" (/srv/backup/bareos) Pool: Incr Media type: File 2022-02-06 23:32:03 kilo-sd JobId 58793: Ready to read from volume "VolIncr-0022" on device "MultiFileStorage0001" (/srv/backup/bareos). 2022-02-06 23:32:03 kilo-sd JobId 58793: Forward spacing Volume "VolIncr-0022" to file:block 0:3331542115. 2022-02-06 23:32:03 kilo-sd JobId 58793: End of Volume at file 0 on device "MultiFileStorage0001" (/srv/backup/bareos), Volume "VolIncr-0022" 2022-02-06 23:32:03 kilo-sd JobId 58793: Ready to read from volume "VolIncr-0023" on device "MultiFileStorage0001" (/srv/backup/bareos). 2022-02-06 23:32:03 kilo-sd JobId 58793: Forward spacing Volume "VolIncr-0023" to file:block 0:750086502. | ||||
| Tags | No tags attached. | ||||
 |
Thanks for reporting this issue. I also already noticed that problem. It will be very hard to fix this properly without a complete redesign of the whole reservation logic, which would be a huge effort. But meanwhile we could think about a workaround to mitigate this somehow. |
|
|
related to internal task 5574 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-02-07 10:37 | mschiff | New Issue | |
| 2022-02-24 11:46 | stephand | Assigned To | => stephand |
| 2022-02-24 11:46 | stephand | Status | new => acknowledged |
| 2022-02-24 11:46 | stephand | Note Added: 0004526 | |
| 2024-03-20 14:38 | bruno-at-bareos | Note Added: 0005854 | |
| 2024-05-15 15:52 | arogge | Status | acknowledged => closed |
| 2024-05-15 15:52 | arogge | Resolution | open => suspended |
