Hi;
Now that LVM is in the SGI tree, we would like to
find out if anybody is seeing similar issues
around RAID 5 software support and the complaints
of mount with XFS in the kernel and trying to mount
LVM volumes:
LVM 0.9 (obviously)
2.4.0-test13-pre3 and 2.4.0-prerelease
First, there are two problems we seem to have with
RAID 5 with LVM on top and XFS as the file system.
The first is that the MMX optimization in xor.h
fails and keeps the xor module from even loading
properly (see attached patch to avoid this). Having
gotten around that, we then have a problem with
the rsync daemon. We get a kernel oops (we have not
had time to use kdb on it yet but will) on the
starting the raid, but you can still proceed and
use it. However, it never resyncs nor makes any
progress to resync according to /proc/mdstat. Then,
at shutdown of the raidset (or attempted), the
raid stop hangs. We will give more info as we debug,
but it is 100% reproduceable.
Second, with XFS in the kernel in order to use a root
XFS system, mount (2.10m) complains that the major and/or
minor numbers of the device are incorrect and mount
will not work unless you force it. I believe this is
just a detection issue of mount() with XFS in the kernel
as it works when you force it. umount, however,
complains no matter what even though it does unmount
it.
As we find more information or fixes, we will send
them on to the list. If anyone sees similar issues,
please let us know.
thanks, Scott
raid5_piii_avoid_xor.patch
Description: Binary data
|