From: "Rob Mueller" <robm@fastmail.fm>
To: "Chris Mason" <mason@suse.com>, <akpm@osdl.org>
Cc: "Lars Roland" <lroland@gmail.com>,
"Bron Gondwana" <brong@fastmail.fm>,
<linux-kernel@vger.kernel.org>,
"Vladimir Saveliev" <vs@namesys.com>,
"Jeremy Howard" <jhoward@fastmail.fm>
Subject: Re: 2.6.12.2 dies after 24 hours
Date: Wed, 13 Jul 2005 10:50:51 +1000 [thread overview]
Message-ID: <03b601c58744$ee69e390$7c00a8c0@ROBMHP> (raw)
In-Reply-To: 200507122042.11397.mason@suse.com
> 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.
Well we have always mounted our cyrus filesystems with:
noatime,nodiratime,notail
And the problem was occuring all the time with these mount options. We've
since also added on your suggestion nolargeio=1 and used the patch Vladimir
created. I'm not sure which of those fixed the problem, but it definitely
has not occured since we did those last 2 things.
Are you saying that if you mount with noatime *and* use your new patch it
will fix the problem?
What about the 2 threads linked to. Did those end up getting anywhere?
> http://www.ussg.iu.edu/hypermail/linux/kernel/0409.0/2056.html
> http://hulllug.principalhosting.net/archive/index.php/t-22774.html
Rob
next prev parent reply other threads:[~2005-07-13 0:52 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
2005-07-13 0:50 ` Rob Mueller [this message]
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='03b601c58744$ee69e390$7c00a8c0@ROBMHP' \
--to=robm@fastmail.fm \
--cc=akpm@osdl.org \
--cc=brong@fastmail.fm \
--cc=jhoward@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=lroland@gmail.com \
--cc=mason@suse.com \
--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