Skip to contentSkip to conversation

Inexplicable disk activity trying to load modules on devfs

DISCUSSION Daniel Jacobowitz 4 participants 5 messages Jun 15, 2002 – Jun 18, 2002

lore
Share & tools
lore
#0 lore raw

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.

Signature · 2 lines
Daniel Jacobowitz                           Debian GNU/Linux Developer
MontaVista Software                         Carnegie Mellon University
#1 lore raw
Quoted 9 lines · Daniel Jacobowitz

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.

Quoted 8 lines

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?

-

#2 lore raw
In reply to Daniel Jacobowitz
Quoted 19 lines · Andrew Morton
Quoted 9 lines · Daniel Jacobowitz

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.

Quoted 8 lines

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.

Quoted 1 line

syslog activity from a printk, perhaps?

Nope. No log activity whatsoever.

Signature · 2 lines
Daniel Jacobowitz                           Debian GNU/Linux Developer
MontaVista Software                         Carnegie Mellon University
#3 lore raw
Quoted 18 lines · Daniel Jacobowitz
Quoted 17 lines · Andrew Morton
Quoted 15 lines · Daniel Jacobowitz

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.

Quoted 3 lines
Quoted 1 line

syslog activity from a printk, perhaps?

Nope. No log activity whatsoever.

Updated atime on the /dev/blah node?

Random guess...

Rob

#4 lore raw
In reply to Daniel Jacobowitz
Quoted 3 lines · Daniel Jacobowitz

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

I have a similar problem with the popular 'dig' utility. Running 'dig 2> /dev/null > /dev/null' suffices to cause disk activity, even when run many times in succession.

As far as stracing can tell (dig is multithreaded), there is no reason for this.

Regards,

bert

Signature · 3 lines
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO