similar to: Solution to problem : dynamic variable drops with non-empty dirty list

while trying to use the USDT made available to us in Postgresql database I have problems enabling them. On my database server I ran 1024+ PG processes (1024 clients). The server is a 8 core T2000 @1000MHz. 32GB. 7 storage arrays. Solaris 10 Update 4. Home compiled PG 8.3 beta 1 (optimized binary for T1 chip) with DTrace probes enabled. When running without enabling the probes I have approx 25%

[Mod: linux-kernel removed from To: list. --alex] -----BEGIN PGP SIGNED MESSAGE----- Kernels 2.0.x do not sufficiently allocate space for the internal stack used for garbage collection on unix domain sockets. I have neither examined nor tested 2.1.x kernels. Because the garbage collection system defines a MAX_STACK depth of 1000 for it''s internal use, it is relatively trivial to

Just showing someone how great DTrace is and then we spot something I do not understand. Of course it can be a major misunderstanding of myself. Would appreciate another (expert) look upon this. The goal we try to achieve is trying to get insight if there is a bursty nature in the time slot when system calls are done. Following DTrace snippet is tried: dtrace -q -p 3173 -n

Hello, I''m building some simple monitoring tools to watch zfs storage servers. Is this possible to run dtrace script for example 10 seconds? (Of course it is, I just trying to figure out how). Right know it has to be stopped by "CTRL-C" I''m particulary interested in scripts like iscsiio.d, iscsiwho.d from

Bryan, I''m trying to use a Dtrace script with a modest size global variable and hit a problem. Looking for a solution, I turn to the docs and notice that option "dynvarsize" appears just once in the docs, and it refers you to Chapter 3, where there is no mention. It doesn''t help me anyhow. I have: #!/usr/sbin/dtrace -qws #pragma D option dynvarsize=2000000

I''m trying to time a function within Firefoxwith a pid$target probe [2]. e.g dtrace -Zqw -x dynvarsize=64m -x evaltime=preinit -p 13954 -s menu- construct.d -s sigcont.d elapsed: 12.7942481ms cpu : 7.7911194ms count : 40 times I''m also measuring Firefox startup time by running it arguments like this: ... file:///Users/joelr/work/mozilla/startup/startup.html#`python

Hi Folks, I''m trying to get to grips with dapptrace, running it on my Mac. Everything seems pretty straightforward, except for - of course - what I''m trying to do. I want to focus in on my code but I can''t seem to be able to output just the functions I want, i.e. user functions. The -U option gives everything. Too much of course. Leaving that blank means the

Hello, I need help here about plockstat on X86 platform (Sun X4600 AMD) # plockstat -A -p 20034 plockstat: processing aborted: Abort due to systemic unresponsiveness # plockstat -e 5 -s 10 -A -x bufsize=100k -x aggsize=20m -p 20034 plockstat: processing aborted: Abort due to systemic unresponsiveness # ps -ef | grep 20034 algodev 20034 1 2 07:00:54 ? 86:17

Hi all, We just got a shiny new T5440, and one of the first things I noticed (besides the insane number of hardware contexts), is that dtrace takes 30 seconds to a minute to fire up scripts with 5-6 probes, where our T5220 usually takes under a second. Shutdown is similar, though slightly faster. This is mostly annoying because it takes so long to attach that it''s hard to tell when

Hi Bryan, > Does that sit well with everyone? Seems fine to me. Just revisiting one of Dragan''s points, though (sorry if I missed the answer) - is there a reason for making this global (via a #pragma) rather than, say, simply providing two functions which print in the different orders? e.g. printa() for sort by sample, printak() for sort by key. My reason for wanting to do both in

I am teaching a DTrace class and a student noticed that 2 iosnoop scripts run in two different windows were producing different results. I was not able to answer why this is. Can anyone explain this. Here are the reults from the two windows: # io.d ... sched 0 <none> 1024 dad1 W 0.156 bash 1998

when check java process lock statistics, plockstat failed, please see below: # prstat -mLp 21162 PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWPID 21162 7677 0.9 0.1 0.0 0.0 0.0 99 0.0 0.3 83 89 215 0 java/81 21162 7677 0.3 0.1 0.0 0.0 0.0 0.0 99 0.2 106 33 305 0 java/35 21162 7677 0.1 0.0 0.0 0.0 0.0 100 0.0 0.1 79 6 85 0 java/59

Suppose I have a USDT probe in Firefox and that I''m trying to catch the startup with a probe like this: proc:::exec-success /execname == "firefox-bin"/ { start = timestamp; } and stop tracing when Firefox hits this USDT probe: mozilla:::main-entry { exit(0); } How do I put the running firefox-bin into "trace mode" so that my USDT probe fires? Thanks, Joel

Hello. On a server running 2.4.25, I have the two following errors in the kernel logfile: Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Should I worry about them (disk failure, filesystem damage) ? Thanks. As an addition what does the pair '08:11' means ? Is

On my Debian box: Package: lilo Version: 1:22.2-5 Severity: normal lilo seems to cause a kernel warning (see subject) when / is a ext3 partition. Maybe a kernel problem? Who knows. I'm running 2.4.19-rc1-ac7 -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux hummus 2.4.19-rc1-ac7 #1 Wed Jul 17 22:14:20 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions

Hello, I am not subscribed to this mailing list. My apologies if non-members are not allowed to post in this forum. I have a Linux-2.4.19pre10aa4 computer and I have seen an error message "Unexpected dirty buffer encountered at do_get_write_access:598 (03:05 blocknr 0)" appears in the log. With a little bit of research I found that this message is printed from fs/jbd/journal.c,

In __ocfs2_mark_extent_written, when we meet with the situation of c_split_covers_rec, the old solution just replace the extent record and forget to access and dirty the buffer_head. This will cause a problem when the unwritten extent is in an extent block. So access and dirty it. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/alloc.c | 27 ++++++++++++++++++++++++++- 1 files

Remove ptep_test_and_clear_{dirty|young} from i386, and instead use the dominating functions, ptep_clear_flush_{dirty|young}. This allows the TLB page flush to be contained in the same macro, and allows for an eager optimization - if reading the PTE initially returned dirty/accessed, we can assume the fact that no subsequent update to the PTE which cleared accessed / dirty has occurred, as the

When running autotest with AUTOFEATURE=true, all of my specs and features run fine. However, if I have a feature containing a scenario that fails, autotest lists that feature, but then returns "0 scenarios", and then runs all of the features again. Any idea why this might be? Best, Tom -- Posted via http://www.ruby-forum.com/.

It appears that something about the 4.2.1-rc1 tree is leaving around generated files in a modified state after a build: # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: tools/libxl/libxlu_cfg_y.c # modified: