This error may appear in course of syncing. It means that there's not enough space on the logical drive where this job is configured to be syncing.
An Agent will try to allocate all the available storage, thus the error pops up when there's indeed no more space left. This may affect other applications that rely on this drive.
NoteImportant note: on pre-seeded folders, when downloading a patched file, the Agent will reserve twice as much space for it, since the patched file will be downloaded into the .sync subdirectory and then moved to its proper place.
Apart from the obvious reason - small storage size, lack of space can also be affected by the Archive. Agents keep files' versions in .sync/Archive directory, which will also take some space. If necessary clear it manually and change its settings to store the files for fewer days.
If some space is cleared, the Agent will automatically resume syncing (in Sync job) or continue the job run (Consolidation or Distribution jobs) provided the job run itself hasn't aborted or timed out yet.
It's possible to configure the moment when the error is triggered and disallow the Agent to take up all the storage. Add either of the two custom parameters to the Agent profile and restart the Agent:
disk_min_free_space_gb. Value is in Gigabytes (example: 1 for 1 Gb). It's the offset to the storage total space. It means that once there are that many Gigabytes of free space (or less) remaining on the drive, the Agent will give an error.
disk_min_free_space. Value is in percentage (example: 10 for 10%). Calculation of free space remaining on the drive. Once the stated percentage (or less) of disk space reached, the Agent will give an error.