RAID does not know about "free space" (that is a filesystem thing), so that
would be either some strange interaction between the filesystem and lower
layers, or a measurement error - I guess.
High fragmentation could lead to extra filesystem activity, but that's not
really something the RAID can influence.
>
> I have to notice that this box is rather under heavy load
> (1 GB cvs tree, nfs homes etc.) My question is whether this
> load can depend on available disk space because I do not
> see any suspect processes that can cause such a high load.
>
> Kernel: 2.2.19
> Patches: lfs + md + ide
> RH6.2 + glibc-2.2.12
Please check that your disks are using DMA (hdparm /dev/hdX). You should
see something like:
[root@eagle /root]# hdparm /dev/hda
/dev/hda:
multcount = 16 (on)
I/O support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on) <=========== INDICATES DMA
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 782/128/63, sectors = 6306048, start = 0
Without DMA you will see high CPU load from accessing the disks, regardless of
free space.
-- ................................................................ : jakob@unthought.net : And I see the elder races, : :.........................: putrid forms of man : : Jakob Østergaard : See him rise and claim the earth, : : OZ9ABN : his downfall is at hand. : :.........................:............{Konkhra}...............: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/