Samba share is blocking access to home folder

[lefsha]

I have samba folder is mounted to local folder in home directory.
Samba connection has some issue. It's a different topic.

Why I can't access other files in my home directory by using mc or other file browsers?

It looks to be general behavior for any flavor of Linux. Why not just give an empty folder
if some one entering that directory and don't bother at all if nobody trying to access the shared data.

Unlimited loop without possibility to interrupt it is not the best solution for obviously predicted and normal issue
with remote data access.

Of course, if there any solution for that problem existing I would like to know. But then it should be a default behavior.
_________________
Lefsha

[eccerr0r]

I think I finally understand what you're asking here... having a bit of trouble understanding the question.

What's happening is that the mounted directory is being polled when the program you're using is reading all directory entries in the parent directory. The directory entry read is stuck in kernel code. Directories are "files" in the Unix point of view hence they all get treated similarly.

Unfortunately there's no real way for the user to tell the kernel to "give up" early on that read - the kernel stays in "D" state and it itself determines when it should give up and return to the user - if at all.

Ideally there's some sort of timeout that the kernel should respect, but what would be nice is some way for the user to tell the kernel to give up on the call before timeout - and have that program stop trying again unless a change in status comes back from the kernel. This is especially a problem with networks where you can't really tell if the other machine is either busy or will never come back.

Not sure if there's a clean solution here unfortunately.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[lefsha]

Sorry for making my question so unclear.

Is it not a common issue, every one knows about?

I will try to disable all kind of oplocks in smb.conf not quite sure, but may be it will help.
Unfortunately it's a server setting, so no user can control it. So bad.