Red Hat Bugzilla – Bug 74405
Software RAID partition occasionally mounted as md3 and as ext3 standalone partition
Last modified: 2016-04-18 05:38:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020424
Description of problem:
Customer has three 36GB HDs and has defined software RAID=1 (mirror) for all
file systems. Each fs on sda is mirrored on sdb and sdc. About 50% of time, /var
is mounted as md3 AND as /dev/sda6 causing corruption detection on next reboot.
Workaround was to remove all labels from /etc/fstab. Several reboots later, were
unable to duplicate problem.
See Issue Tracker 7500 for full details.
Bugzilla 70353 was taken out against Milan and appears to be similar problem.
AS rpm is util-linux-2.11f-17.1.i386.rpm.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Customer defined all partitions as mirrored software raid (1) across three
HDs. See attached files for details
2.booting system resulted in df command displaying /dev/md3 as /var and
/dev/sda6 as /var which was one of the mirrored partitions for /var.
3.Writing into this partition as /dev/sda6 caused fsck on reboot.
4.Occurred about 50% of time.
5.Engineering suggested removing all labels from fstab (fstab.new attachment)
and problem appeared to go away.
Actual Results: Per #2 above, booting system resulted in df command displaying
/dev/md3 as /var and /dev/sda6 as /var which was one of the mirrored partitions
Expected Results: Should not be able to mount one partition of a Software Raid
1 as a standalone partition. mount should prevent this from happening as I'm
told 70353 did for Milan.
See attached files -- nothing looks wrong but sda6 was incorrectly mounted about
50% of the time causing an fsck in the following reboot (due to non-matching
Created attachment 76904 [details]
df command output
Created attachment 76905 [details]
fdisk -l output
Created attachment 76906 [details]
Created attachment 76907 [details]
mount command output
Created attachment 76908 [details]
Created attachment 76909 [details]
AS kernel version (uname -a output)
Created attachment 76910 [details]
gahagan/johnson suggested workaround - fstab without LABELs
fstab without labels is the workaround, and the fix is in 8.0.