Since my upgrade to 2.5.30 on Linux the FULL backup always failes! Before the upgrade it never come up with that.
SERVER231: Loading file list…
Info
15.04.23 04:24
SERVER231: Started loading files…
Fehler
15.04.23 09:21
Error writing file metadata -1
Fehler
15.04.23 09:40
Error writing file metadata -1
Info
16.04.23 20:39
Waiting for file transfers…
Info
16.04.23 20:46
Waiting for file hashing and copying threads…
Warnungen
16.04.23 20:47
Not all folder metadata could be applied. Metadata was inconsistent.
Info
16.04.23 20:47
Writing new file list…
Info
16.04.23 20:48
All metadata was present
Info
16.04.23 20:48
Transferred 1.96597 TB - Average speed: 118.98 MBit/s
Fehler
16.04.23 20:48
FATAL: Backup failed because of disk problems (see previous messages)
The problem is it starts a FULL backup again next weekend and ends with the same message!
I had the same problem. Could not find any problems with the disk, I reformatted several times to try Ext 3, 4 and BTRFS and swapped disk . My only solution was to revert back to the previous version of Urbackup. 2.4.15, no problems reported since. Of course doing this means the you need to clear out the current back up as they are not compatible.
I did change the config from warn to debug, now have to wait till next week for full backup because this weekend is already to short on time for a full one.
i see this in the debug log:
2023-04-29 07:40:54: Starting HTTP-Server on port 55414
2023-04-29 07:40:54: HTTP: Server started up successfully!
2023-04-29 07:40:56: SQLite: recovered 15137 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2023-04-29 07:41:11: SQLite: recovered 140731 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2023-04-29 07:41:11: SQLite: recovered 4880 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2023-04-29 07:41:12: SQLite: recovered 26220 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283
2023-04-29 07:41:12: SQLite: recovered 3 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2023-04-29 07:41:12: SQLite: recovered 15137 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2023-04-29 07:41:12: SQLite: recovered 3 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2023-04-29 07:41:13: SQLite: recovered 140731 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2023-04-29 07:41:13: SQLite: recovered 26220 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283
2023-04-29 07:41:13: SQLite: recovered 4880 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2023-04-29 07:41:13: Started UrBackup…
2023-04-29 07:41:13: Removing temporary files…
2023-04-29 07:41:13: Recreating temporary folder…
2023-04-29 07:41:14: Testing if backup destination can handle subvolumes and snapshots…
2023-04-29 07:41:14: InternetService: Server started up successfully!
2023-04-29 07:41:14: UrBackup Server start up complete.
2023-04-29 07:41:14: Looking for old Sessions… 0 sessions
2023-04-29 07:41:14: Server started up successfully!
Should i be concerned about the recovery things going on?
I did check the client versions, the servers with Client Version 2.4.11 not make problems, the server witch i did upgrade to 2.5.23 when i made the upgrade to server 2.5.30 are the one with problems. Maybe it is the Client? Deleting the Backups is no option!
