summaryrefslogtreecommitdiffstats
path: root/fs/xfs/xfs_alloc.h
diff options
context:
space:
mode:
authorDave Chinner <dchinner@redhat.com>2011-01-04 04:49:29 +0000
committerAlex Elder <aelder@sgi.com>2011-01-11 20:28:17 -0600
commitc58efdb442bb49dea1d148f207560c41918c1bf4 (patch)
treed6e117ae65ff7ff921600ef936a7bbb4e3130010 /fs/xfs/xfs_alloc.h
parenteda77982729b7170bdc9e8855f0682edf322d277 (diff)
downloadop-kernel-dev-c58efdb442bb49dea1d148f207560c41918c1bf4.zip
op-kernel-dev-c58efdb442bb49dea1d148f207560c41918c1bf4.tar.gz
xfs: ensure log covering transactions are synchronous
To ensure the log is covered and the filesystem idles correctly, we need to ensure that dummy transactions hit the disk and do not stay pinned in memory. If the superblock is pinned in memory, it can't be flushed so the log covering cannot make progress. The result is dependent on timing - more oftent han not we continue to issues a log covering transaction every 36s rather than idling after ~90s. Fix this by making the log covering transaction synchronous. To avoid additional log force from xfssyncd, make the log covering transaction take the place of the existing log force in the xfssyncd background sync process. Signed-off-by: Dave Chinner <dchinner@redhat.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Alex Elder <aelder@sgi.com>
Diffstat (limited to 'fs/xfs/xfs_alloc.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud