-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> David, unless you have mdadm running in monitor mode, its not "actively" >> in memory.. the MD driver is in the kernel, and in memory. Mdadm is >> simply a tool, just as fsck.ext2 or such.. its not active until you run >> it, and leaves memory when it finishes its one task. (Someone correct >> me if I'm wrong please....). > >> Tyler. Well, perhaps you can point me in the right direction. I've got lots of slab usage by 47061 47030 99% 0.05K 581 81 2324K buffer_head and I'm just trying to find out what's eating the ram on my computer. It's got to be somehow connected to the md device that I'm using. because this doesn't exist on any of my other computers that have a 2.6 kernel on them. Only the one with the mdadm created RAID array. I'm not saying that it's mdadm, but perhaps some aspect of the md "system". thanks for your time, - -- David Kowis ISO Team Lead - www.sourcemage.org SourceMage GNU/Linux One login to rule them all, one login to find them. One login to bring them all, and in the web bind them. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFCz1CAtgErhgxHMHsRAmmXAJ4r0GXFKlTIKm++VW4aT+jklCvr2gCdEcXg 1lkWtJZ8AXE+M3kKTadiNdM= =HVOK -----END PGP SIGNATURE----- - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
