FIles 0 bytes after opened

[mvv_vmd]

@tflidd

The ultimate pointer would be if you can reliably reproduce the issue (then it is certainly a candidate for a bug report at Issues · nextcloud/server · GitHub).

Isolating issues won’t be easy I guess.

Thanks for your reply, I have not been able to reproduce the issue after it stopped happening. That would make a bug report possible indeed.

@tflidd

Is this folder shared by a specific user compared to other shared folders? Is it reshared?

The only unique thing I could find with the shared folder was the trailing space., Resharing is common, the user sharing does this a lot.

@tflidd

Mostly office but not only. You spoke of an image affected as well, was it changed at some point? Or were the files moved around (when perhaps someone else edited them)?

As far as I can tel the files where just opened an they would revert to 0 bytes. I did think Onlyoffice was opening them as if empty and then overwriting them as empty. However it does not seem to be the case, also because I found empty image files I needed to restore. Onlyoffice does do this btw, I have a file that appears empty in OO but not in Libre.

@tflidd

When you didn’t use redis, the file locking was done in your database. Perhaps you kept the old locking table that caused the issue. Should be oc_file_locks or similar. Is this table empty and if not are the files concerned on it? And if you have backups from before, it would be interesting to look at this specific table.
Normally the problems should be less this file locking cache on redis…

I did not clear the locking table, that could at least explain the issue with restoring files. I’ll check the backups of that day, we have these for some months.

@tflidd

This was the name of the shared folder creating these problems? Trailing white spaces created problems with syncing on Windows: https://github.com/nextcloud/server/issues/5843
Are any of these folders synced by users with a desktop client?

I did see that report making me suspect the trailing space. Trailing spaces are all sorts of terrible in file/dir names. Some users have NC sync on Linux so it could be a cause. Luckily we have eliminated Windows for all but three systems on our network, oss ftw

@tflidd

Do you use a current version, it’s just to avoid that you chase an old already known and fixed bug.

We use the most current version, I try to update fairly quickly.

I think I’m going to setup a test system to figure these things out, try to reproduce. I’m also upgrading OO this weekend to 5.3 and do some more digging on the production system, thanks again so far.