linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: linux-btrfs@vger.kernel.org, wqu@suse.com, lkp@01.org
Subject: Re: [lkp-robot] [btrfs] d1f6ad52c3: BTRFS error (device md0): SUPER_FLAG_CHANGING_FSID is set
Date: Thu, 18 Jan 2018 11:34:42 +0800	[thread overview]
Message-ID: <e105cef6-6fef-71fb-4736-0ae7f6f916cc@oracle.com> (raw)
In-Reply-To: <20180117124559.GB3474@yexl-desktop>


This seems to have picked up wrong patch for testing, it should use [1],
a set of 3 patches.

[1]
   [PATCH V4 0/3] Add missing flags in the kernel

Thanks, Anand

On 01/17/2018 08:45 PM, kernel test robot wrote:
> 
> FYI, we noticed the following commit (built with gcc-7):
> 
> commit: d1f6ad52c3f93a9da45e11001e0a0be8f3c31e9e ("btrfs: add support for SUPER_FLAG_CHANGING_FSID in btrfs.ko")
> url: https://github.com/0day-ci/linux/commits/Anand-Jain/btrfs-add-missing-BTRFS_SUPER_FLAG-define/20180109-041023
> base: https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git next
> 
> in testcase: aim7
> with following parameters:
> 
> 	disk: 4BRD_12G
> 	md: RAID1
> 	fs: btrfs
> 	test: disk_src
> 	load: 500
> 	cpufreq_governor: performance
> 
> test-description: AIM7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of multiuser system.
> test-url: https://sourceforge.net/projects/aimbench/files/aim-suite7/
> 
> 
> on test machine: 40 threads Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz with 384G memory
> 
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> 
> [   25.285253] BTRFS error (device md0): SUPER_FLAG_CHANGING_FSID is set
> [   25.285255] BTRFS error (device md0): superblock contains fatal errors
> 
> 
> To reproduce:
> 
>          git clone https://github.com/intel/lkp-tests.git
>          cd lkp-tests
>          bin/lkp install job.yaml  # job file is attached in this email
>          bin/lkp run     job.yaml
> 
> 
> 
> Thanks,
> Xiaolong
> 

           reply	other threads:[~2018-01-18  3:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20180117124559.GB3474@yexl-desktop>]

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=e105cef6-6fef-71fb-4736-0ae7f6f916cc@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=wqu@suse.com \
    --cc=xiaolong.ye@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;
as well as URLs for NNTP newsgroup(s).