public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: High latencies writing to a memory mapped file
Date: Tue, 27 Jul 2010 16:49:14 +0200	[thread overview]
Message-ID: <20100727144914.GA29349@citd.de> (raw)
In-Reply-To: <4C4EDEFD.7000401@hardwarefreak.com>

On 27.07.2010 08:28, Stan Hoeppner 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).
> 
> Can you supply any kinda of empirical data or logging that would suggest the
> problem lies with XFS?  You've not given us much to go on except anecdote.
> 
> Google "linux server hangs" and you'll find thousands of causes and solutions.

The "best" further anecdote i have is:
I cloned(*) the server, on identical hardware (ignoring HDDs), for 
someone else with 2 major differences.
- no loop-aes, as they didn't need encryption.
- ext4 instead of xfs

That machine has currently an uptime of 180 days and i don't have a 
single report of a "hang". (Which technically doesn't mean that the 
machine doesn't have that same bug. Only that no one ever complained to 
me)

For empirical data: I don't know how or where to start.



*:
In the best sense of the word.
As the first step i 'rsync'ed the "system"-HDD of our server to a new 
HDD. ...


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

  parent reply	other threads:[~2010-07-27 14:46 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 [this message]
2010-07-27 19:59       ` Kinzel, David
2010-07-27 21:02         ` Matthias Schniedermeyer

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=20100727144914.GA29349@citd.de \
    --to=ms@citd.de \
    --cc=stan@hardwarefreak.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