Thanks Gordon, Guy, Michel and Neil, your advises were very useful. Gordon was right, all raids are still syncing (Bellow part of the /proc/mdstat file). Guy you were right too, the command "uptime" does not display the cpu load directly, sorry about that. Best regards Gilberto ---------------------------------------------------------------------------------------------------------------------------------------------------- Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] [raid10] [faulty] md6 : active raid1 sdk[0] sdl[1] 244190144 blocks [2/2] [UU] [================>....] resync = 83.4% (203849152/244190144) finish=5.0min spee d=131933K/sec md5 : active raid1 sdi[0] sdj[1] 244190144 blocks [2/2] [UU] [================>....] resync = 83.8% (204684480/244190144) finish=5.1min spee d=127124K/sec . . . -------------------------------------------------------------------------------------------------------------------------------------------------------------- Gordon Henderson wrote: >On Mon, 23 Jan 2006, Gilberto Diaz wrote: > > > >> The problem is that the following proccesses are using a lot of cpu >>time. >> >> md1_raid1 >> md1_resync >> ...... >> md6_raid1 >> md6_resync >> >> Here is a sample of the uptime command >> >>17:54:16 up 5:48, 2 users, load average: 5.02, 5.05, 5.26 >> >> Does anybody have an idea what is the problem? Thank a lot in advance >> >> > >to me, it looks like the "problem" is that the RAID system is still >creating the array and syncing all the partitions up. Once it's finished >your system will be idle. > >I bet it's stopped doing it by the time you get this email... What does >the output of > > cat /proc/mdstat > >look like? > >Gordon > > > - 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