# File System Warnings from backup jobs

**URL:** <https://forum.duplicati.com/t/file-system-warnings-from-backup-jobs/18730>\
**Category:** Support\
**Created:** [July 22, 2024, 2:20pm UTC](https://forum.duplicati.com/t/file-system-warnings-from-backup-jobs/18730 "2024-07-22T14:20:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kenkendk](https://forum.duplicati.com/user_avatar/forum.duplicati.com/kenkendk/32/5305_2.png) [@kenkendk](https://forum.duplicati.com/u/kenkendk)\
**Post date:** [July 29, 2024, 6:39am UTC](https://forum.duplicati.com/t/file-system-warnings-from-backup-jobs/18730/2 "2024-07-29T06:39:18Z")

</div>

> [@Richard\_DeVito\_Jr](#):
>
> I think there is a bug in the enumeration routines on this platform. Maybe it needs to be able to look at extended file status when reading network drives?

From Duplicati’s perspective, the mounted folders are “local” and it is treated this way, so no extra logic accounts for transient errors, and no timeouts are managed by Duplicati. It just opens the file and starts reading. Any delay or special cases should be handled by the OS.

I guess we could retry files that are not accessible, but do you have any suggestions? Have you seen another way of dealing with such errors in another application?

---

_[View the full topic](https://forum.duplicati.com/t/file-system-warnings-from-backup-jobs/18730)._