On 12/11/23 20:20, Michael Biebl wrote:
Is expecting a clean "fsck -n -f XXX" run wrong?
Have you tried "fsck.mode=force fsck.repair=yes" as well?
while not suspecting a defect in the manual pages, I tried all
combinations of yes/auto yes/preen. I have also tried rebooting now with
these parameters, and I see the same output in the journal.
Tomorrow I'll try to replicate this on some other machine which I have,
and maybe on a vm if I can figure out how to fake some filesystem error.
Thank you, regards
alessandro
