Unable to test samba share

[sanchosk]

• Linux-distro (kernel version): Debian, 6.11.10-amd64
• Desktop Environment (KDE/GNOME etc.): Gnome
• Qt Version: qt5
• KDiskMark Version: 3.1.3
• FIO Version: fio-3.38

Description:

When adding folder from SMB share and starting test, the app asks for admin password and then displays error message

fio: pid=0, err=2/file:filesetup.c:174, func=open, error=No such file or directory

Steps To Reproduce:

• mount samba share in read/write mode
• ensure you can create file in the target directory using both current user and root
• ensure you can delete file using both current user and root
• start kdiskmark
• select the add directory and provide the path to the samba share
• click All
• provide root password

Expected result:
the test will start and run successfully.

Actual result:
Error message:
fio: pid=0, err=2/file:filesetup.c:174, func=open, error=No such file or directory

[sanchosk]

Also tested with .deb version 3.1.4 with the same fio lib, result is the same.

[Arcitec]

Same issue here.

• KDiskMark 3.1.4 on Fedora 41, running natively (not a Flatpak).
• SMB path added via file picker in KDiskMark: /run/user/1000/gvfs/smb-share:server=gl-mt6000.local,share=johnny/benchmark (which is a valid directory and is usable in any normal terminal window).
• Adding the path instantly crashes the application with [1] 59294 floating point exception (core dumped) kdiskmark (no other messages).

I then tried mounting it as an actual directory on disk without GVFS FUSE layer:

sudo mount -t cifs -o username=$USER,password=MYPASSWORD,uid=$USER,gid=$USER //10.0.0.1/johnny ~/netshare

Then I tried using ~/netshare as the path in KDiskMark and got the exact same error as you:

• KDiskMark asks for root password.
• Then it pops up an error with fio: pid=0, err=2/file:filesetup.c:174, func=open, error=No such file or directory.

I guess I'll have to use fio directly myself. That's what KDiskMark uses under the hood.

I noticed that fio does not work on GVFS shares (it says "Operation not supported"), but it works if you mount them manually as CIFS mount points via the command I showed above.

So I did a benchmark with:

$ cd ~/netshare
$ mkdir benchmark
$ fio --name=write_throughput --directory="benchmark" --numjobs=5 \
--size=1G --time_based --runtime=60s --ramp_time=2s --ioengine=libaio \
--direct=1 --verify=0 --bs=1M --iodepth=1 --rw=write \
--group_reporting=1

This works. Unfortunately I don't know what settings KDiskMark would use, so this is not a 1:1 comparison. :)

My most suspicious setting is --iodepth=1 (which requires --direct=1 btw). We run 5 threads/jobs (--numjobs=5) but each job only submits a single request at a time. I think CrystalDiskMark and KDiskMark default to like 8 at a time. But I wasn't sure. And either way, raising the number to 8 or even 64 doesn't change the speed at all for me, so I put it at 1.