From: Chris Mason <mason@suse.com>
To: "Rob Mueller" <robm@fastmail.fm>, akpm@osdl.org
Cc: "Lars Roland" <lroland@gmail.com>,
"Bron Gondwana" <brong@fastmail.fm>,
linux-kernel@vger.kernel.org,
"Jeremy Howard" <jhoward@fastmail.fm>,
"Vladimir Saveliev" <vs@namesys.com>
Subject: Re: 2.6.12.2 dies after 24 hours
Date: Tue, 12 Jul 2005 20:42:09 -0400 [thread overview]
Message-ID: <200507122042.11397.mason@suse.com> (raw)
In-Reply-To: <039301c58741$a4df9fb0$7c00a8c0@ROBMHP>
On Tuesday 12 July 2005 20:27, Rob Mueller wrote:
> > > We're also applying the attached patch. There's a bug in reiserfs that
> > > gets tickled by our huge MMAP usage (it's amazing what really busy
> > > Cyrus daemons can do to a server, ouch). It's fixed in generic_write,
> > > so we take the few percent performance hit for something that doesn't
> > > break!
> >
> > Interesting - When I got the problem it was on mail servers under high
> > load (handling 60.000 emails pr. hour) with reiserfs as file system. I
> > have seen this problem on 5 different servers so I am confident that
> > it is not hardware failure.
> >
> > Sometimes the server load just rises and then the server dies other
> > times the load rises but the kernel manages to get it back alive
> > filling up syslog with messages like this
>
> Sounds like a different issue. The patch Bron included before fixes (or at
> least reduces to the point where it fixes it for us) a problem where
> processes get stuck in D state and are unkillable. A reboot is required to
> remove them. Apparently this is a known bug in ReiserFS (see messages
> below). As noted, the same bug exists in ext3. There appears to have been
> some patches to try and fix it for both reiserfs and ext3, but I'm not sure
> if they're in the mainline kernel yet.
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0409.0/2056.html
> http://hulllug.principalhosting.net/archive/index.php/t-22774.html
>
There is a much less complex solution that I've just recently gotten working
in the SUSE kernel. If reiser3/ext3 don't log the inode during atime
updates, the problem goes away.
You can solve this now by mounting with -o noatime (although that might not
play well with cyrus, not sure). My current patch works around this in ugly
ways, what I plan on doing during OLS is finding out why ext3 is still
logging the inode all the time.
For reiser3, this was to avoid kswapd having to log a bunch of inodes in
response to memory pressure, but that was back in 2.4 when things were
different. We shouldn't need to do it anymore...
-chris
next prev parent reply other threads:[~2005-07-13 0:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 9:26 2.6.12.2 dies after 24 hours Rob Mueller
2005-07-12 9:43 ` Lars Roland
2005-07-12 11:46 ` Rob Mueller
2005-07-12 12:13 ` Lars Roland
2005-07-12 13:51 ` Bron Gondwana
2005-07-12 16:37 ` Lars Roland
2005-07-13 0:27 ` Rob Mueller
2005-07-13 0:42 ` Chris Mason [this message]
2005-07-13 0:50 ` Rob Mueller
2005-07-13 1:03 ` Chris Mason
2005-07-13 1:27 ` Rob Mueller
2005-07-13 1:00 ` Chris Mason
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=200507122042.11397.mason@suse.com \
--to=mason@suse.com \
--cc=akpm@osdl.org \
--cc=brong@fastmail.fm \
--cc=jhoward@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=lroland@gmail.com \
--cc=robm@fastmail.fm \
--cc=vs@namesys.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