From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 2 Jan 2001 13:26:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 2 Jan 2001 13:26:39 -0500 Received: from va-ext.webmethods.com ([208.234.160.252]:31274 "EHLO localhost.neuron.com") by vger.kernel.org with ESMTP id ; Tue, 2 Jan 2001 13:26:25 -0500 Date: Tue, 2 Jan 2001 12:57:52 -0500 (EST) From: stewart@neuron.com To: Andi Kleen cc: linux-kernel@vger.kernel.org Subject: Re: sync() broken for raw devices in 2.4.x?? In-Reply-To: <20010102023554.A2232@gruyere.muc.suse.de> Message-ID: 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 Thanks for the correction. I am using a buffered block device then, not a real synchronous raw device. stewart On Tue, 2 Jan 2001, Andi Kleen wrote: > On Mon, Jan 01, 2001 at 07:50:31PM -0500, stewart@neuron.com wrote: > > > > I have a sync()/fdatasync() intensive application that is designed to work > > on both raw files and raw partitions. Today I upgraded my kernel to the > > new pre-release and found that my benchmark program would no longer finish > > when handed a raw partition. I've written a small Java program (my app is > > in Java) which demonstrates the bug. Make foo.dat a raw scsi partition to > > re-produce. In my case it's "mknod foo.dat b 8 18". > > Just a minor correction: this is not a raw partition, but a buffered blockdevice. > If you want a real rawdevice (where sync is a noop because all IO goes > synchronously to disk) you need to bind a character raw device to the > block device first using the raw util. > > >From a quick look sync_buffers() [which implements fsync on block devices] > has not changed significantly between 2.2 and 2.4 and uses the same algorithm. > > -Andi > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/