Bug 122135

Summary: unable to anonymously mmap 67108864
Product: [Applications] k3b Reporter: Andrea Cimitan <cimi86>
Component: generalAssignee: Sebastian Trueg <trueg>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: success??? not really

Description Andrea Cimitan 2006-02-17 00:12:28 UTC
Version:           0.12.11-0.12.12 (using KDE KDE 3.5.1)
Installed from:    Unlisted Binary Package
Compiler:          gcc version 4.0.3 20051222 (prerelease) Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.0-20051222/configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --prefix=/usr --enable-shared --enable-languages=c,c++,objc --enable-threads=posix --enable-__cxa_atexit
Thread model: posix
OS:                Linux

(Archlinux) I've found this bug writing 4GB DVD. K3b stops with this error

-----------------------
K3b Version: 0.12.12

KDE Version: 3.5.1
QT Version: 3.3.5
Kernel: 2.6.16-rc3
Devices

[...]

Size of filesystem calculated: 2296251

growisofs: 6.1

growisofs
-----------------------
:-( unable to anonymously mmap 67108864: Resource temporarily unavailable
-----------------------
[...]

The only change to burn is to launch "ulimit -l unlimited" from superuser and then burn with root...
Tested kernels: 2.6.15, 2.6.15.2, 2.6.16-rc3
Tested k3b: 0.12.9, 0.12.10, 0.12.11, 0.12.12.

The bug reproduce only with  0.12.11 - 0.12.12.
Comment 1 Sebastian Trueg 2006-02-17 00:45:24 UTC
not a k3b bug.
see http://fy.chalmers.se/~appro/linux/DVD+RW/
Comment 2 Andrea Cimitan 2006-02-20 13:20:27 UTC
It is a k3b bug because I'm able to burn successefully with 0.12.9 and 0.12.10 version!!!!
Comment 3 Andrea Cimitan 2006-02-20 13:21:34 UTC
*with same dvd+rw-tools obviusly...
Comment 4 Sebastian Trueg 2006-02-20 16:05:29 UTC
Again: this is not a K3b bug. The problem is that K3b uses a higher default writing buffer than growisofs, namely 40 MB.
You seem to have configured 60 MB. So it could even be called a user problem.
K3b 0.12.10 and below do not set the buffer size in growisofs >= 6.0, so in those cases you get your default 30MB.
Comment 5 Andrea Cimitan 2006-02-20 19:16:49 UTC
Thank you!!! finally a good answer... and how I can set different writing buffer?
Comment 6 Sebastian Trueg 2006-02-21 02:36:26 UTC
k3b settings -> advanced -> manual writing buffer
Comment 7 bogdan 2006-03-12 15:12:53 UTC
I got this too:
:-( unable to anonymously mmap 33554432: Resource temporarily unavailable
I tried to set the maual buffer to various sizes, but it didn't work for me.

What value should I set it to 

I solved the issue by issuing "ulimit -l unlimited" before starting k3b, but I think I need a more elegant way.

Regards,
Bogdan
Comment 8 bogdan 2006-03-12 15:17:24 UTC
I have very new kernel.

I found this link which explains the issue:

http://lists.debian.org/cdwrite/2006/01/msg00077.html
Comment 9 Marijn Schouten 2006-10-04 18:49:53 UTC
This bug is still biting me. I'm using k3b-0.12.17 and dvd+rw-tools-6.1-r1 which are apparently (still?) the culprit. It would be nice if the workaround we need to set anyway could be the standard. 
Comment 10 Marijn Schouten 2006-10-04 18:51:56 UTC
Created attachment 18014 [details]
success??? not really

Also k3b happily reports success when it has failed and done nothing.
Comment 11 Marijn Schouten 2006-10-05 10:27:13 UTC
I retract my previous statement that k3b reports success when it has actually not written anything. It seems it is possible to write 3GB onto a DVD+RW in a few seconds. I've not confirmed that it does or doesn't write when it fails to mmap, but reports success.
Comment 12 Sebastian Trueg 2006-10-30 13:50:37 UTC
how about growisofs 7.0?
Comment 13 Peter Lemieux 2006-11-09 17:30:26 UTC
I found changing the ulimit as described in Andy Polyakov's message cited above http://lists.debian.org/cdwrite/2006/01/msg00077.html fixed this problem.  For a permanent fix, add the command "ulimit -l unlimited" to ~/.bashrc.

Because modern kernels can require K3b to run with root privileges, I made the change to /root/.bashrc.  I've edited the launchers for K3b to run the program as root.

Of course, none of these problems are intrinsic to K3b.  They reflect issues with the hardware, kernel, and burning programs K3b invokes.  See, for instance, 
http://lkml.org/lkml/2004/8/19/173.