mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Theodore Tso <tytso@mit.edu>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ext3 __log_wait_for_space: no transactions
Date: Fri, 31 Oct 2008 16:45:38 +0200 (EET)	[thread overview]
Message-ID: <Pine.SOC.4.64.0810311634580.26420@math.ut.ee> (raw)
In-Reply-To: <20081031140742.GA17651@mit.edu>

> You'll almost certainly get much better performance if you increase
> your journal size.  I should make the crash go away, too, although I
> would like to figure out what is going on so we can fix it.

OK, but let's fix this first.

> In the meantime, you say this happens nightly.  Can you take a look at
> the time when it normally crashes and see if you can correlate it to
> some cron job activity?  Maybe that will be a hint as to what is
> triggering it.

I had a look but didn't find anything very useful. Will reread the logs 
now... it seems useful though:

Oct 30 09:39:01 rhn /USR/SBIN/CRON[21777]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)

No hangs on Oct 29.

Oct 28 02:39:01 rhn /USR/SBIN/CRON[5459]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)

Oct 27 it did not hang.

Oct 26 14:39:01 rhn /USR/SBIN/CRON[5116]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)

Seems to be a hang at Sunday at daytime when nobody was using it but 
cron daemon.

These are all last lines in syslog before the crash, coming from
/etc/cron.d/php5:09,39 *     * * *     root   [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm
so it runs twice an hour.

-- 
Meelis Roos (mroos@linux.ee)

  reply	other threads:[~2008-10-31 14:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  9:49 Meelis Roos
2008-10-30 14:21 ` Theodore Tso
2008-10-30 20:43   ` Meelis Roos
2008-10-31 14:07     ` Theodore Tso
2008-10-31 14:45       ` Meelis Roos [this message]
2008-10-31 13:39   ` Meelis Roos
2008-11-01  6:54 ` Andrew Morton
2008-11-01  8:56   ` Simon Arlott
2008-11-01  8:59   ` Meelis Roos
2008-11-01 16:38     ` Theodore Tso
2008-11-01 17:10       ` Theodore Tso
2008-11-01 20:21         ` Bartlomiej Zolnierkiewicz
2008-11-04 14:50           ` Theodore Tso
2008-11-04 14:54             ` Meelis Roos
2008-11-04 17:48             ` Bartlomiej Zolnierkiewicz

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=Pine.SOC.4.64.0810311634580.26420@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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

Powered by JetHome