From owner-freebsd-questions@FreeBSD.ORG Mon Dec 21 17:04:06 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 952EE106568D for ; Mon, 21 Dec 2009 17:04:06 +0000 (UTC) (envelope-from cronfy@gmail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id 2A03A8FC08 for ; Mon, 21 Dec 2009 17:04:05 +0000 (UTC) Received: by fxm10 with SMTP id 10so2409771fxm.14 for ; Mon, 21 Dec 2009 09:04:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=oZfqYB5JQCr0k1QpAwpI2vvaZWD698PpTOr9+43dclk=; b=vtyGMsTzRmAsd03ufsl5ZPBkFWIUDc8xfWCqRyFUxSG7BaSPS31KiKXs7wLJXOOh/g g/4ufxsaRJ0Cpbbd4H4unnjkuqXZbylVpJPb95yJW13l4gjXIgmqVQRWHmnLVeZFgaZK U02KiiLIAaAzXFTRqMuRW2QY5kG5+8yjw64Sk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=MQvhOPo0qCV61RlloziBsnfh0/3SR3amuzvHSDxLwMkmwWMkib6bjc+yIvSsbrt35T blHD4bqoOgoWc6ALSHI2cZ6YpwX5YruIA1DZCIzGrt/DQiH8ORYt5s7F5ktv6gCXJzgW FNrm3qzOrzEEQWciefkCvFeHXh0K+ocEjugqM= MIME-Version: 1.0 Received: by 10.223.4.132 with SMTP id 4mr1736999far.45.1261415045119; Mon, 21 Dec 2009 09:04:05 -0800 (PST) In-Reply-To: <20091218181204.GB98208@guilt.hydra> References: <4B1DF953.4050504@sprinthost.ru> <4B1E2D40.9060900@sprinthost.ru> <20091218181204.GB98208@guilt.hydra> From: cronfy Date: Mon, 21 Dec 2009 20:03:45 +0300 Message-ID: To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: FreeBSD is too filesystem errors sensitive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 17:04:06 -0000 >> After panic data *is* getting corrupted anyway - MySQL tables that were >> open are broken, soft-updates are unsync'ed etc etc. > If it's an option for you, you may want to look into disabling soft > updates as well so that you don't have to just hope that everything gets > synced before the end of the world. =A0Depending on your usage, however, > this might result in unacceptably poor performance. I am thinking about it. I am using RAID controller with battery and write cache enabled, but I just did not test performance for Softupdates vs no Softupdates + Write cache. Probably, someone have done this already? --=20 // cronfy