From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
During the fixating phase, cdrecord eats some system resource that
blocks almost all other activity.  During this period, no processes
can be spawned, but those that were running, eg gkrellm, vi, X,
continue.  A running vi session will do some moving around, but then
will lock up until the fixating is done.  A new command, eg, ls, will
simply block and wait until fixating is over.  Gkrellm shows no
appreciable use of cpu or disk, but a graph of some unknown parameter
in 'proc' rises to a high level.  Top stops completely.

If a DVD is written with only a small amount of data say, 495 MB out
of 4.7 GB, the fixating period lasts a long while - 3:20 m:s and all
this time, nothing else can be done on the system.  When fixating is
done, everything unblocks and goes back to normal behaviour.

Version-Release number of selected component (if applicable):
cdrecord-2.01.1-5

How reproducible:
Always

Steps to Reproduce:
1.  Record some data (a small part of a DVD):
    awk -F '\t' '{ print $2 "=" $2 }' $1 | \ 
    /usr/bin/mkisofs -quiet \
        -R -D -allow-leading-dots -graft-points -allow-multidot \
        -max-iso9660-filenames -relaxed-filenames \
        -path-list -  |
    ( /usr/bin/cdrecord -dao -v driveropts=burnfree fs=16m -eject \
        dev=$CDDEV tsize=${SIZE}s - 2> /dev/null ) | tee -a $LOG

2.  After the data is written, while cdrecord says it is 'fixating',
    try to do some other work.  Run ls, start vi, run ps, etc.

3.  Observe that nothing works.  No new processes will start.
    Observe that gkrellm shows substantially no use of cpu or disk,
    but that 'Proc' shows a graph that rises to an abnormally high 
    value.

Actual Results:  See 3. above.

When fixating is done - more than 3 minutes later - everything
unfreezes.  All pending keystrokes are processed, as expected.

Expected Results:  cdrecord should not block other system activity.

Additional info:

This is at most, inconvenient.  There is no lasting harm done.
Still, it is not normal and should be fixed.

My DVD writer is a PIONEER DVD-RW DVR-105.  I don't recall seeing this
behaviour before FC3.