diff options
author | Jan Kara <jack@suse.cz> | 2012-04-07 11:05:19 +0200 |
---|---|---|
committer | Jan Kara <jack@suse.cz> | 2012-05-15 23:34:37 +0200 |
commit | fd2cbd4dfa3db477dd6226d387d3f1911d36a6a9 (patch) | |
tree | b0ada946d14cdcf5db6da2d177be9590a3449e9a /include/trace | |
parent | 1ce8486dcc00c1e095af8d155fa4451936b89013 (diff) | |
download | op-kernel-dev-fd2cbd4dfa3db477dd6226d387d3f1911d36a6a9.zip op-kernel-dev-fd2cbd4dfa3db477dd6226d387d3f1911d36a6a9.tar.gz |
jbd: Write journal superblock with WRITE_FUA after checkpointing
If journal superblock is written only in disk's caches and other transaction
starts reusing space of the transaction cleaned from the log, it can happen
blocks of a new transaction reach the disk before journal superblock. When
power failure happens in such case, subsequent journal replay would still try
to replay the old transaction but some of it's blocks may be already
overwritten by the new transaction. For this reason we must use WRITE_FUA when
updating log tail and we must first write new log tail to disk and update
in-memory information only after that.
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'include/trace')
-rw-r--r-- | include/trace/events/jbd.h | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/include/trace/events/jbd.h b/include/trace/events/jbd.h index d9658a9..da6f259 100644 --- a/include/trace/events/jbd.h +++ b/include/trace/events/jbd.h @@ -170,19 +170,22 @@ TRACE_EVENT(jbd_cleanup_journal_tail, ); TRACE_EVENT(journal_write_superblock, - TP_PROTO(journal_t *journal), + TP_PROTO(journal_t *journal, int write_op), - TP_ARGS(journal), + TP_ARGS(journal, write_op), TP_STRUCT__entry( __field( dev_t, dev ) + __field( int, write_op ) ), TP_fast_assign( __entry->dev = journal->j_fs_dev->bd_dev; + __entry->write_op = write_op; ), - TP_printk("dev %d,%d", MAJOR(__entry->dev), MINOR(__entry->dev)) + TP_printk("dev %d,%d write_op %x", MAJOR(__entry->dev), + MINOR(__entry->dev), __entry->write_op) ); #endif /* _TRACE_JBD_H */ |