From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/5 v7] ext4: Speedup orphan file handling
Date: Wed, 25 Aug 2021 18:47:51 -0400 [thread overview]
Message-ID: <YSbIl0FfDCtPJyal@mit.edu> (raw)
In-Reply-To: <20210825161331.GA14270@quack2.suse.cz>
On Wed, Aug 25, 2021 at 06:13:31PM +0200, Jan Kara wrote:
>
> Interestingly, I couldn't make generic/476
> fail for me either with or without my patches so that may be some random
> failure. I'm now running that test in a loop to see whether the failure
> will reproduce to investigate.
On my test infrastructure (using gce-xfstests, which uses 5gig test
and scratch partitions using PD-SSD as the device, 2CPU's, with 7.5 GB
of memory), it's failing 70% of the time in the 1k and orphan_file_1k
case.
Looking through my notes, that's a known failure:
generic/476 1k
Run an all-writes fsstress run with multiple threads to shake out
bugs in the write path.
50% of the time. fsck complaining corrupted file system block
bitmap differences all negative. Possible cause: races loading
adjacent block bitmaps in a single 4k page, leading to bitmap
updates getting lost?
Eric Whitney reports that it's a punch hole bug, where we are
leaking a block or a cluster (in bigalloc); with fixed seed he
can repro reliably at 100%.
- Ted
TESTRUNID: tytso-20210825172314
KERNEL: kernel 5.14.0-rc2-xfstests-00019-g3e5533948c16 #326 SMP Mon Aug 23 22:27:25
EDT 2021 x86_64
CMDLINE: --update-files -c 1k -C 10 generic/476
CPUS: 2
MEM: 7680
ext4/1k: 10 tests, 7 failures, 3399 seconds
generic/476 Failed 327s
generic/476 Failed 348s
generic/476 Failed 344s
generic/476 Pass 343s
generic/476 Pass 335s
generic/476 Failed 348s
generic/476 Failed 341s
generic/476 Failed 335s
generic/476 Failed 345s
generic/476 Pass 333s
Totals: 10 tests, 0 skipped, 7 failures, 0 errors, 3399s
FSTESTIMG: gce-xfstests/xfstests-202108232144
FSTESTPRJ: gce-xfstests
FSTESTVER: blktests 62ec9d6 (Tue, 1 Jun 2021 10:08:38 -0700)
FSTESTVER: e2fsprogs v1.46.4-5-g4cda2545-orphan_file (Sun, 22 Aug 2021 10:07:15 -0400)
FSTESTVER: fio fio-3.27 (Wed, 26 May 2021 10:10:32 -0600)
FSTESTVER: fsverity v1.4 (Mon, 14 Jun 2021 16:14:52 -0700)
FSTESTVER: ima-evm-utils v1.3.2 (Wed, 28 Oct 2020 13:18:08 -0400)
FSTESTVER: nvme-cli v1.14-61-gf729e93 (Fri, 25 Jun 2021 10:21:17 -0600)
FSTESTVER: quota v4.05-40-g25f16b1 (Tue, 16 Mar 2021 17:57:19 +0100)
FSTESTVER: util-linux v2.37 (Tue, 1 Jun 2021 09:52:10 +0200)
FSTESTVER: xfsprogs v5.12.0 (Fri, 21 May 2021 15:53:24 -0400)
FSTESTVER: xfstests-bld 779b6a0 (Mon, 23 Aug 2021 21:29:52 -0400)
FSTESTVER: xfstests linux-v3.8-3295-gddc09fff (Mon, 23 Aug 2021 20:54:57 -0400)
FSTESTCFG: 1k
FSTESTSET: generic/476
FSTESTOPT: count 10 aex
GCE ID: 2585249240830380583
next prev parent reply other threads:[~2021-08-25 22:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 9:57 [PATCH 0/5 v7] ext4: Speedup orphan file handling Jan Kara
2021-08-16 9:57 ` [PATCH 1/5] ext4: Support for checksumming from journal triggers Jan Kara
2021-08-16 9:57 ` [PATCH 2/5] ext4: Move orphan inode handling into a separate file Jan Kara
2021-08-16 9:57 ` [PATCH 3/5] ext4: Speedup ext4 orphan inode handling Jan Kara
2021-08-16 9:57 ` [PATCH 4/5] ext4: Orphan file documentation Jan Kara
2021-08-16 9:57 ` [PATCH 5/5] ext4: Improve scalability of ext4 orphan file handling Jan Kara
2021-08-24 17:14 ` [PATCH 0/5 v7] ext4: Speedup " Theodore Ts'o
2021-08-25 11:30 ` Jan Kara
2021-08-25 16:13 ` Jan Kara
2021-08-25 17:48 ` Theodore Ts'o
2021-08-25 22:13 ` Jan Kara
2021-08-25 22:47 ` Theodore Ts'o [this message]
2021-08-26 14:55 ` Theodore Ts'o
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=YSbIl0FfDCtPJyal@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
/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).