The Release notes for Veritas Storage Foundation state that the reason you cannot do fbt tracing of their vxio driver is because it's text size is larger than 2 MB:
Dynamic Tracing Function Boundary Tracing probes Dynamic Tracing (DTrace) Function Boundary Tracing (FBT) probes are not supported with the vxio driver. This is because of a limitation in Solaris 10 that such probes cannot handle modules with a text size larger than 2MB. The following error message is generated on the console as a result of using DTrace FBT probes with the vxio driver: fbt: WARNING: couldn’t allocate FBT table for module vxio These messages are harmless, and can be safely ignored. Here's the size we come up with for the module: # /usr/ccs/bin/size -f /kernel/drv/sparcv9/vxio 2915048(.text) + 64696(.rodata) + 241920(.rodata1) + 99120(.data) + 79624(.data1) + 6728(.bss) = 3407136 Is there a fix or workaround in the works for this? We're looking to use vxio fbt probes but obviously can't until this is resolved. Asking Symantec to lower the size of their text area is a non-starter. Gordon Marler [EMAIL PROTECTED] -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list [email protected]
