Tomoaki AOKI writes:
> Looks fixed now, but what confused me is that r273919 modifies
> etc/rc.d/geli. I've not configured GELI neither in head VM nor
> stable/10 host.
Yes, it breaks the cycle in the rcorder graph. Whether you use geli or
not is irrelevant; the script still runs.
> *Noticed
On Sat, 01 Nov 2014 15:21:48 +0100
Dag-Erling Sm〓rgrav wrote:
> Tomoaki AOKI writes:
> > Dag-Erling Sm〓rgrav writes:
> > > Manfred Antar writes:
> > > > Then for some reason /var started to being mounted mfs. [...] If
> > > > I have varmfs="NO" and cleanvar_enable="NO" everything works fine.
On 01.11.2014 21:26, Trond Endrestøl wrote:
> What good does the file /entropy do if boot up is delayed everytime
> during "Writing entropy file:"?
Probably some entropy is needed before saved file is loaded.
As raw guessing of alternative solution it is possible to make some part
of previously s
On Sat, 1 Nov 2014 18:03+0100, Dag-Erling Smørgrav wrote:
> Ian Lepore writes:
> > Dag-Erling Smørgrav writes:
> > > I think you misremember. It is impossible to guarantee that the
> > > system will always have enough entropy right from the start.
> > > Servers, desktops and laptops will be fin
Ian Lepore writes:
> Dag-Erling Smørgrav writes:
> > I think you misremember. It is impossible to guarantee that the
> > system will always have enough entropy right from the start.
> > Servers, desktops and laptops will be fine, but embedded systems and
> > VMs might not be able to unblock unti
On Sat, 2014-11-01 at 15:59 +0100, Dag-Erling Smørgrav wrote:
> Ian Lepore writes:
> > Dag-Erling Smørgrav writes:
> > > That means we're not getting enough entropy during early boot, or
> > > we're underestimating the amount of entropy we're getting. We added
> > > entropy harvesting to device_
Ian Lepore writes:
> Dag-Erling Smørgrav writes:
> > That means we're not getting enough entropy during early boot, or
> > we're underestimating the amount of entropy we're getting. We added
> > entropy harvesting to device_attach() about a year ago, which in
> > most cases provides enough entro
On Sat, 2014-11-01 at 15:21 +0100, Dag-Erling Smørgrav wrote:
> Tomoaki AOKI writes:
> > Dag-Erling Smørgrav writes:
> > > Manfred Antar writes:
> > > > Then for some reason /var started to being mounted mfs. [...] If
> > > > I have varmfs="NO" and cleanvar_enable="NO" everything works fine.
>
Tomoaki AOKI writes:
> Dag-Erling Smørgrav writes:
> > Manfred Antar writes:
> > > Then for some reason /var started to being mounted mfs. [...] If
> > > I have varmfs="NO" and cleanvar_enable="NO" everything works fine.
> > Not really. The default for varmfs is AUTO, which mounts a memory
>
On Sat, 01 Nov 2014 01:33:09 +0100
Dag-Erling Sm〓rgrav wrote:
> Manfred Antar writes:
> > 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 fin
Manfred Antar writes:
> 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.
Not really. The default for varmfs is AUTO, which mounts a memory f
"O. Hartmann" writes:
> r273800 was the last (obviously) working on one box, r273872 seems to
> have the problem:
Are you sure? If I understand Manfred correctly, r273905 was running
fine for him.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-
Le 31/10/2014 23:35, Martin MATO a écrit :
Le 31/10/2014 22:50, Martin MATO a écrit :
Le 31/10/2014 22:23, Dag-Erling Smørgrav a écrit :
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 tri
On Oct 31, 2014, at 15:35, Martin MATO wrote:
> Le 31/10/2014 22:50, Martin MATO a écrit :
>> Le 31/10/2014 22:23, Dag-Erling Smørgrav a écrit :
>>> Can you all please tell me which revision(s) you were running before you
>>> upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*"
>>>
Am Fri, 31 Oct 2014 22:23:28 +0100
Dag-Erling Smørgrav schrieb:
> 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.
>
> DES
r273800 was the last (obviously) working on one box, r273
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The problem should have been corrected by r273919. Please update your
system and update /etc/ with mergemaster.
Cheers,
- --
Xin LI https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
-BEGIN PGP SIGNATURE-
Le 31/10/2014 22:50, Martin MATO a écrit :
Le 31/10/2014 22:23, Dag-Erling Smørgrav a écrit :
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.
DES
Absolutely
here it is
/var/log/mes
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
Le 31/10/2014 22:23, Dag-Erling Smørgrav a écrit :
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.
DES
Absolutely
here it is
/var/log/messages:Oct 31 12:11:05 kernel: FreeBSD 11.0-
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/kern
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.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http:/
Le 31.10.2014 21:35, Martin MATO a écrit :
> Le 31.10.2014 21:00, Manfred Antar a écrit :
>> At 12:20 PM 10/31/2014, O. Hartmann wrote:
>>
>>> On all CURRENT systems I updated today (31.10.2014) I had massive
>>> filesystem corruption
>>> after reboot. The systems do have
>>>
>>> FreeBSD 11.0-CU
At 12:20 PM 10/31/2014, O. Hartmann wrote:
>On all CURRENT systems I updated today (31.10.2014) I had massive filesystem
>corruption
>after reboot. The systems do have
>
>FreeBSD 11.0-CURRENT #1 r273914: Fri Oct 31 19:40:04 CET 2014 amd64
>
>and suffer without exception from the same breakage, q
On all CURRENT systems I updated today (31.10.2014) I had massive filesystem
corruption
after reboot. The systems do have
FreeBSD 11.0-CURRENT #1 r273914: Fri Oct 31 19:40:04 CET 2014 amd64
and suffer without exception from the same breakage, quitting services and/or
reporting
corrupted files
24 matches
Mail list logo
