From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: "ralda-Mmb7MZpHnFY@public.gmane.org"
<ralda-Mmb7MZpHnFY@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Trouble accessing Buffalo NAS with CIFSFS
Date: Thu, 19 Jan 2012 23:08:50 +0530 [thread overview]
Message-ID: <4F18552A.3030804@suse.com> (raw)
In-Reply-To: <20120119090752.9b7aea6c.ralda-Mmb7MZpHnFY@public.gmane.org>
On 01/19/2012 01:37 PM, ralda-Mmb7MZpHnFY@public.gmane.org wrote:
> new installation. With CIFS I can mount the NAS station and I can see
> the directory listings, but whenever I try to copy a file to the NAS
> station the copy hangs and probably never return (leaving the process
> with a D status in process list).
> The NAS is mounted like this (output from /proc/mounts):
>
> //archiv/share /nas cifs rw,mand,nosuid,nodev,noexec,relatime,sec=ntlm,
> unc=\\archiv\share,username=root,uid=1002,forceuid,gid=65534,forcegid,
> addr=192.168.178.3,file_mode=0600,dir_mode=0700,nounix,rsize=16384,
> wsize=65216,actimeo=1
> 0 0
>
> mount.cifs --version: 1.10
>
> dmesg output gives info like this:
>
> CIFS VFS: Autodisabling the use of server inode numbers on \\archiv
> \share. This server doesn't seem to support them properly. Hardlinks
> will not be recognized on this mount. Consider mounting with the
> "noserverino" option to silence this message.
> CIFS VFS: Server archiv has not responded in 300 seconds.
> Reconnecting...
> CIFS VFS: sends on sock ae3b9b40 stuck for 15 seconds
> CIFS VFS: Error -11 sending data on socket to server
> CIFS VFS: sends on sock ae3b9b40 stuck for 15 seconds
> CIFS VFS: Error -11 sending data on socket to server
> CIFS VFS: sends on sock ae3b9b40 stuck for 15 seconds
> CIFS VFS: Error -11 sending data on socket to server
> CIFS VFS: Error -32 sending data on socket to server
> CIFS VFS: Error -32 sending data on socket to server
> CIFS VFS: Error -32 sending data on socket to server
> ...
>
Error -32 is -EPIPE and it is kinda unusual from kernel_sendmsg(). I'm
suspecting problems with CIFS socket/TCP state but hard to tell without
much information. Wondering perhaps, CIFS should also handle -EPIPE like
sunrpc and try to gracefully shutdown the socket on -EPIPE allowing
reconnections works without trouble...
Suresh
next prev parent reply other threads:[~2012-01-19 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 8:07 Trouble accessing Buffalo NAS with CIFSFS ralda-Mmb7MZpHnFY
[not found] ` <20120119090752.9b7aea6c.ralda-Mmb7MZpHnFY@public.gmane.org>
2012-01-19 12:05 ` Jeff Layton
[not found] ` <20120120113042.0fdfea5f.ralda@gmx.de>
[not found] ` <20120120101938.7ca7464d@tlielax.poochiereds.net>
[not found] ` <20120120165657.00042c72.ralda@gmx.de>
[not found] ` <20120120165657.00042c72.ralda-Mmb7MZpHnFY@public.gmane.org>
2012-01-20 16:19 ` Jeff Layton
[not found] ` <20120120111936.5329cbb4-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2012-01-20 19:06 ` ralda-Mmb7MZpHnFY
[not found] ` <20120120200626.b04b1d40.ralda-Mmb7MZpHnFY@public.gmane.org>
2012-01-20 19:32 ` Jeff Layton
[not found] ` <20120120143235.1d4d811e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2012-01-20 19:42 ` Steve French
[not found] ` <CAH2r5mt5KPtK_5Abz8nz_sKH3vT2h=1d7DHHBvX4BSRd37auug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-20 20:54 ` Harald Becker
2012-01-20 21:24 ` Łukasz Maśko
2012-01-20 21:07 ` ralda-Mmb7MZpHnFY
2012-01-19 17:38 ` Suresh Jayaraman [this message]
[not found] ` <4F18552A.3030804-IBi9RG/b67k@public.gmane.org>
2012-01-19 18:39 ` Steve French
-- strict thread matches above, loose matches on Subject: below --
2012-01-19 8:19 ralda-Mmb7MZpHnFY
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=4F18552A.3030804@suse.com \
--to=sjayaraman-ibi9rg/b67k@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ralda-Mmb7MZpHnFY@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.