aboutsummaryrefslogtreecommitdiffstats
path: root/fs/block_dev.c
diff options
context:
space:
mode:
authorBenjamin Marzinski <bmarzins@redhat.com>2009-06-25 15:09:51 -0500
committerSteven Whitehouse <swhiteho@redhat.com>2009-07-30 10:52:33 +0100
commit1946f70ab5e4eb8b54a8eaaedba2293a3750ab7e (patch)
tree91cc1850c7777d5cdea8713710081f70bb63a202 /fs/block_dev.c
parent2163b1e616c41c286f5ab79912671cd4bf52057c (diff)
downloadkernel_samsung_crespo-1946f70ab5e4eb8b54a8eaaedba2293a3750ab7e.zip
kernel_samsung_crespo-1946f70ab5e4eb8b54a8eaaedba2293a3750ab7e.tar.gz
kernel_samsung_crespo-1946f70ab5e4eb8b54a8eaaedba2293a3750ab7e.tar.bz2
GFS2: keep statfs info in sync on grows
GFS2 wasn't syncing its statfs info on grows. This causes a problem when you grow the filesystem on multiple nodes. GFS2 would calculate the new space based on the resource groups (which are always current), and then assume that the filesystem had grown the from the existing statfs size. If you grew the filesystem on two different nodes in a short time, the second node wouldn't see the statfs size change from the first node, and would assume that it was grown by a larger amount than it was. When all these changes were synced out, the total fileystem size would be incorrect (the first grow would be counted twice). This patch syncs makes GFS2 read in the statfs changes from disk before a grow, and write them out after the grow, while the master statfs inode is locked. Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/block_dev.c')
0 files changed, 0 insertions, 0 deletions