On Mon, Jun 2, 2025 at 1:31 PM Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > > On Thu, May 29, 2025 at 10:50:01AM +0800, Yafang Shao wrote: > > Instead, we propose introducing configurable options to notify users > > of writeback errors immediately and prevent further operations on > > affected files or disks. Possible solutions include: > > > > - Option A: Immediately shut down the filesystem upon writeback errors. > > - Option B: Mark the affected file as inaccessible if a writeback error occurs. > > > > These options could be controlled via mount options or sysfs > > configurations. Both solutions would be preferable to silently > > returning corrupted data, as they ensure users are aware of disk > > issues and can take corrective action. > > I think option A is the only sane one as there is no way to > actually get this data to disk. Do you have a use case for option B? 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. -- Regards Yafang
