I have extracted material from the list-exchanges
related to this and submitted:


against the kernel for the issue.

I placed emphasis on the SSD-trim related "freeing
free block" panics that "fsck -B" can lead to
after it gets the g_vfs_done messages for unclean
ufs file systems but first noted that:

mksnap_ffs /.snap2

was enough to get the g_vfs_done messages.

I figured that the nastiest and most important known
consequences were "fsck -B" being broken for unclean
ufs file systems and having later panics trying to
trim based on how it is broken.

I did also mention dump as producing the messages.

I referenced. . .

> See also the exchange of list submittals associated
> with:
> https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066505.html
> and:
> https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066508.html

Mark Millard
markmi at dsl-only.net

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to