First, thank you for your quick and complete reply :)
then:
Furthermore, file system corruption due to an abrupt
cut of power should be avoided. Whenever the system comes
up in a non-clean state, fsck should be run first, _then_
the boot process should continue. Still it's possible that
On Sun, 5 May 2013 10:42:02 +0430, takCoder wrote:
i added fsck_background=no to rc.conf but i still see the error.. and i
don't see any differance in system startup output! how should i know it's
working??
Please check the correct syntax for the /etc/rc.conf entry:
background_fsck=NO
On 05/05/2013 07:12, takCoder wrote:
Furthermore, file system corruption due to an abrupt
cut of power should be avoided. Whenever the system comes
up in a non-clean state, fsck should be run first, _then_
the boot process should continue. Still it's possible that
this process leaves
Hi guys,
I have a system running 10-CURRENT (r250217) which I've built Postgresql
9.2.4 with DTrace support enabled on a VM running 9.1-STABLE (r250009)
which I'm unable to build it on.
On 10-CURRENT the problem is that dtrace -l does not list the postgresql
provider.
My make.conf on both
Hi!
Back in FreeBSD 7 there was a flag to disable the FIFO on the sio
device driver. From
http://www.freebsd.org/cgi/man.cgi?query=sioapropos=0sektion=0manpath=FreeBSD+7.4-stablearch=defaultformat=html:
Meaning of flags:
0x1 shared IRQs
0x2 disable FIFO
0x4 no AST/4 compatible
On Mon, 29 Apr 2013 13:29:18 +0200, David Demelier demelier.da...@gmail.com
wrote:
2013/4/18 David Demelier demelier.da...@gmail.com:
Hello,
I would like to use ZFS over MBR for multiboot purposes. I've followed
that guide https://wiki.freebsd.org/RootOnZFS/ZFSBootPartition but it
does not
On 5/5/2013 3:20 PM, Giorgos Keramidas wrote:
Hi David,
Thanks for following up with what the real problem was. I updated the
Wiki to include this:
Note that partition order is important. It seems that zfsboot
requires the freebsd-zfs partition to be the first, so make sure you
