https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195458
Andrew Smith <iamasmith.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iamasmith.h...@gmail.com
--- Comment #10 from Andrew Smith <iamasmith.h...@gmail.com> ---
It seems that this at last effects all Kernels since 10.1-RELEASE through p3.
If you have one of these Kernels with Softupdates active on the root filesystem
and you replace /sbin/init then you get this behaviour.
If you either disable file system softupdates on the filesystem or you disable
the softupdates option in a new Kernel build then the issue does not exist.
I suspect people that haven't had this issue have some other environmental
difference that nobody has highlighted yet.
The issue of course hits 10.0-RELEASE to 10.1-RELEASE upgrades since when
freebsd-update install is run, the first thing done is to replace the Kernel
and ask for a reboot then run freebsd-update again. The Kernel exhibiting the
problem is then in place.
Could this be related to the changes made to ufs for the per FFS-Filesystem
threading around August? (r269457, r269533, r269583).
--
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"
