Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

From: Manfred Antar <null_at_pozo.com>
Date: Fri, 31 Oct 2014 15:31:54 -0700
At 02:44 PM 10/31/2014, Andreas Tobler wrote:
>On 31.10.14 22:23, Dag-Erling Smørgrav wrote:
>>Can you all please tell me which revision(s) you were running before you
>>upgraded?  Something like "bzgrep 11.0-CURRENT /var/log/messages*"
>>should do the trick.
>
>+1 here. 'Corrupted' /usr. Changed entry in fstab to not check fs.
>
>[zrhws131:/boot/kernel.old] andreast% strings kernel | grep CURRENT
>_at_(#)FreeBSD 11.0-CURRENT #33 r273767M: Tue Oct 28 11:20:32 CET 2014
>
>Andreas
>
>
>

FreeBSD 11.0-CURRENT #0 r273905: Fri Oct 31 06:15:56 PDT 2014 11.0-CURRENT
No corruption here, during the last few days i was getting sysctl-random error during boot.
So today I did a buildworld installworld buildkernel installkernel, and mergemaster .
some of the /etc/rc.d/random files were updated.
Reboot
Then for some reason /var started to being mounted mfs.
so for me i think it has something to do with the new rc.d startup files.
If I have varmfs="NO" and cleanvar_enable="NO"  everything works fine.
I noticed one thing during boot:

Writing entropy file:random: unblocking device.

takes a little longer 
I changed to entropy_save_sz="4096"  in /etc/rc.conf, maybe thats why.

========================
||      null_at_pozo.com           ||
||                                      ||
======================== 
Received on Fri Oct 31 2014 - 21:32:29 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:53 UTC