| commit | d9ba7615bfd8bb06f79c853f9dfff9e93a837941 | |
| author | Steven Whitehouse <swhiteho@redhat.com> | |
| Thu, 23 Apr 2009 07:59:41 +0000 (23 08:59 +0100) | ||
| committer | Steven Whitehouse <swhiteho@redhat.com> | |
| Thu, 23 Apr 2009 09:07:37 +0000 (23 10:07 +0100) | ||
| tree | 647f6078a7804a53b4902b90942864942e9d425b | treesnapshot (tar.gz zip) |
| parent | d8bd504ab800c8e9aadb983914a33e7166320bec | commitdiff |
GFS2: Ensure that the inode goal block settings are updated
GFS2 has a goal block associated with each inode indicating the
search start position for future block allocations (in fact there
are two, but thats for backward compatibility with GFS1 as they
are set to identical locations in GFS2).
In some circumstances, depending on the ordering of updates to
the inode it was possible for the goal block settings to not
be updated on disk. This patch ensures that the goal block will
always get updated, thus reducing the potential for searching
the same (already allocated) blocks again when looking for free
space during block allocation.
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
GFS2 has a goal block associated with each inode indicating the
search start position for future block allocations (in fact there
are two, but thats for backward compatibility with GFS1 as they
are set to identical locations in GFS2).
In some circumstances, depending on the ordering of updates to
the inode it was possible for the goal block settings to not
be updated on disk. This patch ensures that the goal block will
always get updated, thus reducing the potential for searching
the same (already allocated) blocks again when looking for free
space during block allocation.
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
| fs/gfs2/rgrp.c | diffblobblamehistory |