After reading through most of this thread, hoping for some indication of a solution or positive steps towards one, I would also like to contribute to SuperMarios and schumakus information given, and inform that I see this hanging smbd several times a day too.
I can think of many reasons why files get "busy" and data gets "corrupted" when this issue arises, but likely not that the fault in the samba subsystem or journaling part is directly corrupting data, but when a file is being altered or written and another system or service is triggering the lock-up situation, the corruption occurs on the other process that actually did noting "wrong". So in my mind it is more the consequence of using a system which has this faulty condition is not safe - and QNAP better get this fixed NOW!
My 809 has 8 2TB disks in one RAID 5 and has several million files (large and small) in many thousands of folders (which QNAP can' have a copy of either
). I also have a 409 Pro myself - and just recommended two others to buy respectively a 219P+ and a 659 Pro+. I really hope they don't have to experience the same situation as the latter will be using this in a business scenario and for customer upload access etc (not via SAMBA, though - but local access will be affected).
And this leads to my info regarding all of this: It seems to me, that only SAMBA access is affected, whilst you can still access the Admin Web GUI and other services even if SAMBA access is hung. I can trigger the condition by:
- Have the NAS being idle for some time, perhaps 5 minutes is enough, but perhaps more... say 15 minutes
- Read access via SAMBA is fine at this point
- Create a folder in some SAMBA share via SAMBA (from Windows)
- At that point I can't name the new folder (which Windows usually initially names "New folder") but the parent folder view becomes unresponsive
- The admin interface and FTP access still works - and I think other non-SAMBA subsystems probably do too
- As said, either the folder view locks up for some seconds (20-40, someone mentions) or times out with an error to follow
- The operation then completes (if the app performing the operation didn't time out itself) but all SAMBA access is unresponsive during the black-out period.
- I have seen this being triggered by creating files too (not just directories)
The bottom line is that it was good to read that SuperMario had the condition described quite well and that I finally too got a diagnosis that fit what I saw - I just hope this has the proper priority at QNAP - because the SAMBA service is probably the most vital function and must have absolutely rock stable