mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baruch Even <baruch@ev-en.org>
To: Fabio Coatti <fabio.coatti@wseurope.com>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	Simone Piunno <simone.piunno@wseurope.com>,
	linux-kernel@vger.kernel.org
Subject: Re: bonnie++ uninterruptible under heavy I/O load
Date: Fri, 11 Mar 2005 13:29:17 +0000	[thread overview]
Message-ID: <42319D2D.7060402@ev-en.org> (raw)
In-Reply-To: <200503111420.52890.fabio.coatti@wseurope.com>

Fabio Coatti wrote:
> Alle 12:35, venerdì 11 marzo 2005, Denis Vlasenko ha scritto:
> 
>>>Unresponsiveness is not 2.6.11 specific (we've seen the same thing on
>>>2.6.10 and 2.6.8), not I/O scheduler specific ("as" and "deadline" behave
>>>the same) and not CPU/SMP specific (reproduced on single P4 HT and single
>>>P3), but only on these two DL585 servers we've seen bonnie++ resisting
>>>kill -9 for tens of seconds.
>>>
>>>Of course on request I can provide any other useful info.
>>>Any help is appreciated.
>>
>>I think Alt-SysRq-T will be interesting to see
> 
> Unfortunately this machine is on a remote location, so we don't have access to 
> keyboard. In some days we will be able to have a report of Alt-SysRq-T, but 
> until this  of course we can provide any information that can be gathered on 
> a remote shell.

echo t > /proc/sysrq-trigger

will do the job equivalently.

Baruch


  reply	other threads:[~2005-03-11 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 11:08 Simone Piunno
2005-03-11 11:35 ` Denis Vlasenko
2005-03-11 13:20   ` Fabio Coatti
2005-03-11 13:29     ` Baruch Even [this message]
2005-03-11 14:14       ` Simone Piunno
2005-03-11 15:16         ` Jens Axboe
2005-03-11 15:50           ` Fabio Coatti
2005-03-11 15:54             ` Jens Axboe
2005-03-11 15:58               ` Simone Piunno
2005-03-11 16:00                 ` Jens Axboe
2005-03-11 16:24                   ` Simone Piunno
2005-03-11 14:24 Christian Guggenberger

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=42319D2D.7060402@ev-en.org \
    --to=baruch@ev-en.org \
    --cc=fabio.coatti@wseurope.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simone.piunno@wseurope.com \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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

all inboxes | Powered by JetHome®