Bug 25291
Summary: | RAID start-up in rc.sysinit fails if RAID is loaded as a module | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Ben North <ben_north> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | mgalgoci, rvokal, zaitcev |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-08 00:27:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ben North
2001-01-30 11:23:28 UTC
Will be in 5.60-1 ; thanks! I understand the requestor's concern, and they need to be addressed, but, IMHO, the bug was not fixed completely. Old script did have its merit. Consider a scenario: I have an experimental RAID volume, and I do have /etc/raidtab, but normally I boot a kernel without MD support. In that case, "fixed" script goes inside the outer if, then executes all raid start programs (all of them eventually failing), and bombs. I would suggest 1. reverting to the old script; 2. running some sort of modprobe before the test for /proc/mdstat and /etc/raidtab. If that fails, then continue. This way we split out three different results: a missing module [result -> continue] failed RAID [result -> bail to prompt] BTW, Matt has some related problem on devserv, so adding him to cc:. -- Pete Sure, will be changed in 5.71-1 to: # Add raid devices if [ ! -f /proc/mdstat ]; then modprobe md >/dev/null 2>&1 fi if [ -f /proc/mdstat -f /etc/raidtab ]; then ... The fix that Bill posted yesterday works on all my configurations. Personally, I would test -z "$USEMODULES" before running modprobe, and using /sbin/modprobe -- just to be on a safer side. I am far from understanding all issues though, so it's up for Bill to decide. Thanks for the fix! |