From owner-freebsd-fs@FreeBSD.ORG Thu Jul 8 13:59:40 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66051106564A for ; Thu, 8 Jul 2010 13:59:40 +0000 (UTC) (envelope-from dak.col@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1C2948FC17 for ; Thu, 8 Jul 2010 13:59:39 +0000 (UTC) Received: by gyd8 with SMTP id 8so463566gyd.13 for ; Thu, 08 Jul 2010 06:59:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=a9RJyDuOQI3KVJco7qs5f1TX6tsrFXP/B5cXl/FYAqY=; b=Av50pSFo0KBabpklG35TL31A1lHgEh+ChnMgcgrMGgIOnQk2T35/LzD6zG2Sec6Rmk 8HjpMdb11n60wQHCFWDB5RKRToL0xrmmv5IePSRpEn0ULuKujZjO2kEp62dfPjRo30Ct oaqhlUk2YiGlMiGl5bmDg5lyAvAQIfS/hmIU4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YcDfaloDdXOyPlb/rztIFFNwBokpj+suEe3BgLmxHhMFxelu+T8tn2cWnm/HTNL/sg FQ9PUkjeQI2Dbo+xCLhXWHAHUhiSCOepBxCJky0Sb23rkVbNkOm+OipHrb9sRuqSqMxu c+MtYTN8bY2nqGjM3C0CBkSQecte+W0NIU1FU= MIME-Version: 1.0 Received: by 10.90.53.3 with SMTP id b3mr3363070aga.121.1278597573573; Thu, 08 Jul 2010 06:59:33 -0700 (PDT) Received: by 10.90.28.10 with HTTP; Thu, 8 Jul 2010 06:59:33 -0700 (PDT) In-Reply-To: <394586.41761.qm@web112417.mail.gq1.yahoo.com> References: <4C3563A8.7060301@modulus.org> <688583.92527.qm@web112402.mail.gq1.yahoo.com> <4C358574.2040009@modulus.org> <394586.41761.qm@web112417.mail.gq1.yahoo.com> Date: Thu, 8 Jul 2010 08:59:33 -0500 Message-ID: From: Diego Arias To: Simun Mikecin Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Freebsd 8 Release /usr Die After host VMWARE Crash X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 13:59:40 -0000 On Thu, Jul 8, 2010 at 6:18 AM, Simun Mikecin wrote: > > > > > ----- Original Message ---- > > From: Andrew Snow > > To: Simun Mikecin ; freebsd-fs@freebsd.org > > Sent: Thu, July 8, 2010 9:59:48 AM > > Subject: Re: Freebsd 8 Release /usr Die After host VMWARE Crash > > > > On 08/07/10 17:45, Simun Mikecin wrote: > > > AFAIK virtual environments ignore disk sync requests by default. For > >example, in > > > VirtualBox they are ignored by default, by you could enable it if you > want > >(with > > > a performance penalty). Haven't used VMWare, so not 100% sure about > it, > >maybe > > > someone more knowledgable with VMWare knows what it's defaults are. > > > > VMware vSphere/ESX/ESXi makes all writes synchronous. > > > > (It is terribly slow on RAID cards that lack battery-backed cache!) > > > Thanx for the info. > But, there is still a chance that the host environment on which (original > poster's) VMware is running uses a lying ATA drive or some other storage > that > behaves the same as a lying ATA drive. > > > > > Hi there: - I discard a CPU/memory corruption because 8 more VM were running there and start without problem (Windows, not Unix ,Linux or BSD) - Actually i dont know if it is FreeBSD Fault but its curious and dangerous. - Its stock system so, no Async - Any info you need that might be usefull just ask, im here to help and can give you all the info you need - The FSTAB is in the first mail and this report mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) - the machine its actually running from its backup, i have not touched the FSTAB or mount stuff since installation - the machine was installed on VirtualBox then migrated to VMWARE with the convert utility from Virtualbox - SAN Hard drives are all Fibre Channel On Raid 5, fully redundant path, the SAN Switches on the chassis (Enclosure) didn't die when the enclosure start malfunctioning, other SAN applications works without trouble after restart on the same chasis as Virtual machines on the same LUN. the Blades Hard drives are SAS 10000RPM Diego Arias -- mmm, interesante.....