From: Adrian Bunk <bunk@stusta.de>
To: Marc Koschewski <marc@osknowledge.org>
Cc: Ross Vandegrift <ross@jose.lug.udel.edu>,
Christian <christiand59@web.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc: CIFS reproducibly freezes the computer
Date: Thu, 16 Feb 2006 13:11:23 +0100 [thread overview]
Message-ID: <20060216121123.GD3511@stusta.de> (raw)
In-Reply-To: <20060215133523.GA6628@stiffy.osknowledge.org>
On Wed, Feb 15, 2006 at 02:35:23PM +0100, Marc Koschewski wrote:
> * Ross Vandegrift <ross@lug.udel.edu> [2006-02-14 13:47:08 -0500]:
>
> > On Tue, Feb 14, 2006 at 05:40:03PM +0100, Marc Koschewski wrote:
> > > Is that maybe dependant on _what_ version of Samba is running on the receiving
> > > end?
> >
> > I've seen it copying to Windows 2k3. Only uploading large files, and
> > it's not every time. I'd say 50% of the time, my box freezes when
> > copying something around 100MiB or larger.
> >
> > IIRC, my workstation at the office is running 2.6.15.1 or .4.
>
> I moved to CIFS because SMB didn't work well for me, as well as did NFS. Both
> seems to stall in a way, I could never really reproduce. But CIFS is very stable
> over here. Never ever had a problem with it, whereas both NFS and SMB are likely
> to cause trouble at least once a week. Without log records, without any chance
> of recovery. Mostly hard-freezes.
The problems are often error paths.
I might be running in some unusual error paths in CIFS, and the same
might be true for you in the SMB and NFS cases.
The SMB file system in the kernel is unfrtunately unmaintained, but NFS
is well maintained. Have you sent a bug report for your NFS problems
similar to my bug report for my CIFS problems?
> Marc
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-02-16 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 13:50 2.6.16-rc: CIFS reproducibly freezes the computer Adrian Bunk
2006-02-14 15:00 ` Marc Koschewski
2006-02-14 15:59 ` Christian
2006-02-14 16:40 ` Marc Koschewski
2006-02-14 18:47 ` Ross Vandegrift
2006-02-15 13:35 ` Marc Koschewski
2006-02-15 16:47 ` Ross Vandegrift
2006-02-16 12:11 ` Adrian Bunk [this message]
2006-02-16 13:32 ` Marc Koschewski
2006-02-27 6:29 ` Adrian Bunk
2006-02-28 3:02 ` Ross Vandegrift
2006-02-14 18:12 ` Jan Engelhardt
2006-02-14 18:33 ` Lee Revell
[not found] ` <OFD6EC212C.9D3CD1CC-ON87257115.0057751D-86257115.0057E155@us.ibm.com>
2006-02-16 12:07 ` [linux-cifs-client] " Adrian Bunk
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=20060216121123.GD3511@stusta.de \
--to=bunk@stusta.de \
--cc=christiand59@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@osknowledge.org \
--cc=ross@jose.lug.udel.edu \
/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