All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11)
Date: Mon, 07 Mar 2005 18:49:05 -0600	[thread overview]
Message-ID: <422CF681.3010109@shaw.ca> (raw)
In-Reply-To: <3FnYi-11J-1@gated-at.bofh.it>

Jens Axboe wrote:
> fsync on ext2 only really guarantees that the data has reached
> the disk, what the disk does it outside the realm of the fs.
> If the ide drive has write back caching enabled, the data just
> might only be in cache. If the power is removed right after fsync
> returns, the drive might not get a chance to actually commit the
> write to platter.

Is this really the behavior in the current kernel? If so this seems 
quite wrong to me - if the application did an fsync, I think the kernel 
should be sending cache flush commands to the drive before the call 
completes..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2005-03-08  0:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3Fnc7-mf-11@gated-at.bofh.it>
     [not found] ` <3FnYi-11J-1@gated-at.bofh.it>
2005-03-08  0:49   ` Robert Hancock [this message]
2005-03-07  9:57 [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11) Junfeng Yang
2005-03-07 10:45 ` Jens Axboe
2005-03-07 22:55   ` Junfeng Yang
2005-03-08 11:02   ` Pavel Machek
2005-03-08 11:04     ` Jens Axboe
2005-03-08 12:31 ` Theodore Ts'o
2005-03-08 20:27   ` Junfeng Yang
2005-03-20  2:00   ` Bernd Eckenfels

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=422CF681.3010109@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.