With the latest CVS version of PVFS2, you can dynamically modify the
kernel or client debug mask. Here is how it works:
After loading the kernel module and starting the client-core, you can view
the current values of either mask by issuing a 'cat' on
/proc/sys/pvfs2/kernel-debug or /proc/sys/pvfs2/client-debug. To modify
either mask, you must "write" a debug string to
/proc/sys/pvfs2/kernel-debug or client-debug. The easiest way is by using
'echo'. For
example:
echo "io,permissions" > /proc/sys/pvfs2/client-debug
echo "file,dcache" > /proc/sys/pvfs2/kernel-debug
If you can't remember which keywords work with each debug mask, issue a
'cat' on /proc/sys/pvfs2/debug-help....it's crude but you get the basics.
If you happen to type in a keyword that does not work for the intended
mask, that keyword is stripped from the list and ignored when converting
from a string to a number.
Anytime either debug mask is modified, an informational message is written
to /var/log/messages, displaying the human readable string and the numeric
mask value.
Anytime you start the client-core, it will overwrite the values of both
debug masks based on the environment variables PVFS2_DEBUGMASK and
PVFS2_KMODMASK. Thus, if they are not defined, kernel-debug and
client-debug will show "none" as their current value. NOTE: the strings
from the environment variables are also edited and will ignore keywords
that don't belong.
Let me know if you have any trouble with the new debugging functionality.
Becky
--
Becky Ligon
PVFS Developer
Clemson University
864-656-3865
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
