From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 205417] Files corruption ( fs/ext4/inode.c:3941 ext4_set_page_dirty+0x3e/0x50 [ext4] )
Date: Mon, 04 Nov 2019 16:11:51 +0000 [thread overview]
Message-ID: <bug-205417-13602-TOsKyWzmri@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205417-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205417
--- Comment #5 from Ivan Baidakou (the.dmol@gmail.com) ---
Yes, the original message is reproduced every time I boot with 5.3.8
approximately after a few mins boot. I just launch my DE(awesome), Firefox,
Telegram, Claws-mail, and terminal. Actually visually no buggy behavior can be
observed, except the message in /var/log/messages.
The buggy behavior was in Saturnday, when
1. I launched a WarThunder game, which does heavy I/O (I assume it calculates
checksums of files, and if they mismatch, then download new asseets) - it just
hanged.
2. Then I was sure that it is a bug in game, and removed it. A bit later I just
spawned "make -j9" several times simultaneously for the same project (debug,
release, and sanitizer-build) - and when it hanged, I finally payed attention
to the original kernel message.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-11-04 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 13:14 [Bug 205417] New: Files corruption ( fs/ext4/inode.c:3941 ext4_set_page_dirty+0x3e/0x50 [ext4] ) bugzilla-daemon
2019-11-04 14:32 ` [Bug 205417] " bugzilla-daemon
2019-11-04 14:52 ` bugzilla-daemon
2019-11-04 14:55 ` bugzilla-daemon
2019-11-04 15:55 ` bugzilla-daemon
2019-11-04 16:11 ` bugzilla-daemon [this message]
2019-11-04 16:12 ` bugzilla-daemon
2019-11-05 21:12 ` bugzilla-daemon
2019-12-18 12:52 ` bugzilla-daemon
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=bug-205417-13602-TOsKyWzmri@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).