diff options
| author | Mark Tinguely <tinguely@sgi.com> | 2014-07-24 20:49:40 +1000 |
|---|---|---|
| committer | Dave Chinner <david@fromorbit.com> | 2014-07-24 20:49:40 +1000 |
| commit | 5c18717ea25fcb87c746deac1bf2ef2ff46e154a (patch) | |
| tree | e3e730412cbfa4e831da455608ca47d0549ef129 /fs/xfs | |
| parent | 2451337dd043901b5270b7586942abe564443e3d (diff) | |
| download | op-kernel-dev-5c18717ea25fcb87c746deac1bf2ef2ff46e154a.zip op-kernel-dev-5c18717ea25fcb87c746deac1bf2ef2ff46e154a.tar.gz | |
xfs: fix cil push sequence after log recovery
When the CIL checkpoint is fully written to the log, the LSN of the checkpoint
commit record is written into the CIL context structure. This allows log force
waiters to correctly detect when the checkpoint they are waiting on have been
fully written into the log buffers.
However, the initial context after mount is initialised with a non-zero commit
LSN, so appears to waiters as though it is complete even though it may not have
even been pushed, let alone written to the log buffers. Hence a log force
immediately after a filesystem is mounted may not behave correctly, nor does
commit record ordering if multiple CIL pushes interleave immediately after
mount.
To fix this, make sure the initial context commit LSN is not touched until the
first checkpointis actually pushed.
[dchinner: rewrite commit message]
Signed-off-by: Mark Tinguely <tinguely@sgi.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'fs/xfs')
| -rw-r--r-- | fs/xfs/xfs_log_cil.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/xfs/xfs_log_cil.c b/fs/xfs/xfs_log_cil.c index 2ee4388..f6b79e5 100644 --- a/fs/xfs/xfs_log_cil.c +++ b/fs/xfs/xfs_log_cil.c @@ -78,8 +78,6 @@ xlog_cil_init_post_recovery( { log->l_cilp->xc_ctx->ticket = xlog_cil_ticket_alloc(log); log->l_cilp->xc_ctx->sequence = 1; - log->l_cilp->xc_ctx->commit_lsn = xlog_assign_lsn(log->l_curr_cycle, - log->l_curr_block); } /* |
