On Wed, 2006-03-29 at 15:31 -0500, Peter Jones wrote: > > This generates a whole bunch of seek errors on my dmraid drive (hde). > > The internet nash mount function is definately causing the seek errors > > (even in test mode). If you let it find and use /bin/mount it works > > fine and mounts with no seek errors on any drives (only with nash > > --force option, test mode just prints how it parsed the mount command > > line). > > Yup, that's it. nash's mount tries to populate the whole blkid.tab when > you tell it to mount something by device name, just like mount(8) does. ... and actually, you wouldn't see these errors if not for a kernel bug that's happening as well. It's creating partition devices with backing sectors that aren't valid for the disk. That's just plain wrong. Are you seeing these errors after booting, or just during the boot process? If it's the former, they should be pretty harmless, though ugly. -- Peter _______________________________________________ Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
