| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <bug-219300-13602-YGMBAnF0Uu@https.bugzilla.kernel.org/> Date: Tue, 24 Sep 2024 16:15:10 +0000 From: bugzilla-daemon@...nel.org To: linux-ext4@...r.kernel.org Subject: [Bug 219300] ext4 corrupts data on a specific pendrive https://bugzilla.kernel.org/show_bug.cgi?id=219300 --- Comment #10 from nxe9 (linuxnormaluser@...ton.me) --- OK, thanks. You convinced me. @Theodore Tso: Thank you for your detailed post. As I wrote in the first post, i tried f2fs once and it also broke the data. This confirms your claims. I tried the „basic-veryfy.fio“. Unfortunately, this method is not very practical, because in the case of my pendrive, the verification time is about 60 days. After 10 hours I stopped. The progress was less than one percent. Another properly functioning pendrive would also require many days. Perhaps this method would generate an error, but it is very cumbersome. >From the perspective of the average user, this is not a good situation, because you can operate on hardware that is not fully functional, not be fully aware of it and not have an easy and effective method to verify the status of your device. True, you can also buy hardware from a more reputable manufacturer. Unfortunately, there's nothing I can do about it. Well, the only thing I can do is throw this equipment in the trash. Thank you again. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
Powered by blists - more mailing lists