All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: ROBIN CERNIN <cerninr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CIFS - VFS error question
Date: Thu, 27 Sep 2012 09:37:09 +0100	[thread overview]
Message-ID: <1348735029.2633.20.camel@localhost> (raw)
In-Reply-To: <CAFdSyFFkcSbBrqH7mgBJxFL+kfZNuMBK+8ZGoarPxQeAS0rXng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, 2012-09-26 at 09:33 +0200, ROBIN CERNIN wrote:
> Hello,
> 
> First of all I wanna say you are doing great job developing cif-utils.
> Secondly I have question on using following version of cifs:
> 
> filename:       /lib/modules/2.6.18-308.8.1.
> el5/kernel/fs/cifs/cifs.ko
> version:        1.60RH
> description:    VFS to access servers complying with the SNIA CIFS
> Specification e.g. Samba and Windows
> license:        GPL
> author:         Steve French <sfrench-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> srcversion:     63D9396D38F380652744D7E
> depends:
> vermagic:       2.6.18-308.8.1.el5 SMP mod_unload gcc-4.1
> parm:           CIFSMaxBufSize:Network buffer size (not including
> header). Default: 16384 Range: 8192 to 130048 (int)
> parm:           cifs_min_rcv:Network buffers in pool. Default: 4
> Range: 1 to 64 (int)
> parm:           cifs_min_small:Small network buffers in pool. Default:
> 30 Range: 2 to 256 (int)
> parm:           cifs_max_pending:Simultaneous requests to server.
> Default: 50 Range: 2 to 256 (int)
> module_sig:    883f3504fa440f6a462ac2afa8e12f112b2f409f6ea4176acbbe7f2f2c13e944e9a17d507b429c09c8e9ef6118eb3d5c40fcbfa81c96bf86e626c06e
> 
> on RHEL get following errors in the /var/log/messages:
> 
> Sep 24 20:08:48 xxxxxxx kernel:  CIFS VFS: No response for cmd 50 mid 39222
> Sep 24 20:08:48 xxxxxxx kernel:  CIFS VFS: No response for cmd 50 mid 39231
> Sep 24 20:08:48 xxxxxxx kernel:  CIFS VFS: No response for cmd 50 mid 39236
> Sep 25 10:45:16 xxxxxxx kernel:  CIFS VFS: Send error in SessSetup = -5
> Sep 25 10:45:16 xxxxxxx kernel:  CIFS VFS: Unexpected lookup error -5
> Sep 25 13:08:25 xxxxxxx kernel:  CIFS VFS: No response for cmd 6 mid 47208
> Sep 25 16:50:27 xxxxxxx kernel:  CIFS VFS: No response for cmd 162 mid 48857
> Sep 25 20:07:37 xxxxxxx kernel:  CIFS VFS: No response for cmd 50 mid 50442
> 
> 
> Can you please clarify a bit to me what are these errors related to? I
> dont hear anyone complaing that this isnt working but I can still see
> these errors.
Hi Robin, 

Did you have any network outages or network congestion at those times?
It appears the client for some reason couldn't receive a response from
the server.

Sachin Prabhu

  parent reply	other threads:[~2012-09-27  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26  7:33 CIFS - VFS error question ROBIN CERNIN
     [not found] ` <CAFdSyFFkcSbBrqH7mgBJxFL+kfZNuMBK+8ZGoarPxQeAS0rXng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-26 17:42   ` Steve French
2012-09-27  8:37   ` Sachin Prabhu [this message]
2012-09-27  8:59     ` ROBIN CERNIN
2012-09-27 13:04     ` Jeff Layton
     [not found]       ` <20120927090409.3d2febe7-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-09-28 21:03         ` ROBIN CERNIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1348735029.2633.20.camel@localhost \
    --to=sprabhu-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=cerninr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.