oe-lkp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: David Sterba <dsterba@suse.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	<linux-btrfs@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [btrfs]  1d73d634d1: xfstests.btrfs.197.fail
Date: Mon, 12 Feb 2024 23:03:56 +0800	[thread overview]
Message-ID: <202402122244.c5d74821-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "xfstests.btrfs.197.fail" on:

commit: 1d73d634d1268267a5a2b5b1845e48a620ad503c ("btrfs: always scan a single device when mounted")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

[test failed on linux-next/master b1d3a0e70c3881d2f8cf6692ccf7c2a4fb2d030d]

in testcase: xfstests
version: xfstests-x86_64-c46ca4d1-1_20240205
with following parameters:

	disk: 6HDD
	fs: btrfs
	test: btrfs-197



compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 8G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)



If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202402122244.c5d74821-lkp@intel.com



2024-02-09 01:33:38 export TEST_DIR=/fs/sdb1
2024-02-09 01:33:38 export TEST_DEV=/dev/sdb1
2024-02-09 01:33:38 export FSTYP=btrfs
2024-02-09 01:33:38 export SCRATCH_MNT=/fs/scratch
2024-02-09 01:33:38 mkdir /fs/scratch -p
2024-02-09 01:33:38 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4 /dev/sdb5 /dev/sdb6"
2024-02-09 01:33:38 echo btrfs/197
2024-02-09 01:33:38 ./check btrfs/197
FSTYP         -- btrfs
PLATFORM      -- Linux/x86_64 lkp-hsw-d01 6.8.0-rc3-00073-g1d73d634d126 #1 SMP PREEMPT_DYNAMIC Fri Feb  9 09:01:24 CST 2024
MKFS_OPTIONS  -- /dev/sdb2
MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch

btrfs/197       - output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/197.out.bad)
    --- tests/btrfs/197.out	2024-02-05 17:37:40.000000000 +0000
    +++ /lkp/benchmarks/xfstests/results//btrfs/197.out.bad	2024-02-09 01:34:06.449577143 +0000
    @@ -1,25 +1,33 @@
     QA output created by 197
     raid1
    +ERROR: error adding device '/dev/sdb3': Invalid argument
     Label: none  uuid: <UUID>
     	Total devices <NUM> FS bytes used <SIZE>
     	devid <DEVID> size <SIZE> used <SIZE> path SCRATCH_DEV
     	*** Some devices missing
    ...
    (Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/197.out /lkp/benchmarks/xfstests/results//btrfs/197.out.bad'  to see the entire diff)
Ran: btrfs/197
Failures: btrfs/197
Failed 1 of 1 tests



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240212/202402122244.c5d74821-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2024-02-12 15:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202402122244.c5d74821-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).