[gentoo-user] Re: e2fsck -c when bad blocks are in existing file?

[Grant Edwards]

On 2022-11-12, Michael <confabulate@××××××××.com> wrote:
> On Wednesday, 9 November 2022 16:53:13 GMT Laurence Perkins wrote:
>
>> Badblocks doesn't ask to write anything at the end of the run.  You
>> tell it whether you want a read test, a write-read test or a
>> read-write-read-replace test at the beginning.
>
> Not to labour the point, but 'e2fsck -v -c' runs a read test and at
> the end it informs me "... Updating bad block inode", even if it
> came across no read errors (0/0/0) and consequently does not prompt
> for a fs repair.

That's _e2fsck_ thats doing the writing at the end, not badblocks. The
statement was that _badblocks_ doesn't ask to write anything at the
end of the run.