diff options
author | Dave Chinner <dchinner@redhat.com> | 2012-03-22 06:15:11 +0100 |
---|---|---|
committer | Ben Myers <bpm@sgi.com> | 2012-03-27 00:47:24 +0200 |
commit | 3948659e30808fbaa7673bbe89de2ae9769e20a7 (patch) | |
tree | 06ff528be9bd33a4f2579fb05514460b7fa1ec8a /fs/nfsd | |
parent | xfs: don't cache inodes read through bulkstat (diff) | |
download | linux-3948659e30808fbaa7673bbe89de2ae9769e20a7.tar.xz linux-3948659e30808fbaa7673bbe89de2ae9769e20a7.zip |
xfs: Account log unmount transaction correctly
There have been a few reports of this warning appearing recently:
XFS (dm-4): xlog_space_left: head behind tail
tail_cycle = 129, tail_bytes = 20163072
GH cycle = 129, GH bytes = 20162880
The common cause appears to be lots of freeze and unfreeze cycles,
and the output from the warnings indicates that we are leaking
around 8 bytes of log space per freeze/unfreeze cycle.
When we freeze the filesystem, we write an unmount record and that
uses xlog_write directly - a special type of transaction,
effectively. What it doesn't do, however, is correctly account for
the log space it uses. The unmount record writes an 8 byte structure
with a special magic number into the log, and the space this
consumes is not accounted for in the log ticket tracking the
operation. Hence we leak 8 bytes every unmount record that is
written.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'fs/nfsd')
0 files changed, 0 insertions, 0 deletions