mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: stewart@neuron.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: sync() broken for raw devices in 2.4.x??
Date: Tue, 2 Jan 2001 02:35:54 +0100	[thread overview]
Message-ID: <20010102023554.A2232@gruyere.muc.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10101011925130.1859-100000@localhost>
In-Reply-To: <Pine.LNX.4.10.10101011925130.1859-100000@localhost>; from stewart@neuron.com on Mon, Jan 01, 2001 at 07:50:31PM -0500

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/

  reply	other threads:[~2001-01-02  2:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02  0:50 stewart
2001-01-02  1:35 ` Andi Kleen [this message]
2001-01-02 15:26   ` stewart
2001-01-02 17:57   ` stewart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010102023554.A2232@gruyere.muc.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stewart@neuron.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®