From: Luke Dashjr <luke@dashjr.org>
To: Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>
Cc: linux-kernel@vger.kernel.org
Subject: zram corruption
Date: Tue, 1 Feb 2022 02:29:26 +0000 [thread overview]
Message-ID: <202202010229.27088.luke@dashjr.org> (raw)
I use ext4 on zram for my temp directories, and sometimes rarely, things get
corrupted. Using ext4 on a normal disk works fine in the same scenarios.
I haven't managed to figure out what exactly is going on, but I do have a
157 GB strace log of it happening.
One scenario that fairly reliably reproduces it, is building 3 copies of
binutils in parallel. About half the
time, /var/tmp/portage/cross-i686-w64-mingw32/binutils-2.37_p1-r2/work/build/binutils/.deps/stabs.Po
ends up truncated, and one of the builds fails.
The only other scenario I've seen it happen in (much less reproducible), is
running Bitcoin functional tests. In this case, however, the ext4 structure
itself got corrupted, and Linux was unable to recover (the directories
affected became unusable until reboot).
I suspect it's probably a threading-related issue, but it's plausible it could
be page size related (I *think* I'm using 64k pages) though in the latter
case I would expect it to be much more common.
https://bugzilla.kernel.org/show_bug.cgi?id=215557
reply other threads:[~2022-02-01 2:58 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=202202010229.27088.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.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