Re: [LKP] [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
On 03/29, Ye Xiaolong wrote: >Attach kmsg and reproduce script. > >Note: kernel cmdline contained "memmap=104G!4G memmap=104G!132G" Hi, Any feedback about this issue? Thanks, Xiaolong > >Thanks, >Xiaolong > >On 03/29, kernel test robot wrote: >>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=, 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 > > >modprobe nd_e820 >dmsetup remove_all >wipefs -a --force /dev/pmem0 >wipefs -a --force /dev/pmem1 >mkfs -t btrfs /dev/pmem1 >mkfs -t btrfs /dev/pmem0 >mkdir -p /fs/pmem0 >mount -t btrfs /dev/pmem0 /fs/pmem0 >mkdir -p /fs/pmem1 >mount -t btrfs /dev/pmem1 /fs/pmem1 > >for file in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor >do > echo performance > $file >done > >echo ' >[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' | fio --output-format=json - >___ >LKP mailing list >l...@lists.01.org >https://lists.01.org/mailman/listinfo/lkp -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [LKP] [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
Attach kmsg and reproduce script. Note: kernel cmdline contained "memmap=104G!4G memmap=104G!132G" Thanks, Xiaolong On 03/29, kernel test robot wrote: >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=, 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 kmsg.xz Description: Binary data modprobe nd_e820 dmsetup remove_all wipefs -a --force /dev/pmem0 wipefs -a --force /dev/pmem1 mkfs -t btrfs /dev/pmem1 mkfs -t btrfs /dev/pmem0 mkdir -p /fs/pmem0 mount -t btrfs /dev/pmem0 /fs/pmem0 mkdir -p /fs/pmem1 mount -t btrfs /dev/pmem1 /fs/pmem1 for file in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor do echo performance > $file done echo ' [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' | fio --output-format=json -
[LKP] [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
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=, 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
