Syncing file system failed. Backup is not completely on disk. Invalid argument (code: 22)

Ubuntu 18.04 guest on VMWare host, backing up Windows 2008R2 and 2012 servers. Backups are to removable drive, formatted NTFS. Everything updated to 2.4.8 over the weekend, and now I get (after an apparently otherwise successful backup) the error above Syncing file system failed. Backup is not completely on disk. Invalid argument (code: 22)

How can I debug / resolve this error? Thanks!

I have a same error when start full or incremental backup.
Using Urbackup in docker container, started as described here:
https://www.urbackup.org/download.html#server_docker.

My docker start command:

docker run -d
–name urbackup-server
–restart=always
-v /mnt/toshiba2tb/urbackup/backups:/backups
-v /mnt/toshiba2tb/urbackup/database:/var/urbackup
-p 55413-55415:55413-55415
uroni/urbackup-server

2.3.8 version works fine, but yesterday i was update container to image with version 2.4.9, my commands:

docker rm -f urbackup-server
docker pull uroni/urbackup-server
… and same command as above

Two Windows 7 64bit machines with clients installed provide backups to server 2.3.8, but cannot work with 2.4.9. It log the same error as thread header.

Docker container starting in CentOS 7, volume ‘/mnt/toshiba2tb’ is linked to HDD 2Tb with one NTFS-partition.

How can i fix this error?
Or how can i downgrade Docker image to 2.3.8? It is only ‘latest’ tag i found here:
https://hub.docker.com/r/uroni/urbackup-server/tags

Post the full error please. Including error code. Is it invalid argument as well?

Level Time Message
Info 10/22/19 12:18 Starting scheduled full file backup…
Warnings 10/22/19 13:30 Restarting shadow copy of E:\ because it was started by this server
Info 10/22/19 13:30 Indexing of “COMMON” done. 595 filesystem lookups 0 db lookups and 0 db updates
Info 10/22/19 13:30 Indexing of “PROGRAMS” done. 120287 filesystem lookups 0 db lookups and 0 db updates
Info 10/22/19 13:30 Indexing of “USERS” done. 28352 filesystem lookups 0 db lookups and 0 db updates
Info 10/22/19 13:30 FS01: Loading file list…
Info 10/22/19 13:30 FS01: Started loading files…
Info 10/22/19 13:30 Waiting for file transfers…
Info 10/22/19 13:30 Waiting for file hashing and copying threads…
Info 10/22/19 13:30 Writing new file list…
Info 10/22/19 13:30 All metadata was present
Errors 10/22/19 13:30 Syncing file system failed. Backup is not completely on disk. Invalid argument (code: 22)
Info 10/22/19 13:30 Transferred 190.129 KB - Average speed: 6.23014 MBit/s
Info 10/22/19 13:30 Time taken for backing up client FS01: 1h 12m 20s
Errors 10/22/19 13:30 Backup failed

Thanks, but that was @lanmaster :).

I noticed that you are both using ntfs on Linux. Are you using it with ntfs-3g or something else?

ntfs-3g is correct

Full error string:

Syncing file system failed. Backup is not completely on disk. Invalid argument (code: 22)

Yes, using ntfs-3g

I have this exact same issue. Started Monday after an upgrade of a linux box and upgrade of UR product (client and server). Also using ntfs-3g version 2017.3.23.11.el7 (upgraded from 2017.3.23-6.el7).

Same error:
2019.10.22 23:26:59(error): Syncing file system failed. Backup is not completely on disk. Invalid argument (code: 22)

My environment consists of thus:
- Server: CentOS 7.7.1908 (just upgraded from 7.6) running URBackup 2.4.9 (just upgraded from 2.3.8).
- Clients:
CentOS 7.7.1908 (just upgraded from 7.6) running URBackup client 2.4.8 (just upgraded from 2.3.4)
Server 2012R2 running URClient 2.4.8 (also just upgraded from 2.3.4)
Server 2019 running URClient 2.4.8 (also just upgraded for 2.3.4)

A lot of moving parts for troubleshooting, but I figure the more information the better.

Thank you for any and all assistance… and being new to the forum, thank you for the fantastic product and it’s availability. It has saved me some hard $$$ and some even harder conversations with my administration and advisory committee.

I have the same problem with the new versions - 2.4.9 on server and 2.4.8 on client.

OS on server and client:
Raspbian GNU/Linux 9.11 (stretch)
Linux version 4.19.66-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1253 SMP Thu Aug 15 11:49:46 BST 2019

Backup storage:
HDD 5TB with one NTFS-Partition

Log:

Info 25.10.19 20:50 Starting unscheduled full file backup…
Info 25.10.19 20:50 Backing up “sys_home” without snapshot.
Info 25.10.19 20:50 Indexing of “sys_home” done. 13 filesystem lookups 0 db lookups and 0 db updates
Info 25.10.19 20:50 RASPBERRYFIX: Loading file list…
Info 25.10.19 20:50 RASPBERRYFIX: Started loading files…
Info 25.10.19 20:50 Referencing snapshot on “RASPBERRYFIX” for path “sys_home” failed: FAILED
Info 25.10.19 20:50 Waiting for file transfers…
Info 25.10.19 20:51 mariadbdump.sql: Starting backup of MariaDB at Fri Oct 25 20:51:09 CEST 2019…
Info 25.10.19 20:51 mariadbdump.sql: Backup of MariaDB finished at Fri Oct 25 20:51:20 CEST 2019.
Info 25.10.19 20:51 Waiting for file hashing and copying threads…
Info 25.10.19 20:52 Writing new file list…
Info 25.10.19 20:52 All metadata was present
Errors 25.10.19 20:52 Syncing file system failed. Backup is not completely on disk. Invalid argument (code: 22)
Info 25.10.19 20:52 Transferred 379.108 MB - Average speed: 76.388 MBit/s
Info 25.10.19 20:52 Time taken for backing up client RASPBERRYFIX: 1m 50s
Errors 25.10.19 20:52 Backup failed

How can i fix this problem?

Server version 2.4.10 should fix this issue

Sorry for the delay in response - waiting for backups to complete. Can confirm the error is resolved. Thanks!