From: kenel test robot <oliver.sang@intel.com>
To: Zizhi Wo <wozizhi@huawei.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-xfs@vger.kernel.org>, <chandan.babu@oracle.com>,
<djwong@kernel.org>, <dchinner@redhat.com>, <osandov@fb.com>,
<john.g.garry@oracle.com>, <linux-kernel@vger.kernel.org>,
<wozizhi@huawei.com>, <yangerkun@huawei.com>,
<oliver.sang@intel.com>
Subject: Re: [PATCH V2] xfs: Make the fsmap more precise
Date: Fri, 16 Aug 2024 12:18:33 +0800 [thread overview]
Message-ID: <202408161111.8e30613b-oliver.sang@intel.com> (raw)
In-Reply-To: <20240808144759.1330237-1-wozizhi@huawei.com>
Hello,
kernel test robot noticed "xfstests.xfs.556.fail" on:
commit: afef0c6f182dcaa5858b95edb6df46b7e4a54824 ("[PATCH V2] xfs: Make the fsmap more precise")
url: https://github.com/intel-lab-lkp/linux/commits/Zizhi-Wo/xfs-Make-the-fsmap-more-precise/20240809-005729
base: https://git.kernel.org/cgit/fs/xfs/xfs-linux.git for-next
patch link: https://lore.kernel.org/all/20240808144759.1330237-1-wozizhi@huawei.com/
patch subject: [PATCH V2] xfs: Make the fsmap more precise
in testcase: xfstests
version: xfstests-x86_64-f5ada754-1_20240812
with following parameters:
disk: 4HDD
fs: xfs
test: xfs-556
compiler: gcc-12
test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (Skylake) with 16G 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/202408161111.8e30613b-oliver.sang@intel.com
2024-08-16 01:01:52 export TEST_DIR=/fs/sda1
2024-08-16 01:01:52 export TEST_DEV=/dev/sda1
2024-08-16 01:01:52 export FSTYP=xfs
2024-08-16 01:01:52 export SCRATCH_MNT=/fs/scratch
2024-08-16 01:01:52 mkdir /fs/scratch -p
2024-08-16 01:01:52 export SCRATCH_DEV=/dev/sda4
2024-08-16 01:01:52 export SCRATCH_LOGDEV=/dev/sda2
2024-08-16 01:01:52 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
2024-08-16 01:01:52 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
2024-08-16 01:01:52 echo xfs/556
2024-08-16 01:01:52 ./check xfs/556
FSTYP -- xfs (debug)
PLATFORM -- Linux/x86_64 lkp-skl-d06 6.11.0-rc1-00007-gafef0c6f182d #1 SMP PREEMPT_DYNAMIC Fri Aug 16 02:37:27 CST 2024
MKFS_OPTIONS -- -f /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
xfs/556 - output mismatch (see /lkp/benchmarks/xfstests/results//xfs/556.out.bad)
--- tests/xfs/556.out 2024-08-12 20:11:27.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//xfs/556.out.bad 2024-08-16 01:02:14.357396417 +0000
@@ -1,12 +1,21 @@
QA output created by 556
Scrub for injected media error (single threaded)
+Corruption: disk offset 106496: media error in unknown owner. (phase6.c line 400)
Unfixable Error: SCRATCH_MNT/a: media error at data offset 2FSB length 1FSB.
SCRATCH_MNT: unfixable errors found: 1
+SCRATCH_MNT: corruptions found: 1
+SCRATCH_MNT: Unmount and run xfs_repair.
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/556.out /lkp/benchmarks/xfstests/results//xfs/556.out.bad' to see the entire diff)
Ran: xfs/556
Failures: xfs/556
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240816/202408161111.8e30613b-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-08-16 4:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 14:47 [PATCH V2] xfs: Make the fsmap more precise Zizhi Wo
2024-08-08 15:29 ` Carlos Maiolino
2024-08-09 0:59 ` Zizhi Wo
2024-08-09 9:09 ` Carlos Maiolino
2024-08-10 0:31 ` Zizhi Wo
2024-08-09 16:22 ` Darrick J. Wong
2024-08-10 0:26 ` Zizhi Wo
2024-08-16 4:18 ` kenel test robot [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=202408161111.8e30613b-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=chandan.babu@oracle.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=osandov@fb.com \
--cc=wozizhi@huawei.com \
--cc=yangerkun@huawei.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