Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
linux:samba:troubleshooting [2012/01/16 17:28] 109.230.216.60 LYyEkVNludkTm |
linux:samba:troubleshooting [2012/01/17 21:49] (current) greebo old revision restored |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | Phenmeonal breakdown of the topic, you should write for me too! | + | ===== CIFS VFS No response for cmd n mid… ===== |
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | Aug 1 22:58:16 dreadnought kernel: CIFS VFS: No response to cmd 46 mid 25661 | ||
+ | Aug 1 22:58:16 dreadnought kernel: CIFS VFS: Send error in read = -11 | ||
+ | Aug 1 22:58:16 dreadnought kernel: CIFS VFS: No response for cmd 50 mid 25664 | ||
+ | Aug 1 22:58:16 dreadnought kernel: CIFS VFS: No response to cmd 47 mid 25663 | ||
+ | Aug 1 22:58:20 dreadnought kernel: CIFS VFS: No response to cmd 47 mid 25662 | ||
+ | Aug 1 22:58:20 dreadnought kernel: CIFS VFS: Write2 ret -11, written = 0 | ||
+ | Aug 1 22:58:20 dreadnought kernel: CIFS VFS: Send error in read = -9 | ||
+ | Aug 1 22:58:20 dreadnought kernel: CIFS VFS: Write2 ret -9, written = 0 | ||
+ | Aug 1 22:59:52 dreadnought kernel: CIFS VFS: No writable handles | ||
+ | Aug 1 23:00:29 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:00:36 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:01:16 dreadnought kernel: CIFS VFS: No writable handles for inode | ||
+ | Aug 1 23:02:28 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:03:23 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:03:44 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:05:35 dreadnought kernel: CIFS VFS: No writable handles for inode | ||
+ | Aug 1 23:06:18 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:06:35 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:06:46 dreadnought kernel: CIFS VFS: No writable handles for inode | ||
+ | Aug 1 23:06:46 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:07:02 dreadnought kernel: CIFS VFS: close with pending writes | ||
+ | Aug 1 23:07:46 dreadnought kernel: CIFS VFS: server not responding | ||
+ | </ | ||
+ | |||
+ | I found a workaround which involves disabling Opportunistic Locking. This will have a small performance impact, but at least the thing wont hang up and use 100% CPU for no goddamn reason. Yes, this article has an angry tone, because this issue has eaten way too much of my time today. [[http:// | ||
+ | |||
+ | To disable Opportunistic Locking, you have to set the contents of the file “'' | ||
+ | |||
+ | < | ||
+ | # cifs client workaround | ||
+ | modprobe cifs | ||
+ | echo 0 > / | ||
+ | </ |