I just tried to ktrace a process where the ktrace.out was on an NFS filesystem (v3 TCP mount from a Tru64 4.0F server). The ktrace was _very_ slow and kdump couldn't read it - reporting kdump: bogus length 0xccd6af20 fairly early on. Running the same ktrace to a local filesystem reported no errors. Has anyone else noticed this? -- Peter Jeremy