All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: dm-devel@redhat.com, LKML <linux-kernel@vger.kernel.org>,
	agk@redhat.com, herbert@gondor.apana.org.au,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [dm-devel] Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
Date: Sat, 01 Mar 2008 16:44:47 +0100	[thread overview]
Message-ID: <47C979EF.7070906@wpkg.org> (raw)

Ritesh Raj Sarraf wrote:

(...)

> Meanwhile I was able to reproduce the bug again with the same configuration 
> and the same scenario. So I believe that the bug can be reproduced 
> consistently.
> 
> Here are the steps:
> 
> 1) Initialize a device using dm-crypt and LUKS
> 2) Create a filesystem on top of it and mount it.
> 3) Write huge amount of data (as a normal user). Something like 150GB.
> 
> As the load goes hight (to something like 12-14), the kernel lock-up is logged 
> into dmesg.
> At that moment, the OS is barely responsive.

I tried to reproduce it on two machines running 2.6.24.2, with cfq 
scheduler.

One machine, with 5x HDD, RAID-5, dm-crypt/LUKS, LVM, ext3 on top of it 
all - I created a 250 GB file, the load was 4-5. No lockups or anything.
Later, removing that 250 GB file took over 7 minutes, but that's a 
different story.


Second machine, dm-crypt on a USB-connected drive, LVM, ext3 on top of 
it, X with nvidia binary blob (version 169.09). I created a 190 GB file, 
the load was indeed pretty high - up to about 14. But still, no lockups 
of any kind.


-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2008-03-01 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01 15:44 Tomasz Chmielewski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-28 13:54 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt Ritesh Raj Sarraf
2008-02-29  7:20 ` Andrew Morton
2008-02-29 18:46   ` [dm-devel] " Alasdair G Kergon
2008-02-29 18:59     ` Ritesh Raj Sarraf
2008-03-01 19:30       ` Milan Broz
2008-03-01 19:33         ` Milan Broz
2008-03-06 14:41           ` Ritesh Raj Sarraf

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=47C979EF.7070906@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    /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.