FreeBSD-provided disk images: problems with UFS, fsck_ufs (fsck_ffs(8)); partition sizes …

Where fsck repairs a file system and marks it clean: is there any situation in which it's normal for an immediately subsequent run of fsck to mark it dirty?
 
If the file system has not been mounted or modified in between, then the second run should not mark it dirty. If the file system *IS* mounted during the time of the two fsck runs, things get very complicated; it's not easy to define what "clean" or "dirty" mean on a mounted file system.
 

Bug 256746 is closed, fixed. Commits:
  1. <https://cgit.freebsd.org/src/commit/?id=0c5a59252c8e7b80b98521ebc23a415a05ff9594&h=main> (main)
  2. <https://cgit.freebsd.org/src/commit/?id=fb2feceac34cc9c3fb47ba4a7b0ca31637f8fdf0&h=stable/13> (stable/13)

<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256746#c8>

… The next engineered release will be 13.1 which will contain this change.



If the file system has not been mounted or modified in between, then the second run should not mark it dirty. …

<https://lists.freebsd.org/archives/freebsd-current/att-0339/2021-07-16_00.53_typescript.txt>
  1. marked clean
  2. marked dirty
Postscript

Reproducible with a new disk:
 

Attachments

  • 2021-07-21 19.19 typescript.txt
    65.9 KB · Views: 43
Last edited:
Last edited:
Top