Public bug reported:
Under 16.04 I ran run:
$ stap nfsd-trace.stp
Mon Oct 1 19:48:05 2018 PDT 10.22.7.20:50434 nfsd.proc4.lookup grep
/export/1/blank/build.2018-08-22/bin/grep
Works great.
Under 18.04 I tried:
# stap nfsd-trace.stp
semantic error: while processing probe
module("nfsd").function("nfsd4_lookup@/build/linux-lZKWha/linux-4.15.0/fs/nfsd/nfs4proc.c:735").call
from: nfsd.proc4.lookup from: nfsd.proc.lookup from: nfsd.proc.entries from:
nfsd.proc.entries
The kernel being used:
Linux nas-7-0 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
I thought I might need a newer systemtap, so I installed it from git on Sept
27th 2018. So the same run:
/share/apps/systemtap-2018-09-27# ./bin/stap
./share/systemtap/examples/network/nfsd-trace.stp
semantic error: while processing probe
module("nfsd").function("nfsd4_read@/build/linux-lZKWha/linux-4.15.0/fs/nfsd/nfs4proc.c:744").call
from: nfsd.proc4.read from: nfsd.proc.read from: nfsd.proc.entries from:
nfsd.proc.entries
Other scripts like iostats.stp work as expected.
So basically from what I can tell the neither the ubuntu provided
systemtap, nor the upstream systemtap works with the widely circulated
nfsd-trace.stp file. It's been available from redhat's documentation as
well as part of the upstream source under examples.
I expected the 18.04 result of "stap nfsd-trace.stp" to be much like the
16.04 result. Showing a log of NFS related I/O, path names, time
stamps, etc.
Other NFS related scripts like nfsd-recent.stp works.
** Affects: systemtap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795545
Title:
Systemtap incompatible with ubuntu 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1795545/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
