xfs: perag initialization should only touch m_ag_max_usable for AG 0
authorDarrick J. Wong <darrick.wong@oracle.com>
Mon, 18 Sep 2017 16:42:09 +0000 (09:42 -0700)
committerDarrick J. Wong <darrick.wong@oracle.com>
Tue, 26 Sep 2017 17:55:19 +0000 (10:55 -0700)
commit9789dd9e1d939232e8ff4c50ef8e75aa6781b3fb
tree4e05bf062457bd86a3cbdd922e59997c72757537
parentee70daaba82d70766d0723b743d9fdeb3b06102a
xfs: perag initialization should only touch m_ag_max_usable for AG 0

We call __xfs_ag_resv_init to make a per-AG reservation for each AG.
This makes the reservation per-AG, not per-filesystem.  Therefore, it
is incorrect to adjust m_ag_max_usable for each AG.  Adjust it only
when we're reserving AG 0's blocks so that we only do it once per fs.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
fs/xfs/libxfs/xfs_ag_resv.c