> ----- Original Message ----- > From: "Peter Jones" <pjones@xxxxxxxxxx> > To: "ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions" <ataraid-list@xxxxxxxxxx> > Subject: Re: fc5 seek errors - nash mount (built-in) > Date: Wed, 29 Mar 2006 15:43:10 -0500 > > > 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. The errors show up whenever you use nash's internal mount command. I did my test on my custom 2.6.16-rc4-mm1 kernel, in which I compiled my silicon image 680 raid card driver as a module, and moved it out of the /lib/modules/... tree so that I can # insmod siimage.ko at will after booting. (You can't rmmod it at will, once inserted, that driver is marked [permanant] in lsmod (have to reboot to get rid of it). That way, I can avoid the seek errors in the initrd. Another way to avoid them is the kernel command line parameter hde=noprobe, however, dmraid will not work after that because /sys/block/hde is not created. I agree with you that it would be nice if the kernel initialization of the hard disk driver caused only the creation of /sys/block/hde, and didn't mention anything about partitions. However, that does not generate an annoying repetative error like a normal partition scan would. Why would the internal nash mount command be scanning if not using a volume label or when using a filesystem type of proc or ext3? > > -- > Peter > > _______________________________________________ > > Ataraid-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/ataraid-list > -- _______________________________________________ Search for businesses by name, location, or phone number. -Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 _______________________________________________ Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
