Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: linux-btrfs@vger.kernel.org
Cc: lkp@01.org, "Huang, Ying" <ying.huang@intel.com>,
	Philip Li <philip.li@intel.com>
Subject: Re: [LKP] [btrfs] "fio: pid=2214, got signal=7" error showed in fio test for btrfs
Date: Wed, 29 Mar 2017 15:50:48 +0800	[thread overview]
Message-ID: <20170329075048.GA300@yexl-desktop> (raw)
In-Reply-To: <20170329073654.GK17604@yexl-desktop>

[-- 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 -

  reply	other threads:[~2017-03-29  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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:50 ` Ye Xiaolong [this message]
2017-05-19  6:28   ` Ye Xiaolong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170329075048.GA300@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=philip.li@intel.com \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox