jj_uk Posted August 15, 2021 Share Posted August 15, 2021 (edited) Since updating to 6.10, some files and folders inside appdata are not visible on Windows. The whole appdata folder wasn't being exported as the update changed this from export: yes to export: yes(hidden). - why? I've changed it back to export: yes, but there are a few folders in there that are showing as empty in Windows explorer, but if i go into the affected container's colsole, I can see the files with `ls -la`. Any ideas? Edited August 15, 2021 by jj_uk Quote Link to comment
Squid Posted August 15, 2021 Share Posted August 15, 2021 Could be naming issues on the folders. EG: with 2 folders named TEST1 and test1 you will only see the contents of one of them. Quote Link to comment
jj_uk Posted August 15, 2021 Author Share Posted August 15, 2021 I don't think it's that. If I try to navigate to an affected folder using the Krusader app, I get an access denied error. The permissions for the folders are: drw-rw-rw- 1 99 users 32 May 6 04:49 blueprints Quote Link to comment
Frank1940 Posted August 15, 2021 Share Posted August 15, 2021 1 minute ago, jj_uk said: drw-rw-rw- 1 99 users 32 May 6 04:49 blueprints You must have the Execute bit set in order to be able to read the contents of a Linux directory. that is: drwxrwxrwx (Google is you require more info...) Quote Link to comment
jj_uk Posted August 15, 2021 Author Share Posted August 15, 2021 Thanks, yes, that's fixed it. I didn't change that permission on the folders. Maybe a bug? Quote Link to comment
remotevisitor Posted August 15, 2021 Share Posted August 15, 2021 Permissions on the directory don’t look correct, in order to enter a directory it should have the x (eXecute) permission. Quote Link to comment
remotevisitor Posted August 15, 2021 Share Posted August 15, 2021 (edited) 5 minutes ago, jj_uk said: I didn't change that permission on the folders. Maybe a bug? Possibly a bug in samba for previously allowing access which has been fixed in the latest version. Edited August 15, 2021 by remotevisitor Quote Link to comment
Frank1940 Posted August 15, 2021 Share Posted August 15, 2021 I believe this has occurred in the past to folks. It is usually traced to a plugin, Docker or VM which has been misconfigured. Look at the directory and see if you can figure out which 'program' actually generated that directory. Those would not be 'bad' permissions for data files as most data files would not be executable! Quote Link to comment
Squid Posted August 15, 2021 Share Posted August 15, 2021 Appdata folders have their own unique permission requirements which may or may not be compatible over SMB. Your mileage may vary. Quote Link to comment
jj_uk Posted August 15, 2021 Author Share Posted August 15, 2021 I just installed a new instance of the container and it set all created folders to r-x, as expected. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.