Messages in this thread | | | Date | Thu, 18 Aug 2011 13:16:36 -0400 (EDT) | From | Justin Piszcz <> | Subject | Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 |
| |
On Thu, 18 Aug 2011, Jeff Layton wrote:
> On Thu, 18 Aug 2011 09:15:36 -0400 (EDT) > Justin Piszcz <jpiszcz@lucidpixels.com> wrote: > >> >> >> On Thu, 18 Aug 2011, Jeff Layton wrote: >> >>> On Thu, 18 Aug 2011 08:22:44 -0400 (EDT) >>> Justin Piszcz <jpiszcz@lucidpixels.com> 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)
Justin.
| |