linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219300] ext4 corrupts data on a specific pendrive
Date: Wed, 25 Sep 2024 16:49:06 +0000	[thread overview]
Message-ID: <bug-219300-13602-61F719fUBr@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 #11 from Theodore Tso (tytso@mit.edu) ---
From the user's perspective, it means that you should stick to well-regarded
hardware manufacturers, and look for reviews on the web for people who complain
about lost data.   Then make sure you buy from a reputable vendor, to avoid
buying fakes where the vendors claims that it comes from a well-regarded
hardware manufacturer, and but it's really a fake where there is only 16GB of
flash to back a claimed 1TB drive, and the moment you write more than 16GB of
data, it start overwriting previously written blocks.

In general, even high quality storage from well-regarded companies (e.g.,
Samsung, WDC, etc.) are not all that expensive --- especially compared to the
value of the user's time, and the value of the user's data.   So trying to save
money by purchasing the cheapest possible storage is just false economy.   In
general, if it's too good to be true.... it probably is.

Finally, if Intenso is a reputable manufacturer, you should be able to file a
warrantee claim and they should be able to replace it with a new storage
device.  If they are not willing to do that.... they probably aren't a
reputable manufacturer.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2024-09-25 16:49 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
2024-09-25 16:49 ` bugzilla-daemon [this message]

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-61F719fUBr@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).