Bug 5063

Summary: raidtools do not inform user the they >must< use "persistent-superblock 1" in their raids
Product: [Retired] Red Hat Linux Reporter: mrovner
Component: raidtoolsAssignee: Erik Troan <ewt>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0   
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: 2000-02-24 18:12:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description mrovner 1999-09-11 02:15:44 UTC
Since raidadd/raidrun have been replaced with raidstart
and raidstart lacks some of the functionality of starting
raid devices, the user must use "persistent-superblock 1"
for each raid device, or when the raid is stopped,
raidstart will not start it.

All the /etc/raidtab is fine, but without this option in
each raiddev stanze, if you raidstop the device, the
next time I try to raidstart it, I messages in
/var/log/messages of the type:

	kernel: (read) sdc1's sb offset: 8883840 [events: ea5fe76b]
	kernel: md: invalid raid superblock magic on sdc1
	kernel: md: sdc1 has invalid sb, not importing!
	kernel: could not import sdc1!
	kernel: autostart sdc1 failed!
	kernel: huh12?

Simply adding the persistant-superblock removes this
problem.  Without it, the first time you reboot, you lose
your raid.

It would be nice if this were documented as a "must do",
and if it were mentioned in all the sample raidtabs in
/usr/doc/raidtools-0.90, not just raid0.conf.sample in
that direcotory.

Comment 1 Erik Troan 2000-02-24 18:12:59 UTC
This is fixed now.