All of lore.kernel.org
 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: Sun, 22 Sep 2024 18:58:25 +0000	[thread overview]
Message-ID: <bug-219300-13602-UsHqyJUA0o@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219300-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219300

Artem S. Tashkinov (aros@gmx.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Artem S. Tashkinov (aros@gmx.com) ---
> [11844.111565] Buffer I/O error on device sdb1, logical block 7533568 
> EXT4-fs (sdb1): I/O error while writing superblock 

Typically, such errors indicate a storage failure, not a filesystem problem.

I strongly suspect your media is broken or damaged and should not be used to
store important information.

The easiest way to test it would be to use badblocks with a single pass, using
the `-w     Use write-mode test` option.

The defaults for -b and -c are quite low, I'd suggest:

sudo badblocks -b 4096 -c 1000 -w -s -v /dev/sdX

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

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

  reply	other threads:[~2024-09-22 18:58 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 ` bugzilla-daemon [this message]
2024-09-22 18:59 ` [Bug 219300] " 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

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-UsHqyJUA0o@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.