[Bug 278814] category/port: stress-ng copy-file copy_file_range verify failed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278814

            Bug ID: 278814
           Summary: category/port: stress-ng copy-file  copy_file_range
                    verify failed
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: alessandro.loforte@nozominetworks.com

Tested on two different systems:
System #1
uname -v: FreeBSD 13.3-RELEASE-p1 GENERIC
freebsd-version: 13.3-RELEASE-p2
Latest pkg updates as of May 6th 2024 installed.
Arch: AMD64
Package: stress-ng 0.17.03_2
Tested on File systems: UFS and ZFS

System #2
uname -v: FreeBSD 13.3-RELEASE releng/13.3-n257428-80d2b634ddf0 GENERIC
freebsd-version: 13.3-RELEASE
No pkg updates 
Arch: AMD64
Package: stress-ng 0.17.03_2
Tested on File systems: UFS and ZFS

How to reproduce:

Run:
stress-ng --copy-file 1 --timeout 1m --verify --verbose

I anyhow get various copy-file: copy_file_range verify failed, as per below
example

stress-ng: debug: [9279] invoked with 'stress-ng --copy-file 1 --timeout 1m
--verify --verbose' by user 0 'root'
stress-ng: debug: [9279] stress-ng 0.17.03
stress-ng: debug: [9279] system: FreeBSD freebsd 13.3-RELEASE-p1 FreeBSD
13.3-RELEASE-p1 GENERIC amd64, clang 14.0.5, unknown libc version
stress-ng: debug: [9279] RAM total: 248.6G, RAM free: 222.7G, swap free: 0.0
stress-ng: debug: [9279] temporary file path: '/root', filesystem type: ufs
(28929985 blocks available)
stress-ng: debug: [9279] 48 processors online, 48 processors configured
stress-ng: info:  [9279] setting to a 1 min, 0 secs run per stressor
stress-ng: debug: [9279] CPU data cache: L1: 32K, L2: 1024K, L3: 19712K
stress-ng: debug: [9279] cache allocate: shared cache buffer size: 19712K
stress-ng: info:  [9279] dispatching hogs: 1 copy-file
stress-ng: debug: [9279] starting stressors
stress-ng: debug: [9279] 1 stressor started
stress-ng: debug: [9280] copy-file: [9280] started (instance 0 on CPU 24)
stress-ng: fail:  [9280] copy-file: copy_file_range verify failed, input
offset=183181189, output offset=154836440
stress-ng: fail:  [9280] copy-file: copy_file_range verify failed, input
offset=227829051, output offset=181053085
stress-ng: fail:  [9280] copy-file: copy_file_range verify failed, input
offset=228907811, output offset=133587440
stress-ng: fail:  [9280] copy-file: copy_file_range verify failed, input
offset=66313686, output offset=121081117
stress-ng: fail:  [9280] copy-file: copy_file_range verify failed, input
offset=15248738, output offset=177590895
info: 5 failures reached, aborting stress process
stress-ng: debug: [9280] copy-file: [9280] exited (instance 0 on CPU 5)
stress-ng: error: [9279] copy-file: [9280] terminated with an error, exit
status=2 (stressor failed)
stress-ng: debug: [9279] copy-file: [9280] terminated (stressor failed)
stress-ng: debug: [9279] metrics-check: all stressor metrics validated and sane
stress-ng: info:  [9279] skipped: 0
stress-ng: info:  [9279] passed: 0
stress-ng: info:  [9279] failed: 1: copy-file (1)
stress-ng: info:  [9279] metrics untrustworthy: 0
stress-ng: info:  [9279] unsuccessful run completed in 0.01 secs

-- 
You are receiving this mail because:
You are the assignee for the bug.