From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219300] ext4 corrupts data on a specific pendrive
Date: Tue, 24 Sep 2024 16:15:10 +0000 [thread overview]
Message-ID: <bug-219300-13602-YGMBAnF0Uu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219300-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219300
--- Comment #10 from nxe9 (linuxnormaluser@proton.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.
next prev parent reply other threads:[~2024-09-24 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 15:47 [Bug 219300] New: ext4 corrupts data on a specific pendrive bugzilla-daemon
2024-09-22 18:58 ` [Bug 219300] " bugzilla-daemon
2024-09-22 18:59 ` bugzilla-daemon
2024-09-23 1:35 ` bugzilla-daemon
2024-09-23 1:39 ` bugzilla-daemon
2024-09-23 6:26 ` bugzilla-daemon
2024-09-23 7:07 ` bugzilla-daemon
2024-09-23 16:24 ` bugzilla-daemon
2024-09-23 16:30 ` bugzilla-daemon
2024-09-23 18:53 ` bugzilla-daemon
2024-09-24 16:15 ` bugzilla-daemon [this message]
2024-09-25 16:49 ` 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-219300-13602-YGMBAnF0Uu@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).