On Fri, 2007-04-27 at 11:31 -0700, Andrew Morton wrote: [snip] > ext3's problem here is that a single fsync() requires that ext3 sync the > whole filesystem. Because > > - a journal commit can contain metadata from multiple files, and if we > want to journal one file's metadata via fsync(), we unavoidably journal > all the other file's metadata at the same time. > > - ordered mode requires that we write a file's data blocks prior to > journalling the metadata which refers to those blocks. > > net result: syncing anything syncs the whole world. > > There are a few areas in which this could conceivably be tuned up: if a > particular file doesn't currently have any metadata in the commit, we don't > actually need to sync its data blocks: we could just transfer them into > next commit. Hard, unlikely to be of benefit. [snip] How about mixing the ordered and data journal modes? If the data blocks would fit, have fsync write them into the journal as is done in data=journal mode. Then that file data is committed to disk as fsync requires, but it shouldn't require flushing all the previous metadata to get an ordered guarantee. Or so it seems to me. -- Zan Lynx <[email protected]>
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- References:
- [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- From: Mike Galbraith <[email protected]>
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- From: Linus Torvalds <[email protected]>
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- From: Andrew Morton <[email protected]>
- [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- Prev by Date: [PATCH 17/46] Driver core: add suspend() and resume() to struct device_type
- Next by Date: [PATCH 35/46] debugfs: Add debugfs_create_u64()
- Previous by thread: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- Next by thread: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- Index(es):
 |