Date: Fri, 09 Jul 2010 11:42:31 +1000 From: Andrew Snow <andrew@modulus.org> To: Diego Arias <dak.col@gmail.com>, freebsd-fs@freebsd.org Subject: Re: Freebsd 8 Release /usr Die After host VMWARE Crash Message-ID: <4C367E87.7050505@modulus.org> In-Reply-To: <AANLkTilVlQQfHc5UTss1Q4Ew4AInt-bln70lkVZ7jEAK@mail.gmail.com> References: <AANLkTiknH3e0X5lu30azKWguKkgbH_-3pOLQKXinCDPs@mail.gmail.com> <AANLkTilN4EA6hYYRwbPggAdz6O6iPjA_5Em5SU8hXTlC@mail.gmail.com> <4C3563A8.7060301@modulus.org> <688583.92527.qm@web112402.mail.gq1.yahoo.com> <4C358574.2040009@modulus.org> <394586.41761.qm@web112417.mail.gq1.yahoo.com> <AANLkTilVlQQfHc5UTss1Q4Ew4AInt-bln70lkVZ7jEAK@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/07/10 23:59, Diego Arias wrote: > /dev/ad0s1a on / (ufs, local) > > - the machine was installed on VirtualBox then migrated to VMWARE with > the convert utility from Virtualbox Ahh, I think this is the problem. When converting from VBox, it uses an ATA disk, instead of VMWare's default of SCSI guest disks. This means FreeBSD enables the ATA write cache by default, which VMware honors and might be prone to lose data on power outage. I suspect you should either set hw.ata.wc=0 in loader.conf, or switch to SCSI gues disk type. But its still possible there was CPU/RAM problems and you were just lucky that the other guest disks didnt get corrupt as they may not have been writing to directory metadata at the time of crash. - Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C367E87.7050505>