diff options
| author |   Tim Shimmin <tes@chook.melbourne.sgi.com> | 2007-10-01 16:39:37 +1000 |
|---|---|---|
| committer |   Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-10-01 07:59:03 -0700 |
| commit | 564256c9e06d75e16d894a2cd30604bd6582cbba (patch) | |
| tree | ef5505f335d401862893dd6a1bbca3e6dc3eaa88 /fs/xfs/xfs_trans_buf.c | |
| parent | fix console change race exposed by CFS (diff) | |
| download | linux-dev-564256c9e06d75e16d894a2cd30604bd6582cbba.tar.xz linux-dev-564256c9e06d75e16d894a2cd30604bd6582cbba.zip | |
Revert "[XFS] Avoid replaying inode buffer initialisation log items if on-disk version is newer."
This reverts commit b394e43e995d08821588a22561c6a71a63b4ff27.
Lachlan McIlroy says:
It tried to fix an issue where log replay is replaying an inode cluster
initialisation transaction that should not be replayed because the inode
cluster on disk is more up to date. Since we don't log file sizes (we
rely on inode flushing to get them to disk) then we can't just replay
all the transations in the log and expect the inode to be completely
restored. We lose file size updates. Unfortunately this fix is causing
more (serious) problems than it is fixing.
SGI-PV: 969656
SGI-Modid: xfs-linux-melb:xfs-kern:29804a
Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
Signed-off-by: Tim Shimmin <tes@sgi.com>
Diffstat (limited to '')
| -rw-r--r-- | fs/xfs/xfs_trans_buf.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/xfs/xfs_trans_buf.c b/fs/xfs/xfs_trans_buf.c index 95fff6872a2f..60b6b898022b 100644 --- a/fs/xfs/xfs_trans_buf.c +++ b/fs/xfs/xfs_trans_buf.c @@ -966,7 +966,6 @@ xfs_trans_inode_alloc_buf( ASSERT(atomic_read(&bip->bli_refcount) > 0); bip->bli_flags |= XFS_BLI_INODE_ALLOC_BUF; - bip->bli_format.blf_flags |= XFS_BLI_INODE_NEW_BUF; } |