Again ...
"First, what sort of error do you get when you try to delete files in
users private files? Did you try turning on debugging to see what
Moodle had to say?"
Query DB mdl_files table:
select filearea,userid,filename,filesize,contenthash from mdl_files where filename like '%.mbz'
That's all meta data. Could sort by filesize or userid
Outputs like:
filearea userid filename filesize contenthash
course 6 backup-moodle2-course-10-car_product_indoor-20151209-1131.mbz 10401336 285f25dbd50f8ec9f40b44db15e7c38349dfee1e
course 6 backup-moodle2-course-67-tdp_504-20181120-0557.mbz 332963437 0e1f2fe7995872845947effa69806fe3e28a741e
See the contenthash of first backup? 285f25dbd50f8ec9f40b44db15e7c38349dfee1e
cd /path/to/moodledata/filedir/
find ./ -name 285f25dbd50f8ec9f40b44db15e7c38349dfee1e
./28/5f/285f25dbd50f8ec9f40b44db15e7c38349dfee1e
[root@server filedir]# ls -l ./28/5f/285f25dbd50f8ec9f40b44db15e7c38349dfee1e
-rw-rw-rw- 1 apache apache 10401336 Dec 9 2015 ./28/5f/285f25dbd50f8ec9f40b44db15e7c38349dfee1e
10401336 is actual size of file
Meta data had same,
file -b ./28/5f/285f25dbd50f8ec9f40b44db15e7c38349dfee1e
gzip compressed data, from Unix
shows a gzip compressed ... it's a valid moodle backup .mbz file.
Add to your query the offending userid.
Did you login as the user? Then check users private files area? Have to pretend to restore but don't to see the users private file area.
'SoS', Ken