Re: Inexplicable disk activity trying to load modules on devfs

[Keith Owens <kaos@xxxxxxxxxx>]

On Tue, 25 Jun 2002 23:38:48 -0400, 
Richard Gooch <rgooch@xxxxxxxxxxxxxxx> wrote:
>Daniel Jacobowitz writes:
>> For the curious, the reason is that modprobe writes even failed
>> attempts to a log in /var/log/ksymoops, and calls fdatasync() on
>> that file afterwards.  There is no way to disable this without
>> removing that directory, as a design decision.  I don't personally
>> see the point in logging attempts which fail because there is no
>> driver...
>
>Sounds like the behaviour of modprobe needs to be fixed.

People wanted to know what was invoking modprobe and with what
parameters, especially for failed attempts.  The call to fdatasync() is
to "ensure" that the log data hits the disk _before_ the module is
loaded, otherwise debugging data is lost if the module init routine
oopses.