Message-ID: <4671907F.5050706@cfl.rr.com>
Date: Thu, 14 Jun 2007 15:01:19 -0400
From: Phillip Susi <psusi@cfl.rr.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Pavel Machek <pavel@ucw.cz>
CC: Mark Lord <lkml@rtr.ca>, Andrew Morton <akpm@linux-foundation.org>,
       Stephen Tweedie <sct@redhat.com>, "Theodore Ts'o" <tytso@mit.edu>,
       Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3fs: umount+sync not enough to guarantee metadata-on-disk
References: <46680BB8.50404@rtr.ca> <20070607084142.42583639.akpm@linux-foundation.org> <46682BE7.6080802@rtr.ca> <20070610182746.GA4272@ucw.cz>
In-Reply-To: <20070610182746.GA4272@ucw.cz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 879
Lines: 25

Pavel Machek wrote:
> Hi!
> 
>>> Did this succeed?  If the application is still 
>>> truncating that file, the
>>> umount should have failed.
>> Actually, what I expect to happen is for the remount,ro
>> to block  until the file deletion completes.  But it 
>> doesn't.
>>
>> Once a f/s is read-only, there should be NO writing to 
>> it.  Right?
> 
> Linux happily writes to filesystems mounted read-only. It will replay
> journal on them.

That's a bug and needs fixed.  Read only means read _only_.

And the question still remains; why is sync() not blocking until the 
file has been completely unlinked and the disk is consistent?
-
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/