Bug 452740 - Kernel crash of Domain-0 while doing multiple dd's on a raid device.
Kernel crash of Domain-0 while doing multiple dd's on a raid device.
Status: CLOSED DUPLICATE of bug 452175
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
i386 Linux
low Severity high
: rc
: ---
Assigned To: Xen Maintainance List
Martin Jenner
Depends On:
  Show dependency treegraph
Reported: 2008-06-24 14:25 EDT by Masoud Sharbiani
Modified: 2008-12-09 16:28 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-12-09 16:28:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Crash log, as captured from ttyS0 (28.50 KB, text/plain)
2008-06-24 14:25 EDT, Masoud Sharbiani
no flags Details

  None (edit)
Description Masoud Sharbiani 2008-06-24 14:25:54 EDT
Description of problem:
I have a Dual P4 Xeon machine (32 bit Xeons), with hyperthreading enabled and 6
gigs of memory, with 6 IDE drives. 4 of these are on a separate controller card,
and setup as a soft raid device /dev/md0, mounted on /data. If I try and run
multiple 'dd if=/dev/zero of=/data', it crashes.

Version-Release number of selected component (if applicable):

How reproducible:
Happens every time.

Steps to Reproduce:
1. Run multiple instances of dd if=/dev/zero of=/data/bigfatfile.$RANDOM on a
2. Reducing the amount of memory available to Domain-0 seems to trigger it sooner.

Actual results:
System crashes.

Expected results:

Additional info:
Comment 1 Masoud Sharbiani 2008-06-24 14:25:54 EDT
Created attachment 310169 [details]
Crash log, as captured from ttyS0
Comment 2 Bill Burns 2008-12-09 16:28:53 EST
Closing this as a duplicate of Bugzilla 452175 as it appears to be the same issue.

*** This bug has been marked as a duplicate of bug 452175 ***

Note You need to log in before you can comment on or make changes to this bug.