All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: "Lasse Kärkkäinen / Tronic" <tronic+lzID=lx43caky45@trn.iki.fi>
Cc: linux-kernel@vger.kernel.org, Steve French <smfltc@us.ibm.com>,
	Steve French <sfrench@samba.org>
Subject: Re: CIFS slowness & crashes
Date: Fri, 22 Jul 2005 00:04:16 +0200	[thread overview]
Message-ID: <9a87484905072115041cc576a4@mail.gmail.com> (raw)
In-Reply-To: <42E01163.3090302@trn.iki.fi>

On 7/21/05, Lasse Kärkkäinen / Tronic <tronic+lzID=lx43caky45@trn.iki.fi> wrote:
> I mailed sfrench@samba.org (the guy who wrote the driver) about this a
> month ago, but didn't get any reply. Is anyone working on that driver
> anymore?
> 
As far as I know Steve is still maintaining cifs. If you wrote him and
didn't get a response, then try again after a while (you might have
included him on CC for this mail) - maintainers don't always have time
to answer all mail in a timely fashion (or at all), and it's your
responsability to resend - that's not news.

You could also have written to the samba-technical@lists.samba.org
mailinglist (or copied it - it's listed in MAINTAINERS under "COMMON
INTERNET FILE SYSTEM (CIFS)").

[adding Stephen French to CC]

Personally I'd probably have send the mail
 To: Steve French <sfrench@samba.org>
 Cc: samba-technical@lists.samba.org
 Cc: linux-kernel@vger.kernel.org

> The problems that I wrote him about were:
> 
> 1. CIFS VFS hangs entirely if the server crashes or otherwise goes
> offline. Every process touching the mount halts too and cannot be killed
> (but they are not zombies). System loads start climbing and eventually
> the entire system will die (after system loads reach about 500). It is
> not possible to umount with either smbumount (hangs) nor umount -f
> (prints errors but doesn't umount anything). It won't recover without
> reboot, even if the server becomes back online.
> 
> This problem has been around as long as I have used SMBFS or CIFS. There
> has only been slight variation from one version to another. Sometimes it
> is possible to umount them (after some pretty long timeout), sometimes
> it is not. It seems as if the problem was being fixed, but none of the
> fixes really worked.
> 
> 2. Occassionally the transmission speeds go extremely low for no
> apparent reason. While writing this, I am getting 0.39 Mo/s over a
> gigabit network. Using FTP to read the same file gives 40 Mo/s, which is
> the speed that the file can be read locally on the server too.
> Remounting the CIFS does not help, nor does restarting Samba. However,
> using SMBFS I can get 20 Mo/s which is a bit better but still far from
> what it should be. It is important to mention that sometimes CIFS does
> work faster (about as quickly as SMBFS) and that this misbehavior occurs
> randomly.
> 
> During CIFS transfer, both computers seem to be idling. The CPU usage
> (including I/O wait) is almost none. During SMBFS transfer the server
> smbd process uses about 15 % CPU and the client is almost idle. The
> client is P4 3.4 GHz and the server is Athlon64 3000+.
> 
> I also tested with a Windows XP client machine and found out that this
> slowness issue does not happen with it, using the very same Samba server
> that the Linux CIFS mount is using.
> 
> - Tronic -
> 
>

  reply	other threads:[~2005-07-21 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 21:19 CIFS slowness & crashes Lasse Kärkkäinen / Tronic
2005-07-21 22:04 ` Jesper Juhl [this message]
2005-07-21 22:35   ` Steve French
2005-07-21 23:27     ` Jesper Juhl
2005-07-24 18:18     ` Lasse Kärkkäinen / Tronic
2005-07-21 22:43   ` Steve French

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=9a87484905072115041cc576a4@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@samba.org \
    --cc=smfltc@us.ibm.com \
    --cc=tronic+lzID=lx43caky45@trn.iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.