9 messages in org.freebsd.freebsd-fsRe: Freebsd 8 Release /usr Die After ...| From | Sent On | Attachments |
|---|---|---|
| Diego Arias | Jul 7, 2010 12:03 pm | |
| Julian Elischer | Jul 7, 2010 1:25 pm | |
| Andrew Snow | Jul 7, 2010 10:35 pm | |
| Simun Mikecin | Jul 8, 2010 12:45 am | |
| Andrew Snow | Jul 8, 2010 12:59 am | |
| Simun Mikecin | Jul 8, 2010 4:18 am | |
| Diego Arias | Jul 8, 2010 6:59 am | |
| Andrew Snow | Jul 8, 2010 6:41 pm | |
| Diego Arias | Jul 9, 2010 7:11 am |
| Subject: | Re: Freebsd 8 Release /usr Die After host VMWARE Crash | |
|---|---|---|
| From: | Diego Arias (dak....@gmail.com) | |
| Date: | Jul 9, 2010 7:11:10 am | |
| List: | org.freebsd.freebsd-fs | |
On Thu, Jul 8, 2010 at 8:42 PM, Andrew Snow <and...@modulus.org> wrote:
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
Well you are right, i have ATA type devices (ad0). so im going to change to SAS
-- mmm, interesante.....
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "free...@freebsd.org"