All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Chris Worley <worleys@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Overwriting w/ discard-capable drive causes soft-lockup in ext4 journal code, 2.6.28.8
Date: Tue, 17 Mar 2009 13:01:22 -0500	[thread overview]
Message-ID: <49BFE572.9020302@redhat.com> (raw)
In-Reply-To: <f3177b9e0903171029l13e7dbafyba30ece01172ce6d@mail.gmail.com>

Chris Worley wrote:
> The issue I'm seeing is caused by running this repeatedly on an ext4
> fs (2.6.28.8 kernel) w/ discards enabled (a ram-based MTD device
> contains the fs):
> 
> while `true`
> do  i=0
>      while [ $i -lt 100 ]
>      do dd of=foo"$i" if=/dev/zero bs=1024k oflag=direct &
>           let i=$i+1
>      done
>      wait
> done
> 
> (Note: the loop is intended to fill-up the fs w/ 100 dd threads...
> successive re-runs of the loop will rewrite the same files from
> scratch.)
> 
> ... It causes "soft-lockup" issues on successive iterations,
> immediately as the DD's are launched, as previous foo files get their
> blocks discarded.

I need to find a machine w/ more memory to test on :)  but with a device
of half that size, on 2.6.29-rc7 machine w/ 2 cpus and 2G ram, I'm not
seeing it...

Any chance you can try a 2.6.29-rcX kernel just to double-check?

Thanks,
-Eric

  reply	other threads:[~2009-03-17 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 17:29 Overwriting w/ discard-capable drive causes soft-lockup in ext4 journal code, 2.6.28.8 Chris Worley
2009-03-17 18:01 ` Eric Sandeen [this message]
2009-03-17 19:19   ` Chris Worley

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=49BFE572.9020302@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=worleys@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.