After recent update for 29.04 from 29.03 I noticed that the size used is not displaying correctly. I cant find any recent mention of this in posts or on the github, but perhaps my search fu is failing this morning.
this is what shows from the ui
this is from a du -h -d 1 of the files location, the 1.4tb is for the user displayed above
i do have my data folder mounted as an nfs mount in the OS and mapped the location to the data location where the server is running. in 29.03 this was displaying properly.
The UI is just considering the file sizes that are on the storage, not different versions and not the trash bin.
If you do the du -h -d 1 within the user’s folder, what do you get?
1.4TB same as shown above, same as what used to display in the UI in 29.03.
And do you use external storage?
If you are on the admin page, it sometimes gives you the hint to add some indices to the database to improve performance. Did you do that after the update. Is it asking to do it now?
What you can try, in the web-interface, you can see the size of folders, and you can do the same with du to check which folder is creating this difference. If you identified the folder, we can try to figure out why the update messed things up.
(originally, I was thinking that how cached files like thumbnails etc. are taken into account might differ. However, I’d expect such things on major versions to change and not on updated within the same major version, except there was a bug in the first place).
i have the external storage app installed but its not in use right now.
i saw no indication of adding indexes after this recent update in the logs.
im seeing lower size reported from the web interface, not from the actual file system. I’m sure i have over 1 TB on the filesystem as it contains all of my pictures, which is what the du returns. im going to run a snapshot on my nas just in case something funky is going on with NC.
i think im going to run the full file scan which i havent had to do in a while. i hesitated doing that in the event there was something known with this or needed troubleshooting. the one thing im doing most probably are not is the nfs mount in my fstab on the server mounted to the data location of the container nextcloud is running as, though ive not had this sort of thing happen before since ive had this set up for years.
In theory, it should not be required to do that.
If you have organized the photos in different folders, it might be interesting to know, if some folders are missing, a few files, … so you can get down to the issue where this problem was created. Keep an eye on the bug tracker as well, if someone reports such an issue.
Yes, there are multiple folders, the photos themselves are around 800gb in photos/year/month organization and the rest of my data throughout other folders.