Date: Mon, 07 Mar 2005 18:49:05 -0600
From: Robert Hancock <hancockr@shaw.ca>
Subject: Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2,
 2.6.11)
In-reply-to: <3FnYi-11J-1@gated-at.bofh.it>
To: linux-kernel <linux-kernel@vger.kernel.org>
Message-id: <422CF681.3010109@shaw.ca>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7bit
References: <3Fnc7-mf-11@gated-at.bofh.it> <3FnYi-11J-1@gated-at.bofh.it>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 977
Lines: 23

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/

-
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/