It seems that if you create a software RAID devide (in my case /dev/md0), and create an XFS filesystem on it, fsck.xfs fails because it says it cannot find the device. I noticed it happened when my monitor was disconnected. it did not happen when my monitor was connected… until I disabled KMS. now it happens 100% of the time. I’m assuming the time delay KMS takes when probing for a correct resolution allows the softare RAID device to be created in time for fsck.xfs.
To get around the problem temporarily, I disabled fsck.xfs at boot by making the last 2 entries “0 0” in /etc/fstab.
Is this the correct workaround or a bug? I think there should be a delay for fsck.xfs if it is running on a software RAID device.
> It seems that if you create a software RAID devide (in my case
> /dev/md0), and create an XFS filesystem on it, fsck.xfs fails because
> it says it cannot find the device. I noticed it happened when my
> monitor was disconnected. it did not happen when my monitor was
> connected… until I disabled KMS. now it happens 100% of the time.
> I’m assuming the time delay KMS takes when probing for a correct
> resolution allows the softare RAID device to be created in time for
> fsck.xfs.
>
> To get around the problem temporarily, I disabled fsck.xfs at boot by
> making the last 2 entries “0 0” in /etc/fstab.
>
> Is this the correct workaround or a bug?
Sounds like a bug to me.
> I think there should be a
> delay for fsck.xfs if it is running on a software RAID device.
On 2010-09-05 06:36, jonmdavidson wrote:
>
> It seems that if you create a software RAID devide (in my case
> /dev/md0), and create an XFS filesystem on it, fsck.xfs fails because it
> says it cannot find the device. I noticed it happened when my monitor
> was disconnected. it did not happen when my monitor was connected…
> until I disabled KMS. now it happens 100% of the time. I’m assuming
> the time delay KMS takes when probing for a correct resolution allows
> the softare RAID device to be created in time for fsck.xfs.
>
> To get around the problem temporarily, I disabled fsck.xfs at boot by
> making the last 2 entries “0 0” in /etc/fstab.
>
> Is this the correct workaround or a bug? I think there should be a
> delay for fsck.xfs if it is running on a software RAID device.
The correct workaround would be to add a delay.
You could create an /etc/init.d/boot.delay file and make boot.rootfsck require it - or directly edit
boot.rootfsck. It can be a blind delay, or a wait loop for the appearance of the md device.
If this works, you have very appropriate data to write a bug report in Bugzilla.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
