mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: "J. R. Okajima" <hooanon05@yahoo.co.jp>
Cc: Jeff Layton <jlayton@samba.org>, Jesper Juhl <jj@chaosbits.net>,
	linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>,
	Steve French <sfrench@samba.org>,
	linux-cifs@vger.kernel.org
Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2
Date: Thu, 18 Aug 2011 08:22:44 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1108180821440.7903@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1108180807070.7903@p34.internal.lan>



On Thu, 18 Aug 2011, Justin Piszcz wrote:

>
>
> On Thu, 18 Aug 2011, Justin Piszcz wrote:
>
>> 
>> 
>> On Thu, 18 Aug 2011, J. R. Okajima wrote:
>> 
>>> 
>>> Justin Piszcz:
>>>> Does anyone know if any kernel supports CIFS w/out crashing? I'd like to
>>>> backup some CIFS shares, thanks.
>>>> 
>>>> 
>>>> mount -t cifs //w2/x /mnt -o user=user,pass=pass
>>>> 
>>>> [  881.388836] CIFS VFS: cifs_mount failed w/return code = -22
>>> 	:::
>>> 
>>> Since it failed mounting, this patch will help you. Although the patch
>>> will fix one bug, there still may exist another problem.
>>> 
>>> http://marc.info/?l=linux-cifs&m=131345112022031&w=2
>> 
>> Hi,
>> 
>> Latest patch (this one) applied to linux-3.1-rc2 works, at least it mounted
>> this time and did not instantly crash the kernel!
>> 
>> I also tried the hostname again (and it did not crash the kernel, but it 
>> failed to mount).
>> 
>> Used the IP and it mounted successfully:
>> //10.0.0.11/x          28T  5.0T   23T  19% /mnt
>> //10.0.0.11/y          19T  1.2T   18T   7% /mnt2
>> 
>> It has not crashed yet (which is good), I'll apply this patch to my
>> production machine and test taking backups of this data and let you know
>> if it crashes again, thanks!
>> 
>> Justin.
>
>
> Hello,
>
> It is working but very slowly:
>
> Device eth6 [10.0.1.2] (1/1):
> ================================================================================
> Incoming:                               Outgoing:
> Curr: 37.60 MByte/s                     Curr: 0.44 MByte/s
> Avg: 4.98 MByte/s                       Avg: 0.09 MByte/s
> Min: 0.00 MByte/s                       Min: 0.00 MByte/s
> Max: 40.79 MByte/s                      Max: 0.48 MByte/s
> Ttl: 1.45 GByte                         Ttl: 26.77 MByte
>
> Over 10GbE the other direction (Linux -> Windows (via Samba)) I get 500MiB/s, 
> is CIFS slow?
>
> I'll look into options to tweak the speed but this is very poor speed when 
> you have to transfer 5-10TB.  However, it is not crashing anymore, so any 
> speed is better than that :)
>
> Justin.

Hi,

Mounting with:
rw,uid=1000,gid=100,mode=0644,rsize=130048,wsize=1048576,credentials=/root/.cifs 
Same speed:
Device eth6 [10.0.1.2] (1/1):
================================================================================
Incoming:                               Outgoing:
Curr: 32.42 MByte/s                     Curr: 0.38 MByte/s
Avg: 30.72 MByte/s                      Avg: 0.39 MByte/s
Min: 0.00 MByte/s                       Min: 0.00 MByte/s
Max: 43.64 MByte/s                      Max: 0.59 MByte/s
Ttl: 20.15 GByte                        Ttl: 261.03 MByte

Thoughts?

Has anyone achieved > 30-40MB/s with CIFS?
This is a 10GbE link (and yes JUMBO frames are enabled on both sides, and 
again, samba from Linux->Windows = 500MB/s)

Justin.


  reply	other threads:[~2011-08-18 12:22 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15  9:10 Kernel 3.0: Instant kernel crash when mounting CIFS Justin Piszcz
2011-08-15  9:18 ` Jesper Juhl
2011-08-15 10:47   ` Jeff Layton
2011-08-15 10:54     ` Justin Piszcz
2011-08-15 18:01       ` Justin Piszcz
2011-08-15 18:09         ` Steve French
2011-08-15 19:31         ` Dave Jones
2011-08-17 19:16         ` Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 Justin Piszcz
     [not found]           ` <alpine.DEB.2.02.1108171545190.5877@p34.internal.lan>
2011-08-17 19:47             ` Justin Piszcz
2011-08-17 20:13               ` Jeff Layton
2011-08-17 20:45                 ` Justin Piszcz
2011-08-17 21:11                   ` Arnaud Lacombe
2011-08-17 21:53                     ` Justin Piszcz
2011-08-17 22:13                       ` Justin Piszcz
2011-08-17 22:18                         ` Justin Piszcz
2011-08-17 23:31           ` Valdis.Kletnieks
2011-08-18  3:19           ` J. R. Okajima
2011-08-18 10:35             ` Justin Piszcz
2011-08-18 12:14               ` Justin Piszcz
2011-08-18 12:22                 ` Justin Piszcz [this message]
2011-08-18 13:11                   ` Jeff Layton
2011-08-18 13:15                     ` Justin Piszcz
2011-08-18 17:04                       ` Jeff Layton
2011-08-18 17:15                         ` Steve French
2011-08-18 17:16                         ` Justin Piszcz
2011-08-18 17:25                           ` Steve French
2011-08-18 17:33                             ` Justin Piszcz
2011-08-18 17:43                               ` Steve French
2011-08-18 18:18                                 ` Justin Piszcz
2011-08-18 18:52                                   ` Jeff Layton
2011-08-18 18:54                                     ` Justin Piszcz
2011-08-18 19:02                                       ` Steve French
2011-08-26 21:59                                     ` Jeff Layton
2011-08-26 22:57                                       ` Justin Piszcz
2011-08-26 23:05                                         ` Steve French
2011-08-26 23:16                                           ` Justin Piszcz
2011-08-27 14:31                                             ` Jeff Layton
2011-08-18 17:36                             ` Kong Li
2011-08-18 18:33                             ` Jeff Layton
2011-08-18 14:19                 ` J. R. Okajima
2011-08-18 16:01                 ` Steve French
2011-08-18 16:02                   ` Steve French

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=alpine.DEB.2.02.1108180821440.7903@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=ap@solarrain.com \
    --cc=hooanon05@yahoo.co.jp \
    --cc=jj@chaosbits.net \
    --cc=jlayton@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®