In message <570c74cf.1080...@freebsd.org>, Peter Grehan writes:
> I'll try with a bit more CPU oversubscription and see if I can hit
>this. Thanks for the info - this should help track it down.
For what its worth, I think the port being compiled was:
Another possibly relevant datapoint:
The actively being written to filesystem is UFS+SU+TRIM but no
journal and I think fsck sees more and worse corruption than it
should if writes happened in the order Kirk intended. Specifically
it should never get fsck_ffs into the "please run fsck again" jungle.
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
email@example.com mailing list
To unsubscribe, send any mail to