On 27 Feb, Nikita Danilov wrote:
> The rest is not that clear. Probably you workload results in highly
> fragmented file(s). This is consistent with high CPU consumption by
> lookup_extent (http://khack.osdl.org/stp/288741/profile/profile-tick.sort).
>
> If test doesn't delete its working files before exiting, can you execute
>
> measurefs.reiser4 -T /device-with-reiser4
> measurefs.reiser4 -D /device-with-reiser4
>
> and, if number of files on the file system is sane
>
> measurefs.reiser4 -D -E /device-with-reiser4
Sorry this took a couple of days, but you can view the output of those
commands towards the end of the log file here:
http://khack.osdl.org/stp/289045/logs/run-log.txt
You should be able to find the output by searching for the 'measurefs'
commands.
Mark