Re: 2.4.10ac10, cdrecord 1.9-6, Mitsumi CR-4804TE: lock up burning too large image

[Paul Kreiner]

> Ok. I updated to 1.10 from redhat rawhide, but as said it didn't work at all
> with 2.2 ("failed to mmap /dev/null" or something) so I went back to 1.9. I
> could retry now that I've updated the machine in question to 2.4. (I can
> also see if the 2.2 /dev/null error reproduces if you are interested.) I'll
> retry too large image with 1.10 and report back to you, but I fear it is a
> kernel bug.
 
I believe I ran into this same cdrecord "fail to mmap /dev/null" issue 
before.  The fix (aside from upgrading your kernel to 2.4.x) is to pass 
"fs=0" to cdrecord.  According to the docs, this disables the in-memory FIFO.

Cheers,
Paul Kreiner