From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Layton Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 Date: Thu, 18 Aug 2011 09:11:40 -0400 Message-ID: <20110818091140.385a9455@barsoom.rdu.redhat.com> References: <20110815064734.403b630f@corrin.poochiereds.net> <3300.1313637592@jrobl> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "J. R. Okajima" , Jesper Juhl , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Alan Piszcz , Steve French , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Justin Piszcz Return-path: In-Reply-To: Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: On Thu, 18 Aug 2011 08:22:44 -0400 (EDT) Justin Piszcz wrote: > > > 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. > To be clear -- incoming in this case is reads or writes? Up until 3.0 cifs.ko didn't parallelize writes from a single thread. In 3.0 I added a patchset to increase the allowable wsize and to allow the kernel to issue writes in parallel. Reads still suffer from the same problem however. I'm working on a patchset that should do the same thing for them, but it requires a fairly substantial overhaul of the receive codepaths. -- Jeff Layton From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755817Ab1HRNKU (ORCPT ); Thu, 18 Aug 2011 09:10:20 -0400 Received: from mail-qw0-f46.google.com ([209.85.216.46]:44995 "EHLO mail-qw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755588Ab1HRNKS (ORCPT ); Thu, 18 Aug 2011 09:10:18 -0400 Date: Thu, 18 Aug 2011 09:11:40 -0400 From: Jeff Layton To: Justin Piszcz Cc: "J. R. Okajima" , Jesper Juhl , linux-kernel@vger.kernel.org, Alan Piszcz , Steve French , linux-cifs@vger.kernel.org Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 Message-ID: <20110818091140.385a9455@barsoom.rdu.redhat.com> In-Reply-To: References: <20110815064734.403b630f@corrin.poochiereds.net> <3300.1313637592@jrobl> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 18 Aug 2011 08:22:44 -0400 (EDT) Justin Piszcz wrote: > > > 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. > To be clear -- incoming in this case is reads or writes? Up until 3.0 cifs.ko didn't parallelize writes from a single thread. In 3.0 I added a patchset to increase the allowable wsize and to allow the kernel to issue writes in parallel. Reads still suffer from the same problem however. I'm working on a patchset that should do the same thing for them, but it requires a fairly substantial overhaul of the receive codepaths. -- Jeff Layton