Bug 216229
| Summary: | Same content in two different files - strange problem, unsure if caused by kernel housekeeping | ||
|---|---|---|---|
| Product: | File System | Reporter: | Joerg M. Sigle (joerg.sigle) |
| Component: | ext4 | Assignee: | fs_ext2 (fs_ext2) |
| Status: | RESOLVED INVALID | ||
| Severity: | high | ||
| Priority: | P1 | ||
| Hardware: | AMD | ||
| OS: | Linux | ||
| 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 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | 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 | ||
Found a resolution outside the kernel - content was copied later on through some symlinks. Sorry for the trouble. |
Created attachment 301382 [details] 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.