Finding information about nsys-rep file

Hi
I had profiled an application some weeks ago which generated a large qdstrm file. Because of the large RAM usage, I have recently converted it to nsys-rep, but when I run the stat command, it says no information exist.

$ ls -lh nsys_3d-unet.nsys-rep 
-rw-rw-r-- 1 mahmood mahmood 8.2G Oct 10 00:01 nsys_3d-unet.nsys-rep

$ ~/nsight-systems-2022.2.1/bin/nsys stats nsys_3d-unet.nsys-rep 
Using nsys_3d-unet.sqlite for SQL queries.
Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/nvtxsum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain NV Tools Extension (NVTX) data.

Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/osrtsum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain OS Runtime trace data.

Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/cudaapisum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain CUDA trace data.

Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/gpukernsum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain CUDA kernel data.

Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/gpumemtimesum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain GPU memory data.

Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/gpumemsizesum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain GPU memory data.

Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/openmpevtsum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain OpenMP event data.

Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/khrdebugsum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain KHR Extension (KHR_DEBUG) data.

Running [/home/mnaderan/nsight-systems-2022.2.1/target-linux-x64/reports/khrdebuggpusum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain GPU KHR Extension (KHR_DEBUG) data.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/vulkanmarkerssum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain Vulkan Debug Extension (Vulkan Debug Util) data.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/vulkangpumarkersum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain GPU Vulkan Debug Extension (GPU Vulkan Debug markers) data.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/dx11pixsum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain DX11 CPU debug markers.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/dx12gpumarkersum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain DX12 GPU debug markers.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/dx12pixsum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain DX12 CPU debug markers.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/wddmqueuesdetails.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain WDDM context data.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/unifiedmemory.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain CUDA memory transfers data.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/unifiedmemorytotals.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain CUDA memory transfers data.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/umcpupagefaults.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain CUDA Unified Memory CPU page faults data.

Running [/home/mahmood/nsight-systems-2022.2.1/target-linux-x64/reports/openaccsum.py nsys_3d-unet.sqlite]... SKIPPED: nsys_3d-unet.sqlite does not contain OpenACC event data.

How can I find which type of traces exist in the file?

@jkreibich can you please respond to this?

OK. Apparently, the file was corrupted although it contained some data. I was able to run the application on a bigger system and the final qdstrm file was bigger than this 8GB version.

Please delete this topic. Thanks.