public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: "Kinzel, David" <David.Kinzel@encana.com>
Cc: xfs@oss.sgi.com
Subject: Re: High latencies writing to a memory mapped file
Date: Tue, 27 Jul 2010 23:02:04 +0200	[thread overview]
Message-ID: <20100727210204.GA14184@citd.de> (raw)
In-Reply-To: <F57F2AD357626644AF76410876025D75529604@CGYEX705.encana.com>

On 27.07.2010 13:59, Kinzel, David wrote:
> >> Matthias Schniedermeyer put forth on 7/27/2010 4:24 AM:
> >> 
> >> > We have a linux-computer with samba to act as a fileserver 
> >for a few 
> >> > Windows-Clients and ever since kernel 2.6.26 (Never 
> >happend with 2.6.25) 
> >> > the server randomly "hangs" for a few seconds (Which is more of a 
> >> > problem that drives people crazy).
> >> 
> 
> The server hangs, or the connections to samba do? I've found that samba

That's a question i actually hadn't though about. This certainly extends 
the circle of possible culprits a little. From the top of my mind thats 
the the NIC (Intel e100) and it's e100-driver and the (As Cheap as 
possible) 24-port 100MBit-Switch used to connect all computers. And last 
but not least the whole TCP/IP network-stack in the kernel.

This also differentiates "our" server to the mentioned "copy" which uses 
whichever GBit-NIC that was onboard (Something from Realtek AFAIR) to 
the a tree of even cheaper 5 and 8 port switches, not to mention 
on-the-fly-wiring.

> is given a ridiculously low IO priority so that any IO on the server
> will pretty much cause it to stall -- be it updating locate, a backup
> job, etc. 

Whatever the culprit is, in our case it's something that changed between 
2.6.25 and 2.6.26, before 2.6.26 we were happy with whatever was current 
for years. (System is running a reguarly updated Debian SID for at least 
6-7 years)

And the most irritating things is the "a reboot fixes it". When the 
problem reared it's head, you can restart samba, drop all caches, 
umount/decompose the RAID and whatnot, the problem immediatly reappears
after you get back to working conditions.




Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-07-27 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 14:47 High latencies writing to a memory mapped file Shawn Bohrer
2010-07-22 23:28 ` Dave Chinner
2010-07-26 22:09   ` Shawn Bohrer
2010-07-26 23:22     ` Dave Chinner
2010-08-03 22:03       ` Shawn Bohrer
2010-07-27  9:24 ` Matthias Schniedermeyer
2010-07-27 10:47   ` Emmanuel Florac
2010-07-27 11:27     ` Matthias Schniedermeyer
2010-07-27 13:06       ` Emmanuel Florac
2010-07-27 13:00     ` Stan Hoeppner
     [not found]   ` <4C4EDEFD.7000401@hardwarefreak.com>
2010-07-27 14:49     ` Matthias Schniedermeyer
2010-07-27 19:59       ` Kinzel, David
2010-07-27 21:02         ` Matthias Schniedermeyer [this message]

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=20100727210204.GA14184@citd.de \
    --to=ms@citd.de \
    --cc=David.Kinzel@encana.com \
    --cc=xfs@oss.sgi.com \
    /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