From: "ralda-Mmb7MZpHnFY@public.gmane.org" <ralda-Mmb7MZpHnFY@public.gmane.org>
To: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Trouble accessing Buffalo NAS with CIFSFS
Date: Fri, 20 Jan 2012 20:06:26 +0100 [thread overview]
Message-ID: <20120120200626.b04b1d40.ralda@gmx.de> (raw)
In-Reply-To: <20120120111936.5329cbb4-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
Hallo Jeff!
> At this point, I'd suggest just setting the cifs_max_pending module
> parm low (1 or 2) and seeing if that helps. If it does, then that
> should basically emulate the effect of steve's eventual patch. If it
> doesn't then we'll probably need to have a closer look at why it isn't.
I have set cifs_max_pending to 2 (setting it 1 results in value 2).
Giving interesting results:
Normal mount/cp of single file works (same mount parameter as before).
Copying several files with midnight commander showed me a copy speed of
4.5 to 5.6 MByte per second - start at 4.5 and raising quickly to 5.6).
This speed is higher then ever received on copying to the same NAS
station from same hardware installation. Formerly (kernel 2.6.18
SMBFS) copies startet below 3.5 MBps and raised slowly up to about 4
MBps (or slightly above - only at very big files). So reducing the
setting of cifs_max_pendig not only let the drive work it additionally
gave me a big step in speed optimization.
... but: Switching virtual console during copy process let the copy
stop with a stuck mc as before. The only difference: After killing the
process and a delay of about 2 minutes (felt, not measured) the process
disappeared and NAS drive returned to a working state without system
reboot.
If you like/need I may catch more data for diagnosis tomorrow. Just let
me know what you need and how I shall test. I'm willing to give you all
data for diagnosis I'm able to collect.
--
Harald
next prev parent reply other threads:[~2012-01-20 19:06 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 [this message]
[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
[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=20120120200626.b04b1d40.ralda@gmx.de \
--to=ralda-mmb7mzphnfy@public.gmane.org \
--cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@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.