mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: kernel test robot <oliver.sang@intel.com>, Qu Wenruo <wqu@suse.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org, David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [linus:master] [btrfs] 8af94e772e: xfstests.btrfs.220.fail
Date: Thu, 5 Jun 2025 08:23:34 +0930	[thread overview]
Message-ID: <d188b1ef-5e84-438c-863b-807e534fb67d@gmx.com> (raw)
In-Reply-To: <202506042235.7e3a37da-lkp@intel.com>



在 2025/6/5 00:21, kernel test robot 写道:
> 
> 
> Hello,
> 
> kernel test robot noticed "xfstests.btrfs.220.fail" on:
> 
> commit: 8af94e772ef7bede90895318a3fda6c68a652774 ("btrfs: remove standalone "nologreplay" mount option")

That is fixed by fstests commit: 49170253afef ("fstests: btrfs/220: do 
not use nologreplay when possible"), which is in patches-in-queue branch 
already.

Thanks,
Qu

> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> [test failed on linus/master      7d4e49a77d9930c69751b9192448fda6ff9100f1]
> [test failed on linux-next/master 3a83b350b5be4b4f6bd895eecf9a92080200ee5d]
> 
> in testcase: xfstests
> version: xfstests-x86_64-e161fc34-1_20250526
> with following parameters:
> 
> 	disk: 6HDD
> 	fs: btrfs
> 	test: btrfs-220
> 
> 
> 
> config: x86_64-rhel-9.4-func
> 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/202506042235.7e3a37da-lkp@intel.com
> 
> 2025-06-01 10:11:00 export TEST_DIR=/fs/sdb1
> 2025-06-01 10:11:00 export TEST_DEV=/dev/sdb1
> 2025-06-01 10:11:00 export FSTYP=btrfs
> 2025-06-01 10:11:00 export SCRATCH_MNT=/fs/scratch
> 2025-06-01 10:11:00 mkdir /fs/scratch -p
> 2025-06-01 10:11:00 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4 /dev/sdb5 /dev/sdb6"
> 2025-06-01 10:11:01 echo btrfs/220
> 2025-06-01 10:11:01 ./check btrfs/220
> FSTYP         -- btrfs
> PLATFORM      -- Linux/x86_64 lkp-hsw-d01 6.15.0-rc6-00302-g8af94e772ef7 #1 SMP PREEMPT_DYNAMIC Sun May 18 15:54:12 CST 2025
> MKFS_OPTIONS  -- /dev/sdb2
> MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch
> 
> btrfs/220       [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/220.out.bad)
>      --- tests/btrfs/220.out	2025-05-26 16:25:04.000000000 +0000
>      +++ /lkp/benchmarks/xfstests/results//btrfs/220.out.bad	2025-06-01 10:11:04.131877139 +0000
>      @@ -1,2 +1,5 @@
>       QA output created by 220
>      -Silence is golden
>      +mount: /fs/scratch: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error.
>      +       dmesg(1) may have more information after failed mount system call.
>      +mount -o nologreplay,ro /dev/sdb2 /fs/scratch failed
>      +(see /lkp/benchmarks/xfstests/results//btrfs/220.full for details)
>      ...
>      (Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/220.out /lkp/benchmarks/xfstests/results//btrfs/220.out.bad'  to see the entire diff)
> Ran: btrfs/220
> Failures: btrfs/220
> Failed 1 of 1 tests
> 
> 
> 
> 
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20250604/202506042235.7e3a37da-lkp@intel.com
> 
> 
> 


      reply	other threads:[~2025-06-04 22:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 14:51 kernel test robot
2025-06-04 22:53 ` Qu Wenruo [this message]

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=d188b1ef-5e84-438c-863b-807e534fb67d@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=wqu@suse.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

all inboxes | Powered by JetHome®