Re: CIFS-VFS error

Jeff Layton <[email protected]>
Newsgroups gmane.linux.file-systems.cifs
Message-ID <[email protected]>
On Sun, 19 Apr 2009 21:15:28 -0400
Anirudh Srinivasan <[email protected]> wrote:

> Hi Gurus,
> We have a webserver that has CPU spiking up every sat evening. When i looked
> at that time to the messages i see the following :
> 
> Apr 15 21:16:12 lxweb kernel:  CIFS VFS: No response for cmd 50 mid 47215
> Apr 18 15:50:37 lxweb kernel:  CIFS VFS: No response for cmd 50 mid 47928
> Apr 18 18:22:44 lxweb kernel:  CIFS VFS: sends on sock d410ce00 stuck for 15
> seconds
> Apr 18 18:22:44 lxweb kernel:  CIFS VFS: Error -11 sending data on socket to
> server
> Apr 18 18:22:44 lxweb kernel:  CIFS VFS: Write2 ret -11, written = 0
> Apr 18 18:23:00 lxweb kernel:  CIFS VFS: sends on sock d410ce00 stuck for 15
> seconds
> Apr 18 18:23:00 lxweb kernel:  CIFS VFS: Error -11 sending data on socket to
> server
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: server not responding
> Apr 18 18:23:11 lxweb last message repeated 3 times
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55417
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55418
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55324
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55440
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55215
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55372
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55429
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55426
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55366
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55436
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55389
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55412
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55421
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55325
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55452
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55321
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55461
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55348
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55353
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55460
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55454
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55431
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55428
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55465
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55425
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55437
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55448
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55424
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55415
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55456
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55443
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55433
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55438
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55442
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55447
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55445
> Apr 18 18:23:11 lxweb kernel:  CIFS VFS: No response to cmd 47 mid 55446
> 
> This has been the third week i am seeing this happen . Any help to figure
> out what is going on would be highly appreciated.
> 

What kernel version are you running here?

-- 
Jeff Layton <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.