Re: [RFC v2 0/5] md/raid1: introduce a new sync action to repair badblocks

Next message: Rafael J. Wysocki: " [PATCH v1] PM: sleep: core: Clear device async state upfront during suspend"
Previous message: Laurent Pinchart: "Re: [RFC PATCH] media: Virtual camera driver"
In reply to: Christoph Hellwig: "Re: [RFC v2 0/5] md/raid1: introduce a new sync action to repair badblocks"
Next in thread: Christoph Hellwig: "Re: [RFC v2 0/5] md/raid1: introduce a new sync action to repair badblocks"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Pascal Hambourg

Date: Tue Feb 03 2026 - 15:37:28 EST

On 03/02/2026 at 17:30, Christoph Hellwig wrote:

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.

I did not keep track of the models and do not remember them, it was a long time ago. They were mostly hard disk drives from Dell and HP professional desktop and laptop series, so consumer grade I guess, manufactured around 2010.