Bug 60860 - 2.4.9-24 RAID oops
Summary: 2.4.9-24 RAID oops
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-07 23:12 UTC by Elliot Lee
Modified: 2015-01-04 22:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-30 03:23:39 UTC
Embargoed:

Attachments (Terms of Use)
the raidtab in question. (241 bytes, text/plain)
2002-03-07 23:12 UTC, Elliot Lee 		no flags Details
ksymoops output (5.14 KB, text/plain)
2002-03-07 23:13 UTC, Elliot Lee 		no flags Details
View All

Description Elliot Lee 2002-03-07 23:12:06 UTC 
See attached raidtab and ksymoops report.

I know this appears odd, but I need nested one-device RAID array for testing
purposes, and the kernel just shouldn't oops like this.

kernel is 2.4.9-24
Comment 1 Elliot Lee 2002-03-07 23:12:40 UTC 
Created attachment 47802 [details]
the raidtab in question.
Comment 2 Elliot Lee 2002-03-07 23:13:40 UTC 
Created attachment 47803 [details]
ksymoops output
Comment 3 Elliot Lee 2002-03-07 23:14:50 UTC 
To reproduce, copy the raidtab in place (and modify for local system as needed),
then do:

  mkraid /dev/md0
  mkraid /dev/md1
Comment 4 Arjan van de Ven 2002-03-08 14:25:51 UTC 
Hmm it seems the kernel doesn't like a raid1 of only 1 disk
which architecture is this btw ?
Comment 5 Elliot Lee 2002-03-08 15:30:12 UTC 
It's not a RAID1 of one disk (which seems to work), but a RAID1 of one RAID1 -
the oops only happens after you do the second mkraid.

alpha arch.
Comment 6 Elliot Lee 2003-10-24 17:52:58 UTC 
Please process this old bug.
Note You need to log in before you can comment on or make changes to this bug.