Date: Sun, 9 May 2010 00:16:13 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Ansar Mohammed <ansarm@gmail.com> Cc: Bobby Walker <bobbyjwalker@live.com>, freebsd-questions@freebsd.org Subject: Re: File system Message-ID: <o2v6201873e1005082216l5c298c60p66705bf218b66957@mail.gmail.com> In-Reply-To: <m2k768631271005082018r83839cc5wdc5531906234afa3@mail.gmail.com> References: <u2z768631271005081836k26590481qcaab03601799448d@mail.gmail.com> <BLU0-SMTP88023B888DBB974F2A7FE6BBF80@phx.gbl> <m2k768631271005082018r83839cc5wdc5531906234afa3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 8, 2010 at 10:18 PM, Ansar Mohammed <ansarm@gmail.com> wrote: > Hello Bobby, > > The VM is in my lab environemnt. I have many flavours of Windows, Linux and > FreeBSD. FreeBSD is my firewall running PF. > > > I have rebooted my entire environment hundreds of times, and non of my > Windows or Linux VMs will complain or boot into a repair/single user mode. > > The background to this problem is because the FreeBSD root filesystem (UFS) > is not journaled and for some reason I cannot set my root partition to be > UFS+SoftUpdates. > Well I'd say that's clearly not the problem since so many of us don't have your issues. SU is disabled on / for a reason. I highly doubt you actually want to enable this, but you can if you adjust the FS when it isn't mounted eg boot from fixit cd. > > At any rate, we are in the year 2010, most modern operating systems and > databases and able to survive an unclean shutdown without booting into > single user mode and file system/data corruption. > FreeBSD has defaulted to background checking on SU FS's for the better part of 10 years. What version are you running? What data corruption did you have and what does databases have to do with it? Also DB's that are unexpectly killed can have consistency problems regardless of what FS it writes to and OS happens to be running it. > > I love FreeBSD, and have been a user since 2.x > User as in you saw it running a couple times? So on to your actual issue instead of all the bs, what does your /etc/rc.conf say? Specifically, what is the boot failing on? If you really want the disk/partition/slice journaled, you can do so with gjournal or ZFS offers an even better copy-on-write system. If the install is only running a fw, the zfs is probably overkill though. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?o2v6201873e1005082216l5c298c60p66705bf218b66957>