[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: who is r/w-ing my hdd?



Ron Johnson wrote:
On Fri, 2006-01-13 at 12:00 -0600, Mike McCarty wrote:

Matthias Pfeifer wrote:

Jochen Schulz <ml@well-adjusted.de> wrote in news:5unNS-8tn-23@gated-
at.bofh.it:



Matthias:


I am searching the source of some every 2/3 seconds
happening harddisk read/write operation.

If you are using a journalling file system like ext3, this is normal and
shouldn't stress your hard disk.

J.


How is that? And how does that correspond to my
observation that it must be the x-window-system
that is taking a role in this situation? Can
you explain, please?

I find the answer confusing as well. No matter what FS
one is using, it shouldn't be writing the disc unless
someone requests it. The write may be delayed, but it
shouldn't be created out of thin air. Same thing for
reads. Somewhere there is a process doing disc I/O.


You're thinking like this is a single-tasking OS. Even on a relatively quiet system, when you have a journaling FS, the kernel
will be doing more background disk activity than you'd expect.


This response almost makes me angry. I said specifically
A PROCESS. I didn't say what kind of process. The file system
should not generate writes out of nothing. Somewhere there
is A PROCESS (an instance of a running program, maybe a daemon,
maybe the kernel, who cares, some process) which is generating reads
or writes.

I WROTE a multitasking embedded O/S in 1984, and have participated
in writing another, and in supporting two others. So don't lecture
me about thinking single-threaded.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!



Reply to: