On Saturday, 12 November 2022 16:44:05 GMT Grant Edwards wrote: > On 2022-11-12, Michael <[email protected]> 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.
Thanks for correcting me, the badblocks man page also makes this clear. Unless an output file is specified, it will only display the list of bad blocks on its standard output. It's been a while since I had to run badblocks and forgot its behaviour. Have your questions been answered satisfactorily by Lawrence's contribution?
signature.asc
Description: This is a digitally signed message part.
