From: Chris Worley <worleys@gmail.com>
To: Eric Sandeen <sandeen@redhat.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:19:33 -0600 [thread overview]
Message-ID: <f3177b9e0903171219l2cd6ef84g5416275e999132be@mail.gmail.com> (raw)
In-Reply-To: <49BFE572.9020302@redhat.com>
On Tue, Mar 17, 2009 at 12:01 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> 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?
I'm not able to repeat w/ 2.6.29-rc8.
The system just limps-along, though; SATA doesn't work, Ethernet
doesn't work, and system response is slow... but disk speed is as
expected, and no soft-lockup issues.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-03-17 19:19 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
2009-03-17 19:19 ` Chris Worley [this message]
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=f3177b9e0903171219l2cd6ef84g5416275e999132be@mail.gmail.com \
--to=worleys@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).