search for: jbd2_barrier

...--- a/fs/ext4/fsync.c +++ b/fs/ext4/fsync.c @@ -208,12 +208,11 @@ int ext4_sync_file(struct file *file, int datasync) * the journal device.) */ if (ext4_should_writeback_data(inode) && - (journal->j_fs_dev != journal->j_dev) && - (journal->j_flags & JBD2_BARRIER)) + (journal->j_fs_dev != journal->j_dev)) blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KERNEL, NULL); ret = jbd2_log_wait_commit(journal, commit_tid); - } else if (journal->j_flags & JBD2_BARRIER) + } else blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KER...

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use

ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes. Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other