Hi, We detected below error messages in fio pmem test for btrfs.
machine: Intel(R) Xeon(R) CPU E5-2695 v3 @ 2.30GHz with 256G memory kernel: v4.10 test parameters: [global] bs=2M ioengine=mmap iodepth=32 size=7669584457 direct=0 runtime=200 invalidate=1 fallocate=posix group_reporting time_based [task_0] rw=write directory=/fs/pmem0 numjobs=14 [task_1] rw=write directory=/fs/pmem1 numjobs=14 ==> /tmp/stderr <== fio: pid=2214, got signal=7 fio: pid=2215, got signal=7 fio: pid=2217, got signal=7 fio: pid=2220, got signal=7 fio: pid=2222, got signal=7 fio: pid=2224, got signal=7 fio: pid=2225, got signal=7 fio: pid=2227, got signal=7 fio: pid=2216, got signal=7 fio: pid=2218, got signal=7 fio: pid=2219, got signal=7 fio: pid=2221, got signal=7 fio: pid=2223, got signal=7 fio: pid=2226, got signal=7 fio: pid=2200, got signal=7 fio: pid=2201, got signal=7 fio: pid=2203, got signal=7 fio: pid=2204, got signal=7 fio: pid=2205, got signal=7 fio: pid=2208, got signal=7 fio: pid=2209, got signal=7 fio: pid=2210, got signal=7 fio: pid=2211, got signal=7 fio: pid=2212, got signal=7 fio: pid=2213, got signal=7 fio: pid=2202, got signal=7 fio: pid=2206, got signal=7 fio: pid=2207, got signal=7 fio: file hash not empty on exit while fio test is ok for ext4 with the same test parameters. Attached reproduce.sh may help reproduce the problem. Thanks, Xiaolong
reproduce.sh
Description: Bourne shell script
