Re: ext3fs: umount+sync not enough to guarantee metadata-on-disk

[Phillip Susi]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/