umount /lib/bootchart/tmpfs: Device or resource busy

[Matthew Bauer]

I have added the proper arguments to /boot/grub/menu.lst, but bootchart.tgz is still not created.

Here's the log:

$ dmesg | grep bootchart
Kernel command line: ro root=/dev/sda3 initcall_debug printk.time=y quiet init=/sbin/bootchartd vga=0x037b 3
[ 4.515213] bootchart-collector started as pid 824 with 1 args: '50'
[ 4.515216] bootchart-collector run outside initrd
[ 4.515217] bootchart collector already running as pid 823, exiting...
[ 4.764974] bootchart continuing boot
[ 32.704138] bootchart-collector started as pid 1940 with 2 args: '--dump' '/tmp/bootchart.TdLggrvdT6'
[ 32.704143] bootchart-collector unmounted proc / clean exit
[ 32.704145] umount /lib/bootchart/tmpfs: Device or resource busy

For some reaseon /lib/bootchart/tmpfs is busy?

If I do:
$ sudo umount /lib/bootchart/tmpfs
It succeeds.

How can I fix this?

[Michael Meeks]

Ah ! ignore that warning - that it can't unmount. We are just running two collector processes at once, and it's not a real problem.
Can you confirm that the data is dumped nicely into /tmp/bootchart.TdLggrvdT6 ? [ or whatever it says in dmesg ? ].
I suspect that the root cause of the badness is in the shell piece now - whose errors will not go to dmesg - but may show up in syslog or on your console (did you check there).
if you read /sbin/bootchartd - you see the 'log_header' method ...
Most likely something it calls is missing - and our error toleration is pretty pathetic there. eg do you have 'lsb_release' installed ? :-)

[Michael Meeks]

Hah - ok, so I discovered a truly dumb remote argument parsing mistake that was causing this; and just pushed a fix, can you test with this fix:

commit 6666227
Author: Michael Meeks [e-mail]
Date: Mon Jul 12 15:49:35 2010 +0100

Fix horrible snafus with remote argument parsing...

Thanks :-)

[Matthew Bauer]

Okay, that fixes it. Thanks.