OK, I've taken a closer look at this. ext3 has picked up some
cruft from ext2's sync handling which it does not need in the
least.
It will be fairly straightforward and a useful cleanup to
provide the following semantics for either synchronous
mounts or `chattr +S' directories:
* All metadata operations (rename, unlink, link, symlink, etc)
will be synchronous. So when the system call returns, the data
is crash-proofed.
* All write()s will be synchronous. So when the write() system
call returns, the data written and all associated metadata
will be crash-proofed.
O_SYNC and fsync() will not be necessary - in fact they'll
slow things down slightly by forcing an unnecessary and
probably empty commit.
If you crash in the middle of a write, you may end up with a truncated
file on recovery.
This is in fact the behaviour right now, but the performance is
not good.
The performance problem at present is that large write()s have unnecessary
commits in the middle of them. This is due to the abovementioned
cruft in ext3_get_block() and the things it calls.
> Would you deem it
> possible to get such an option done before ext3fs 1.0.0?
We'd prefer not - we're trying to stabilise things quite
sternly at present. However that doesn't prevent work
on 1.1.0 :)
Seems like a worthwhile thing to do - I'll cut a branch
and do this. It'll take a couple of weeks - as usual, most
of the work is in development and use of test tools...
But I can't predict at this time when we'll merge it into
the mainline fs.
> I hope this makes the requirements of this particular group of
> applications clear.
Yes, it was useful - thanks.
-
-
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/