You need
CONFIG_DYNAMIC_DEBUG=y
Then, after you've loaded the module, you can manipulate which dout
callsites are activated. To turn it all on:
echo 'module ceph +p' > /sys/kernel/debug/dynamic_debug/control
echo 'module libceph +p' > /sys/kernel/debug/dynamic_debug/control
echo 'module rbd +p' > /sys/kernel/debug/dynamic_debug/control
I usually turn down the messenger logging so that I only see messages
coming in and going out:
echo 'file net/ceph/messenger.c -p' > /sys/kernel/debug/dynamic_debug/control
echo 'file' `grep -- --- /sys/kernel/debug/dynamic_debug/control | grep ceph \
| awk '{print $1}' | sed 's/:/ line /'` '+p' > /sys/kernel/debug/dynamic_debug/control
echo 'file' `grep -- === /sys/kernel/debug/dynamic_debug/control | grep ceph \
| awk '{print $1}' | sed 's/:/ line /'` '+p' > /sys/kernel/debug/dynamic_debug/control
In general, though, if you're hunting a specific bug you'll probably only
enable the output for the file or functions or whatever you're interested
in!
sage
On Fri, 4 Feb 2011, Brian Chrisman wrote:
> I'm looking to capture some of the douts from the kernel client.
> If someone can instruct me as to what kernel compile flags would be
> needed and which /proc or /sys files need to be twiddled, I'd
> appreciate it, use it, and document it on the wiki.
>
> -Brian
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
