search for: ocfs2_orphan_for_truncate

...- easy to fix, just move the call just after the write of the inode. 2) ocfs2_setattr() - we can move the call into ocfs2_truncate_file() but that would mean calling jbd2_journal_begin_ordered_truncate() and consequently ocfs2_write_page() under ip_alloc_sem - not too nice. Furthermore ocfs2_orphan_for_truncate() zeros the last cluster beyond i_size and we cannot do that before writing out previous content... Not sure how to solve that yet. Any ideas welcome. Honza -- Jan Kara <jack at suse.cz> SUSE Labs, CR

The following series of patches attempts to detach metadata I/O from struct inode. They are currently tied together pretty tightly. Metadata reads happen via the ocfs2_read_blocks() functions, writes via both jbd2 and ocfs2_write_blocks(). - Each inode has a cache of associated metadata blocks stored on its ip_metadata_cache member. The ocfs2_read/write_blocks() functions take a struct