From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216229] New: Same content in two different files - strange problem, unsure if caused by kernel housekeeping
Date: Sat, 09 Jul 2022 18:22:23 +0000 [thread overview]
Message-ID: <bug-216229-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216229
Bug ID: 216229
Summary: Same content in two different files - strange problem,
unsure if caused by kernel housekeeping
Product: File System
Version: 2.5
Kernel Version: Linux version 5.15.51-i7 (root@think3) (gcc (Debian
8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian)
2.31.1) #1 SMP PREEMPT Thu Jun 30 09:55:14 CEST 2022
Hardware: IA-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext2
Assignee: fs_ext2@kernel-bugs.osdl.org
Reporter: joerg.sigle@jsigle.com
Regression: No
Created attachment 301382
--> https://bugzilla.kernel.org/attachment.cgi?id=301382&action=edit
two consecutively written files on ext2 (by ext4) end up with the same content
when written from the same bash script and ls is not called afterwards from
therein, too
I might have found a problem where two consecutively written files on ext2 (by
ext4) end up with the same content when written from the same bash script - but
NOT if ls is called right thereafter before that same script ends. --- Sounds
strange and possibly scary to me. Might still be a problem of my own, but I
observed it on ext2, and not on ntfs-3g in the same system, and never in many
years before. --- Please see the attached plain text (but better formatted)
description for further information. Thank you.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-07-09 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 18:22 bugzilla-daemon [this message]
2022-07-09 18:22 ` [Bug 216229] Same content in two different files - strange problem, unsure if caused by kernel housekeeping bugzilla-daemon
2022-07-09 18:27 ` bugzilla-daemon
2022-07-09 19:47 ` 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-216229-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).