From: Christoph Hellwig <hch@infradead.org>
To: Pascal Hambourg <pascal@plouf.fr.eu.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Zheng Qixing <zhengqixing@huaweicloud.com>,
song@kernel.org, yukuai@fnnas.com, linan122@huawei.com,
xni@redhat.com, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, houtao1@huawei.com, zhengqixing@huawei.com
Subject: Re: [RFC v2 0/5] md/raid1: introduce a new sync action to repair badblocks
Date: Tue, 3 Feb 2026 08:30:37 -0800 [thread overview]
Message-ID: <aYIirWALBGrMxmbw@infradead.org> (raw)
In-Reply-To: <40f37494-cf9c-4bc3-aa38-75c76b5d988e@plouf.fr.eu.org>
On Tue, Feb 03, 2026 at 09:08:18AM +0100, Pascal Hambourg wrote:
> On 03/02/2026 à 08:31, Christoph Hellwig wrote:
> > Just curious, but what kind of devices do you see that have
> > permanent bad blocks at a fixed location that are not fixed by
> > rewriting the sector?
>
> I have seen this with several hard disk drives of various brands, even
> though SMART attribute #5 (reallocated sector count) had not reached the
> limit.
Weird. Can you share the models? I'm especially curious if these
are consumer of enterprise drives and of what vintage.
next prev parent reply other threads:[~2026-02-03 16:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 6:12 [RFC v2 0/5] md/raid1: introduce a new sync action to repair badblocks Zheng Qixing
2026-02-03 6:12 ` [RFC v2 1/5] md: add helpers for requested sync action Zheng Qixing
2026-02-03 6:12 ` [RFC v2 2/5] md: serialize requested sync actions and clear stale request state Zheng Qixing
2026-02-03 6:12 ` [RFC v2 3/5] md: rename mdstat action "recovery" to "recover" Zheng Qixing
2026-02-03 6:12 ` [RFC v2 4/5] md: introduce MAX_RAID_DISKS macro to replace magic number Zheng Qixing
2026-02-03 6:12 ` [RFC v2 5/5] md/raid1: introduce rectify action to repair badblocks Zheng Qixing
2026-02-03 7:31 ` [RFC v2 0/5] md/raid1: introduce a new sync " Christoph Hellwig
2026-02-03 8:08 ` Pascal Hambourg
2026-02-03 16:30 ` Christoph Hellwig [this message]
2026-02-03 20:36 ` Pascal Hambourg
2026-02-04 16:59 ` Christoph Hellwig
2026-02-03 8:08 ` Zheng Qixing
2026-02-03 16:31 ` Christoph Hellwig
2026-02-04 9:29 ` Zheng Qixing
2026-02-04 9:32 ` Zheng Qixing
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=aYIirWALBGrMxmbw@infradead.org \
--to=hch@infradead.org \
--cc=houtao1@huawei.com \
--cc=linan122@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=pascal@plouf.fr.eu.org \
--cc=song@kernel.org \
--cc=xni@redhat.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai@fnnas.com \
--cc=zhengqixing@huawei.com \
--cc=zhengqixing@huaweicloud.com \
/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