public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steve French (IBM LTC)" <smfltc@us.ibm.com>
To: Nuno Ferreira <nuno.ferreira@graycell.biz>
Cc: linux-cifs-client@lists.samba.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Process hangs copying large file to cifs
Date: Fri, 13 Aug 2004 01:34:19 -0500	[thread overview]
Message-ID: <411C60EA.EA01F2A2@us.ibm.com> (raw)
In-Reply-To: 1092328302.4172.42.camel@taz.graycell.biz

Your log entries indicate that the socket was dead, so the patch you hand applied for hashing of inodes
appears unrelated.   Many (including myself copy) much larger files regularly via CIFS.   I don't know
whether the best approach is to backport the other fixes that could affect this code path to your kernel
so we can see if this is a current problem in some recovery path or has already been fixed.   There are
only three to four global changes in the kernel (that hit the fs/cifs directory) since 2.6.6 that would
have to be dealt with to compile the current 2.6.8 fs/cifs directory on an older 2.6.6 kernel.

Nuno Ferreira wrote:

> On Ter, 2004-06-29 at 12:12 +0100, Nuno Ferreira wrote:
> > On Seg, 2004-06-28 at 16:58 -0500, Steve French wrote:
> > > >  > This is copying a 197Mb from an my laptop's IDE hardisk to a cifs
> > > > mounted share that's on a Win2000 Server
> > >
>


  reply	other threads:[~2004-08-12 18:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28 21:58 Process hangs copying large file to cifs Steve French
2004-06-29 11:12 ` Nuno Ferreira
2004-08-12 16:31   ` Nuno Ferreira
2004-08-12 16:31   ` Nuno Ferreira
2004-08-13  6:34     ` Steve French (IBM LTC) [this message]
2004-08-12 20:06       ` Nuno Ferreira
2004-08-13 16:21         ` Nuno Ferreira
  -- strict thread matches above, loose matches on Subject: below --
2004-06-24  3:16 Steve French
2004-06-24 10:48 ` Nuno Ferreira

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=411C60EA.EA01F2A2@us.ibm.com \
    --to=smfltc@us.ibm.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.ferreira@graycell.biz \
    /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