Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751296AbVL3TbU (ORCPT ); Fri, 30 Dec 2005 14:31:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751297AbVL3TbU (ORCPT ); Fri, 30 Dec 2005 14:31:20 -0500 Received: from quechua.inka.de ([193.197.184.2]:19590 "EHLO mail.inka.de") by vger.kernel.org with ESMTP id S1751296AbVL3TbT (ORCPT ); Fri, 30 Dec 2005 14:31:19 -0500 From: Bernd Eckenfels To: linux-kernel@vger.kernel.org Subject: Re: RAID controller safety Organization: Private Site running Debian GNU/Linux In-Reply-To: <20051230185840.52264.qmail@web34113.mail.mud.yahoo.com> X-Newsgroups: ka.lists.linux.kernel User-Agent: tin/1.7.8-20050315 ("Scalpay") (UNIX) (Linux/2.6.13.4 (i686)) Message-Id: Date: Fri, 30 Dec 2005 20:31:17 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 629 Lines: 15 In article <20051230185840.52264.qmail@web34113.mail.mud.yahoo.com> you wrote: > So all writes would be treated as syncronous in the write-through case (no battery), making fsync > a no-op? The device cache is IMHO not related to the higher level buffer cache. So fsync flushes the buffers and the write-through ensures the controller may not delay it in controller ram. Gruss Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/