Messages in this thread | | | Date | Mon, 15 Feb 1999 16:37:08 GMT | From | "Stephen C. Tweedie" <> | Subject | Re: fsync on large files |
| |
Hi,
On Mon, 15 Feb 1999 10:10:30 +1100 (EST), Damien Miller <dmiller@ilogic.com.au> said:
> On Sat, 13 Feb 1999, Theodore Y. Ts'o wrote: >> Hmm. That's an interesting problem. This is the first time someone's >> called it to my attention that syslog was calling fsync() all the time, >> and obviously this causes a problem if there's a lot of syslogging going >> on and the log files are large.
> Pardon my ignorance, but is there any reason that syslog cannot open > its logfiles with O_SYNC?
Good question, it would certainly help --- lots. Ultimately, though, we really do need to be able to track all of the dirty data and metadata which belongs to any given inode: our fsync is going to be pretty sucky until we do.
--Stephen
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |