Is the whole vault gone when a Google Drive directory doesn't sync?

I created a Vault in my Google Drive (synced with DriveFS), and uploaded 1TB. It was working fine. Then I tried copying in some more files, but Google Drive gave me an error that it couldn’t upload them (I think my internet dropped).

Now when I run a Vault health check, it notifies me that one of the directories is empty. It’s marked “unfixable”. Now, when if I try to copy new files, the copy command freezes–I have to reboot. The log shows this:

o.c.c.dir.BrokenDirectoryFilter - Broken directory file: … w==.c9r\dir.c9r
java.io.IOException: Invalid, empty directory file:

I can’t copy, read or delete files or folders any more due to this missing folder. I’ve read many posts on the forum, and one says there’s no option, but there’s an issue tracker, which states the issue was solved: Corrupted directories - "Unexpectedly large directory file"

But I’m using the current version and the repair/health feature still says this missing directory is ‘unfixable’, and the Vault appears to be broken as a result. Does this mean I lose 1TB of files because 1 directory failed to upload? Or did the fix get moved somewhere else?

Hi,
I know there are others that have gotten Google Desktop to work for synchronizing vaults but I don’t know if any of them have such a large vault.

I don’t know if your data is recoverable that is not my area of expertise.
Of having an error like this diminishes greatly if you mount the Google Drive without synchronization. Let the software access the Google drive directly and the stability goes up for some people especially if you have a very large vault.

Someone else will have to chime in and see if they know a way for you to recover the data that you can’t get to.

I would recommend mounting Google Drive and seeing if your vault is accessible that way. That’s the only thing I can think of.