https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195278
--- Comment #3 from Kenneth Salerno <kennethsale...@yahoo.com> --- Seems to be caused by vfs.unmapped_buf_allowed=1, even though this is a bare metal laptop and not a VM as was reported in the 10 errata. Maybe what I have in common with FreeBSD in a VM is small amount of RAM on my laptop and vfs.unmapped_bufspace is too large for high I/O? Also, when I changed vfs.unmapped_buf_allowed to 0 and rebooted there were further file system corruptions detected during use that were not detected previously when vfs.unmapped_buf_allowed was set to 1, not sure if this is a coincidence. After fsdb clri, fsck -fy, fsck -fy, I was able to run svn update /usr/ports without an error. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
