I have a Scientific Linux build machine:
$ cat /etc/redhat-release Scientific Linux release 6.5 (Carbon)
As a part of our build process, there is an archiving step in which many (hundreds) of object files are archived into a
.a file. During this archiving step which takes about a minute, no other processes can write to disk. Users, for instance, trying to write in their vim sessions during this archiving step hang until the archiving is done.
This happens despite people building with ionice:
ionice -c2 -n7 nice -n19 make -j64 PRETTY=1 <target>
This does seem to be an io issue since the vim sessions (and tmux sessions, and shell sessions, etc.) work fine until a file is written to.
What are the possible bottlenecks that can cause this?