* [LKP] [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
@ 2017-03-29 7:36 ` kernel test robot
0 siblings, 0 replies; 6+ messages in thread
From: kernel test robot @ 2017-03-29 7:36 UTC (permalink / raw)
To: linux-btrfs; +Cc: lkp, Huang, Ying, Philip Li
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
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
[-- Attachment #2: reproduce.sh --]
[-- Type: application/x-sh, Size: 666 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
@ 2017-03-29 7:36 ` kernel test robot
0 siblings, 0 replies; 6+ messages in thread
From: kernel test robot @ 2017-03-29 7:36 UTC (permalink / raw)
To: lkp
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
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
[-- Attachment #2: reproduce.sh --]
[-- Type: application/x-sh, Size: 627 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [LKP] [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
2017-03-29 7:36 ` kernel test robot
@ 2017-03-29 7:50 ` Ye Xiaolong
-1 siblings, 0 replies; 6+ messages in thread
From: Ye Xiaolong @ 2017-03-29 7:50 UTC (permalink / raw)
To: linux-btrfs; +Cc: lkp, Huang, Ying, Philip Li
[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]
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=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
[-- Attachment #2: kmsg.xz --]
[-- Type: application/octet-stream, Size: 22268 bytes --]
[-- Attachment #3: reproduce --]
[-- Type: text/plain, Size: 627 bytes --]
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 -
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
@ 2017-03-29 7:50 ` Ye Xiaolong
0 siblings, 0 replies; 6+ messages in thread
From: Ye Xiaolong @ 2017-03-29 7:50 UTC (permalink / raw)
To: lkp
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
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=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
[-- Attachment #2: kmsg.xz --]
[-- Type: application/octet-stream, Size: 22268 bytes --]
[-- Attachment #3: reproduce.ksh --]
[-- Type: text/plain, Size: 627 bytes --]
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 -
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [LKP] [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
2017-03-29 7:50 ` Ye Xiaolong
@ 2017-05-19 6:28 ` Ye Xiaolong
-1 siblings, 0 replies; 6+ messages in thread
From: Ye Xiaolong @ 2017-05-19 6:28 UTC (permalink / raw)
To: linux-btrfs; +Cc: lkp
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=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
>
>
>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
>LKP@lists.01.org
>https://lists.01.org/mailman/listinfo/lkp
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
@ 2017-05-19 6:28 ` Ye Xiaolong
0 siblings, 0 replies; 6+ messages in thread
From: Ye Xiaolong @ 2017-05-19 6:28 UTC (permalink / raw)
To: lkp
[-- Attachment #1: Type: text/plain, Size: 2696 bytes --]
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=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
>
>
>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
>LKP(a)lists.01.org
>https://lists.01.org/mailman/listinfo/lkp
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-05-19 6:30 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-29 7:36 [LKP] [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs kernel test robot
2017-03-29 7:36 ` kernel test robot
2017-03-29 7:50 ` [LKP] " Ye Xiaolong
2017-03-29 7:50 ` Ye Xiaolong
2017-05-19 6:28 ` [LKP] " Ye Xiaolong
2017-05-19 6:28 ` Ye Xiaolong
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.