From: Daniel Jacobowitz <dan@debian.org>
To: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
Cc: "'akpm@zip.com.au'" <akpm@zip.com.au>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'devfs@oss.sgi.com'" <devfs@oss.sgi.com>
Subject: Re: Inexplicable disk activity trying to load modules on devfs
Date: Mon, 17 Jun 2002 11:01:08 -0400 [thread overview]
Message-ID: <20020617150108.GA4989@nevyn.them.org> (raw)
In-Reply-To: <6134254DE87BD411908B00A0C99B044F039645EB@mowd019a.mow.siemens.ru>
On Mon, Jun 17, 2002 at 10:59:26AM +0400, Borsenkow Andrej wrote:
> >>
> >> I just booted into 2.4.19-pre10-ac2 for the first time, and noticed
> >> something very odd: my disk activity light was flashing at about
> >> half-second intervals, very regularly, and I could hear the disk
> >> moving. I was only able to track it down to which disk controller, via
> >> /proc/interrupts (are there any tools for monitoring VFS activity?
> >> They'd be really useful). Eventually I hunted down the program causing
> >> it: xmms.
> >>
> >> The reason turned out to be that I hadn't remembered to build my sound
> >> driver for this kernel version. Every half-second xmms tried to open
> >> /dev/mixer (and failed, ENOENT). Every time it did that there was
> >> actual disk activity. Easily reproducible without xmms. Reproducible
> >> on any non-existant device in devfs, but not for nonexisting files on
> >> other filesystems. Is something bypassing the normal disk cache
> >> mechanisms here? That doesn't seem right at all.
> >>
> >
> >
> >syslog activity from a printk, perhaps?
>
> No. It is most probably devfsd trying to load sound modules.
>
> This is exactly the reason Mandrake does not enable devfs in kernel-secure.
> You can badly hit your system by doing in a loop ls /dev/foo for some device
> foo that is configured for module autoloading.
>
> It is very fascist decision; the slightly more forgiving way is to disable
> devfsd module autoloading (or disable devfsd entirely, just run it once
> after all drivers are loaded to execute actions) but then you lose support
> for hot plugging and some people do use kernel-secure on desktops.
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...
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-06-17 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 6:59 Inexplicable disk activity trying to load modules on devfs Borsenkow Andrej
2002-06-17 15:01 ` Daniel Jacobowitz [this message]
2002-06-26 3:38 ` Richard Gooch
2002-06-26 22:03 ` Keith Owens
2002-07-19 0:22 ` Richard Gooch
2002-06-26 3:37 ` Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2002-06-15 22:22 Daniel Jacobowitz
2002-06-15 22:44 ` Andrew Morton
2002-06-15 23:04 ` Daniel Jacobowitz
2002-06-18 17:05 ` Rob Landley
2002-06-17 10:10 ` bert hubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020617150108.GA4989@nevyn.them.org \
--to=dan@debian.org \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=akpm@zip.com.au \
--cc=devfs@oss.sgi.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.