You can use automated anti-virus software. That is why I went looking for a way to search and delete all 0 Byte files in a single go. In my case it concerned dozens of files in even more folders. type f -size 0 -delete The -type f option makes sure that we are working on a regular file and not on directories or other special files. exe files or programs turned into 0 bytes, the biggest reason is that the 0KB virus infected your files. This approach works fine if you only need to go through a reasonable amount of files and folders. cd /path/to/directory/to/delete/files find. Here we are again: Following some older forum topics I really wished I din’t need to empty my whole trash for this step but only the corrupted files involved. To delete all zero byte files in the current directory and sub-directories, use the following find command syntax. To get the sync finally running again I needed to delete the zero byte files AND empty them from the trash. I can’t find any corresponding change in the latest webdav release so I wonder if there might have been changes in DT that it suddenly has a case sensitive problem. I am syncing to my Synology webdav and this was working for severals years without any changes. I turned out that the path had a wrong case sensitive character. Why is that a problem only now and only on one device ?Īs mentioned I’ve had some sync issues as well - the error was “forbidden” on all my MacOS and iOS devices. Some very simple formats do not use metadata, such as ASCII text files these may validly be zero bytes (a common convention terminates text files with a one. But my MacBook also holds the same zero byte files and never complained about that. I did some research in my time machine and these files seem to be zero bytes since several years. I’ve identified the zero byte files on my iMac. However, I took the journey of resolving the sync and corrupted database problems yesterday and I want to understand what was going on there. I haven’t followed all in details as I had other stuff to focus on - so perhaps the problems are not related to each other.
Some time later my DT on iMac also complained a corrupted database (in addition I’ve had 2 power crashes, so I don’t know if its related to DTTG). So even if the file has zero data, the file system can deal with it quite easily by allocating storage for the metadata, but zero storage for the data. It doesnt affect performance (as far as I know), but is just annoying that they are there at all. After upgrading to DTTG 3 I’ve had several issues with corrupted files / database. I have several files on my desktop that are greyed-out that I cant delete in any of the normal techniques.