[linux-lvm] modprobe errors in syslog

[Heinz J. Mauelshagen]

Hi Richard,

this is well known because vgscan(8) checks for a couple of possibly
existing devices.
If they don't exist (i.e. the drivers are not loaded or build into the kernel)
that run triggers (lots of) messages. If you face more of them your actual
kernel configuration might include less drivers than your previous one.

There's 2 ways to address this:

 a. change your modules.conf and set the unused drivers to "off".
 b. ignore the messages ;-)


On Fri, Feb 02, 2001 at 03:09:52PM -0500, Richard Smith wrote:
> I have 2.4.1 patched with .9beta3.  Everything I have tried so far is
> working,
> but I get lots of modprobe errors in my log after I run vgscan. please
> advise,
> is this from md.o or devfs ?  I am not using md.o for raid. 
> 
> thanks
> Richard
> _______________________________________________
> linux-lvm mailing list
> linux-lvm at sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen at Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-