BERTRAND Joël <[EMAIL PROTECTED]> writes:
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
> 5426 root 15 -5 0 0 0 R 100 0.0 46:32.54
> md_d0_raid5
First: You can tune the stripe cache.
Secondly: You might want the raid speedup patches that implement
prioritized queueing. That reduces the number of incomplete stripes
written to disk and thus speeds up things a lot.
Thirdly: If you have multiple cores then you probably want patches to
multithread the raid5 code. With just one thread it is ultimately cpu
bound and just won't get faster. XORing and maintainance overhead
seems to be awfully cpu intensive.
Fourth: Learn to live with it. Software Raid5/6 is expensive.
> and some process are in D state :
> Root gershwin:[/etc] > ps auwx | grep D
> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
> root 270 0.0 0.0 0 0 ? D Oct27 1:17 [pdflush]
> root 3676 0.9 0.0 0 0 ? D Oct27 56:03 [nfsd]
> root 5435 0.0 0.0 0 0 ? D< Oct27 3:16 [md7_raid1]
> root 5438 0.0 0.0 0 0 ? D< Oct27 1:01 [kjournald]
> root 5440 0.0 0.0 0 0 ? D< Oct27 0:33 [loop0]
> root 5441 0.0 0.0 0 0 ? D< Oct27 0:05 [kjournald]
> root 16442 0.0 0.0 20032 1208 pts/2 D+ 13:23 0:00 iftop
> -i eth2
>
> Why md7_raid is in D state ? Same question about iftop ?
I would say it is just waiting for the underlying devices to finish
some I/O request. And iftop will be in some kernel call waiting for
something or other.
MfG
Goswin
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
