From: Frank van Maarseveen <frankvm@frankvm.com>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: 2.6.39: raid1 check blocks jbd on other md more than 120 seconds
Date: Fri, 3 Jun 2011 09:38:01 +0200 [thread overview]
Message-ID: <20110603073801.GA30065@janus> (raw)
In-Reply-To: <BANLkTimzMOo9uGjt-sDWPVBBdzSQaqVTWw@mail.gmail.com>
On Thu, Jun 02, 2011 at 11:46:38AM +0200, Mathias Burén wrote:
> On 2 June 2011 11:36, Frank van Maarseveen <frankvm@frankvm.com> wrote:
> > The system runs FC14 with an (almost) stock 2.6.39 kernel, configured to
> > panic if it seems to hang. That's exactly what started to happen without
> > anything being logged in the normal way except over netconsole.
> >
> > /proc/mdstat:
> > Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
> > md3 : active raid1 sda3[0] sdb3[1]
> > 1885338488 blocks super 1.2 [2/2] [UU]
> >
> > md1 : active raid1 sda1[0] sdb1[1]
> > 33555384 blocks super 1.2 [2/2] [UU]
> >
> > kernel messages:
> > (/etc/cron.weekly/99-raid-check kicks in)
> > Jun 2 04:04:00 janus md: data-check of RAID array md3
> > Jun 2 04:04:00 janus md: delaying data-check of md1 until md3 has finished (they share one or more physical units)
> > Jun 2 04:04:00 janus md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
> > Jun 2 04:04:00 janus md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check.
> > Jun 2 04:04:00 janus md: using 128k window, over a total of 1885338488 blocks.
> > Jun 2 04:55:54 janus INFO: task jbd2/md1-8:1188 blocked for more than 120 seconds.
> [...]
>
> Same behavior if you lower this?
>
> Jun 2 04:04:00 janus md: using maximum available idle IO bandwidth
> (but not more than 200000 KB/sec) for data-check.
Practical bandwidth is usually slightly more than 100MB/s at start
to approximately 60MB/s at the end of the disk. I tried setting
sync_speed_max at 70000kB/s. The problem seems to correlate with the
max. practical bandwidth because at the end of the data-check there were
a couple of hung task messages again, referring to postfix- and other
daemons this time. Timeline:
Jun 2 11:52:30 janus kernel: md: data-check of RAID array md3
Jun 2 11:52:30 janus kernel: md: using maximum available idle IO bandwidth (but not more than 70000 KB/sec) for data-check.
Jun 2 18:48:44 hung task
Jun 2 18:48:44 hung task
Jun 2 18:50:44 hung task
Jun 2 18:50:45 hung task
Jun 2 19:28:45 hung task
Jun 2 19:28:45 hung task
Jun 2 19:34:45 hung task
Jun 2 19:34:45 hung task
Jun 2 19:34:45 hung task
Jun 2 19:34:45 hung task
Jun 2 19:53:29 janus kernel: md: md3: data-check done.
Kernel has been booted with hung_task_panic=0.
--
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-03 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 9:36 2.6.39: raid1 check blocks jbd on other md more than 120 seconds Frank van Maarseveen
2011-06-02 9:46 ` Mathias Burén
2011-06-03 7:38 ` Frank van Maarseveen [this message]
2011-06-03 12:08 ` Thomas Harold
2011-06-03 12:36 ` Frank van Maarseveen
2011-06-07 8:24 ` 2.6.39[.1]: raid1 check blocks jbd on other md more than 120 seconds -- workaround Frank van Maarseveen
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=20110603073801.GA30065@janus \
--to=frankvm@frankvm.com \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.