On Tue, Jun 03, 2025 at 11:21:46AM +0800, Yafang Shao wrote: > On Tue, Jun 3, 2025 at 11:13 AM Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > > > > On Tue, Jun 03, 2025 at 11:03:40AM +0800, Yafang Shao wrote: > > > We want to preserve disk functionality despite a few bad sectors. The > > > option A fails by declaring the entire disk unusable upon > > > encountering bad blocks—an overly restrictive policy that wastes > > > healthy storage capacity. > > > > What kind of awful 1980s quality storage are you using that doesn't > > remap bad sectors on write? > > Could you please explain why a writeback error still occurred if the > bad sector remapping function is working properly? It wouldn't. Unless you're using something ancient or really really cheap, getting a writeback error means that the bad block remapping area is full. You should be able to use SMART (or similar) to retire hardware before it gets to that state.
