From mboxrd@z Thu Jan 1 00:00:00 1970 From: Justin Piszcz Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 Date: Thu, 18 Aug 2011 13:33:55 -0400 (EDT) Message-ID: References: <20110815064734.403b630f@corrin.poochiereds.net> <3300.1313637592@jrobl> <20110818091140.385a9455@barsoom.rdu.redhat.com> <20110818130408.71c55b96@barsoom.rdu.redhat.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Jeff Layton , "J. R. Okajima" , Jesper Juhl , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Alan Piszcz , Steve French , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Steve French Return-path: In-Reply-To: Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: On Thu, 18 Aug 2011, Steve French wrote: > On Thu, Aug 18, 2011 at 12:16 PM, Justin Piszcz wrote: >> >> >> On Thu, 18 Aug 2011, Jeff Layton wrote: >> >>> On Thu, 18 Aug 2011 09:15:36 -0400 (EDT) >>> Justin Piszcz wrote: >>> >>>> >>>> >>>> On Thu, 18 Aug 2011, Jeff Layton wrote: >>>> >>>>> On Thu, 18 Aug 2011 08:22:44 -0400 (EDT) >>>>> Justin Piszcz wrote: >>>>> >>>>>> Justin. >>>>>> >>>>> >>>>> To be clear -- incoming in this case is reads or writes? >>>> >>>> Reading from the CIFS share (Windows 7). >>>> >>>>> >>>>> 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. >>>> >>>> Ahh, good to know, have not tried writes yet. >>>> >>>>> >>>>> 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. >>>> >>>> Ok, that explains it then, thanks. >> >> >> Hi, >> >> Watching the rsync, it ran for a while, then: >> >> rsync: send_files failed to open "/cifs/w1/r1/data/hs12/f4_0.JPG": Cannot >> allocate memory (12) >> rsync: send_files failed to open "/cifs/w1/r1/data/hs12/f4_1.JPG": Cannot >> allocate memory (12) >> rsync: send_files failed to open "/cifs/w1/r1/data/hs12/f4_2.JPG": Cannot >> allocate memory (12) >> rsync: send_files failed to open "/cifs/w1/r1/data/hs12/f4_0.JPG": Cannot >> allocate memory (12) > > When we were testing async write to Windows 7 Pavel mentioned to me > another WIndows 7 bug - which may be what you are hitting. > > Under stress of simultaneous operations, Windows 7 server will sometimes start > responding with STATUS_INSUFF_SERVER_RESOURCES error code > (mapped to posix error ENOMEM by the Linux cifs kernel client) > He solved it by setting MaxWorkItems to 4096 in the Windows 7 registry. > > If anyone knows whether Microsoft has fixed this or has a bug #, let us know > because it is easier to hit with Linux kernel 3.0 and later (to > Windows 7 server). Ok, aside from sharing a few files, is there any recommended protocol to transfer millions of files at 10GbE speeds (500MiB/s) in both directions between Windows and Linux? Specifically from Linux.. >>From Windows, it achieves 500MiB/s no issues (From Linux/Samba). The other direction: - 30mb/s over 10GbE - Cannot allocate memory This should be good for moving a small subset of files, but for larger datasets it will not work. Any other filesystems/services/etc to try? Justin. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751458Ab1HRRd5 (ORCPT ); Thu, 18 Aug 2011 13:33:57 -0400 Received: from lucidpixels.com ([72.73.18.11]:58372 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750896Ab1HRRd4 (ORCPT ); Thu, 18 Aug 2011 13:33:56 -0400 Date: Thu, 18 Aug 2011 13:33:55 -0400 (EDT) From: Justin Piszcz To: Steve French cc: Jeff Layton , "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 In-Reply-To: Message-ID: References: <20110815064734.403b630f@corrin.poochiereds.net> <3300.1313637592@jrobl> <20110818091140.385a9455@barsoom.rdu.redhat.com> <20110818130408.71c55b96@barsoom.rdu.redhat.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 18 Aug 2011, Steve French wrote: > On Thu, Aug 18, 2011 at 12:16 PM, Justin Piszcz wrote: >> >> >> On Thu, 18 Aug 2011, Jeff Layton wrote: >> >>> On Thu, 18 Aug 2011 09:15:36 -0400 (EDT) >>> Justin Piszcz wrote: >>> >>>> >>>> >>>> On Thu, 18 Aug 2011, Jeff Layton wrote: >>>> >>>>> On Thu, 18 Aug 2011 08:22:44 -0400 (EDT) >>>>> Justin Piszcz wrote: >>>>> >>>>>> Justin. >>>>>> >>>>> >>>>> To be clear -- incoming in this case is reads or writes? >>>> >>>> Reading from the CIFS share (Windows 7). >>>> >>>>> >>>>> 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. >>>> >>>> Ahh, good to know, have not tried writes yet. >>>> >>>>> >>>>> 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. >>>> >>>> Ok, that explains it then, thanks. >> >> >> Hi, >> >> Watching the rsync, it ran for a while, then: >> >> rsync: send_files failed to open "/cifs/w1/r1/data/hs12/f4_0.JPG": Cannot >> allocate memory (12) >> rsync: send_files failed to open "/cifs/w1/r1/data/hs12/f4_1.JPG": Cannot >> allocate memory (12) >> rsync: send_files failed to open "/cifs/w1/r1/data/hs12/f4_2.JPG": Cannot >> allocate memory (12) >> rsync: send_files failed to open "/cifs/w1/r1/data/hs12/f4_0.JPG": Cannot >> allocate memory (12) > > When we were testing async write to Windows 7 Pavel mentioned to me > another WIndows 7 bug - which may be what you are hitting. > > Under stress of simultaneous operations, Windows 7 server will sometimes start > responding with STATUS_INSUFF_SERVER_RESOURCES error code > (mapped to posix error ENOMEM by the Linux cifs kernel client) > He solved it by setting MaxWorkItems to 4096 in the Windows 7 registry. > > If anyone knows whether Microsoft has fixed this or has a bug #, let us know > because it is easier to hit with Linux kernel 3.0 and later (to > Windows 7 server). Ok, aside from sharing a few files, is there any recommended protocol to transfer millions of files at 10GbE speeds (500MiB/s) in both directions between Windows and Linux? Specifically from Linux.. >>From Windows, it achieves 500MiB/s no issues (From Linux/Samba). The other direction: - 30mb/s over 10GbE - Cannot allocate memory This should be good for moving a small subset of files, but for larger datasets it will not work. Any other filesystems/services/etc to try? Justin.