Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262449AbVD2HZb (ORCPT ); Fri, 29 Apr 2005 03:25:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262450AbVD2HZb (ORCPT ); Fri, 29 Apr 2005 03:25:31 -0400 Received: from ppsw-7.csi.cam.ac.uk ([131.111.8.137]:25048 "EHLO ppsw-7.csi.cam.ac.uk") by vger.kernel.org with ESMTP id S262449AbVD2HZY (ORCPT ); Fri, 29 Apr 2005 03:25:24 -0400 X-Cam-SpamDetails: Not scanned X-Cam-AntiVirus: No virus found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Date: Fri, 29 Apr 2005 08:25:17 +0100 (BST) From: Anton Altaparmakov To: Bryan Henderson cc: Alan Cox , brace@hp.com, Linux Kernel Mailing List , linux-scsi@vger.kernel.org, mike.miller@hp.com Subject: Re: [Question] Does the kernel ignore errors writng to disk? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1114 Lines: 26 On Thu, 28 Apr 2005, Bryan Henderson wrote: > >O_SYNC doesn't work completely on several file systems and only on the > >latest kernels with some of the common ones. > > Hmmm. You didn't mention such a restriction when you suggested fsync() > before. Does fsync() work completely on these kernels where O_SYNC > doesn't? Considering that a simple implementation of O_SYNC just does the > equivalent of an fsync() inside every write(), that would be hard to > understand. Some file systems implement their fsync() function as "return 0;" so no, you cannot rely on it at all. Best regards, Anton -- Anton Altaparmakov (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/ - 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/