[Darshan-users] dxt_analyzer does not provide the data for all the files used in my simulation

Snyder, Shane ssnyder at mcs.anl.gov
Wed Jan 30 18:10:14 CST 2019


Hi Mahzad,

I can think of a few possibilities off the top of my head, but none really strike me as the obvious solution here:

1.) DXT is only supported in the POSIX and MPIIO modules in Darshan currently. So, it should be able to record information on files accessed using MPI-IO routines (MPI_File_open, MPI_FIle_write_all, etc.) or any POSIX calls that operate on file descriptors (open, read/write, etc). It will not record trace data for files accessed using file pointers (FILE *), so things like fopen, fwrite, fread, etc.

2.) Is it possible the file path for the untraced file is in Darshan's list of paths to ignore? I would guess that's not the case, as I'd expect it to be stored along side your other simulation files. Here's the list of paths Darshan is set to ignore:

    "/etc/",
    "/dev/",
    "/usr/",
    "/bin/",
    "/boot/",
    "/lib/",
    "/opt/",
    "/sbin/",
    "/sys/",
    "/proc/",
    "/var/",

3.) Is it possible DXT is running out of trace memory before this particular file is accessed? It will stop tracing new accesses once it's exhausted all memory. You can increase the amount of DXT memory per process by setting the DXT_ENABLE_IO_TRACE variable like you show in your example (i.e., set it to 16 for 16 MiB per process).

Any chance any of those are the issue?

Thanks,
--Shane

On 1/25/19 5:54 PM, Mahzad Khoshlessan via Darshan-users wrote:
Hi all,

I am trying to use dxt_analyzer to get the traces and the OSTs assigned to each of my files during my simulations. When I run dxt_analyzer on my darshan log file the I/O trace file get created. However, I noticed that the report is not complete and does not provide the tracing info on all of my files. I have .XTC file which is my main file and all the data needs to be read are included in this file. I have .psf file and .npz file which is a hidden file and contains the offsets for my .XTC file. I am able to see the tracing report for .psf and .npz files, but nothing for .XTC file which is weird. Does any one know why this is the case? Is not it supposed to report the tracing info for all the files?

I set the following parameters in my submit script before I run my code.

export LD_PRELOAD=/home/mkhoshle/installs/darshan/lib/libdarshan.so:/home/mkhoshle/hdf5/v1.10.1/lib/libhdf5.so
#export LD_PRELOAD=/home/mkhoshle/installs/darshan/lib/libdarshan.so
export DARSHAN_LOGPATH=/oasis/scratch/comet/mkhoshle/temp_project/darshan-logs
export SLURM_NODEFILE=`generate_pbs_nodefile`
export DARSHAN_DISABLE_SHARED_REDUCTION=1
export DXT_ENABLE_IO_TRACE=8


Thanks in advance,



_______________________________________________
Darshan-users mailing list
Darshan-users at lists.mcs.anl.gov<mailto:Darshan-users at lists.mcs.anl.gov>
https://lists.mcs.anl.gov/mailman/listinfo/darshan-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/darshan-users/attachments/20190131/b9b7e48d/attachment.html>


More information about the Darshan-users mailing list