similar to: 2 iosnoop scripts: different results

What''s going on? # dtrace -s iotime_all.d 100 dtrace: failed to enable ''iotime_all.d'': DIF program content is invalid The errant script.... #pragma D option quiet BEGIN { stime = timestamp; io_count = 0; } io:::start /args[2]->fi_pathname != "<none>"/ { start[pid, args[2]->fi_pathname, args[0]->b_edev, args[0]->b_blkno,

I see Intel has released a new tool. Oh, it requires some patches to the kernel to record latency times. Good thing people don''t mind patching their kernels, eh? So who can write the equivalent latencytop.d the fastest? ;-) http://www.latencytop.org/ -- cburgess at qnx.com

Hi there! On a daily backup script, I am getting a lot of these messages: WARNING: <filename> -- update retained (will try again). I've tried googling, but i can't figure out what these messages exactly mean and how i can solve them. Any hint? Thank you Gabriele -- GPG Key Fingerprint: DAD1 E3E3 C3E9 36FB C570 F405 9B5F 7108 A1D0 2FFF

Oeps, forgot the list. > -----Oorspronkelijk bericht----- > Van: L.P.H. van Belle > Verzonden: woensdag 22 mei 2019 16:01 > Aan: 'sambalist at discosucks.it' > Onderwerp: RE: [Samba] Weird Samba/CIFS behavior: client hangs > > Try FQDN in the shares and not \\servername\ that might help. > Most simple to test. > > And OS? > Samba version? >

G''Day Folks, I''ve just rewritten iosnoop so that uses command line arguments (I caved in and used a little Bourne shell for this - hence it''s lost it''s ".d" extension). It''s much more useful now. # iosnoop -h USAGE: iosnoop [-a|-A|-Degstv] [-d device] [-f filename] [-m mount_point] iosnoop # default output

The following script is used as a first attempt to discover IO patterns in a dbase setup: #------------------------------------------------------------------ #pragma D option dynvarsize=128m dtrace:::BEGIN { } pid$target::kaio:entry { self->doit = 1; } pid$target::_aiodone:return { self->doit = 0; } io:::start /self->doit || execname == "oracle"/ {

[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task= ) and "cgtime" (guest time of the task children) fields for the tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to dis= play these new fields. Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net> -- = ------------- Laurent.Vivier@bull.net --------------

[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task= ) and "cgtime" (guest time of the task children) fields for the tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to dis= play these new fields. Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net> -- = ------------- Laurent.Vivier@bull.net --------------

The aim of these four patches is to introduce Virtual Machine time accounting. _Ingo_, as these patches modify files of the scheduler, could you have a look to them, please ? [PATCH 1/4] as recent CPUs introduce a third running state, after "user" and "system", we need a new field, "guest", in cpustat to store the time used by the CPU to run virtual CPU. Modify

The aim of these four patches is to introduce Virtual Machine time accounting. _Ingo_, as these patches modify files of the scheduler, could you have a look to them, please ? [PATCH 1/4] as recent CPUs introduce a third running state, after "user" and "system", we need a new field, "guest", in cpustat to store the time used by the CPU to run virtual CPU. Modify

Dear All, I seem to have stumbled across an AGI problem; I have written an AGI Script (bottom of this email); The script does the following; Makes a CDR entry when called Records the call Updates the CDR Finds a corresponding DNIS from the SMDR table (captured via a serial port logger) Matches up the record and updates the CDR. The script works perfectly in my test lab and has been doing so

Hi, I am profiling some workloads for the voluntary and involuntary context switches. I am interested in finding out the reasons causing these two types of context switches. As far as I understand, involuntary context switch happens on expiration of time slice or when a higher priority process comes in. While the voluntary switch generally happens when a process is waiting for I/O etc. So to

I've tried straight the IP into the share \\x.y.z.k\, same behaviour. The server is smbd 4.7.6 on Ubuntu 18.04. The client is cifs-utils 6.8.2, samba-common 4.10.0 on Ubuntu 19.04 What i get on dmesg is [ 1395.187394] CIFS VFS: Server x.y.z.k has not responded in 120 seconds. Reconnecting... Server's smb.conf: [global] unix extensions = yes case sensitive = auto delete readonly = yes

Hi there! I have a very weird behavior in samba. I have been using a samba server for sharing a folder to a cifs mount client for many years. Since last update, everything still works fine, but when i open a photo subfolder with a specific software (gwenview) and try to load thumbnails, the whole mount stops responding. On the client, i have the "server not responding after 120

On 24/05/2019 10:18, sambalist--- via samba wrote: > I've tried straight the IP into the share \\x.y.z.k\, same behaviour. > > The server is smbd 4.7.6 on Ubuntu 18.04. > The client is cifs-utils 6.8.2, samba-common 4.10.0 on Ubuntu 19.04 > > What i get on dmesg is > [ 1395.187394] CIFS VFS: Server x.y.z.k has not responded in 120 > seconds. Reconnecting... > I

I think a network trace would tell us for use whether the server is responding or not. You can follow the instruction here to make one: https://wiki.samba.org/index.php/Bug_Reporting#cifs.ko -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah

[PATCH 4/8] HVM save restore: vcpu context support Signed-off-by: Zhai Edwin <edwin.zhai@intel.com> save/restore HVM vcpu context such as vmcs diff -r ee20d1905bde xen/arch/x86/domain.c --- a/xen/arch/x86/domain.c Thu Jan 11 16:40:55 2007 +0800 +++ b/xen/arch/x86/domain.c Thu Jan 11 16:46:59 2007 +0800 @@ -573,6 +573,7 @@ int arch_set_info_guest( else {

PATCH 2/4] like for cpustat, introduce the "guest" and "cguest" fields for = the tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to display these new= field Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net> -- = ------------- Laurent.Vivier@bull.net -------------- "Software is hard" - Donald Knuth --------------

PATCH 2/4] like for cpustat, introduce the "guest" and "cguest" fields for = the tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to display these new= field Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net> -- = ------------- Laurent.Vivier@bull.net -------------- "Software is hard" - Donald Knuth --------------

hello anyone faced this error before? dtrace: processing aborted: Abort due to systemic unresponsiveness I used iosnoop -evD > iosnoop.log thanks. __________________________________________________________ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com