From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v4 09/18] xfs: use actual inode count for sparse records in bulkstat/inumbers
Date: Thu, 12 Feb 2015 13:17:16 -0500 [thread overview]
Message-ID: <1423765045-15791-10-git-send-email-bfoster@redhat.com> (raw)
In-Reply-To: <1423765045-15791-1-git-send-email-bfoster@redhat.com>
The bulkstat and inumbers mechanisms make the assumption that inode
records consist of a full 64 inode chunk in several places. For example,
this is used to track how many inodes have been processed overall as
well as to determine whether a record has allocated inodes that must be
handled.
This assumption is invalid for sparse inode records. While sparse inodes
will be marked as free in the ir_free mask, they are not accounted as
free in ir_freecount because they cannot be allocated. Therefore,
ir_freecount may be less than 64 inodes in an inode record for which all
physically allocated inodes are free (and in turn ir_freecount < 64 does
not signify that the record has allocated inodes).
The new in-core inobt record format includes the ir_count field. This
holds the number of true, physical inodes tracked by the record. The
in-core ir_count field is always valid as it is hardcoded to
XFS_INODES_PER_CHUNK when sparse inodes is not enabled. Use ir_count to
handle inode records correctly in bulkstat in a generic manner.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
fs/xfs/xfs_itable.c | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/fs/xfs/xfs_itable.c b/fs/xfs/xfs_itable.c
index 82e3142..7c68058 100644
--- a/fs/xfs/xfs_itable.c
+++ b/fs/xfs/xfs_itable.c
@@ -252,7 +252,7 @@ xfs_bulkstat_grab_ichunk(
}
irec->ir_free |= xfs_inobt_maskn(0, idx);
- *icount = XFS_INODES_PER_CHUNK - irec->ir_freecount;
+ *icount = irec->ir_count - irec->ir_freecount;
}
return 0;
@@ -415,6 +415,8 @@ xfs_bulkstat(
goto del_cursor;
if (icount) {
irbp->ir_startino = r.ir_startino;
+ irbp->ir_holemask = r.ir_holemask;
+ irbp->ir_count = r.ir_count;
irbp->ir_freecount = r.ir_freecount;
irbp->ir_free = r.ir_free;
irbp++;
@@ -447,13 +449,15 @@ xfs_bulkstat(
* If this chunk has any allocated inodes, save it.
* Also start read-ahead now for this chunk.
*/
- if (r.ir_freecount < XFS_INODES_PER_CHUNK) {
+ if (r.ir_freecount < r.ir_count) {
xfs_bulkstat_ichunk_ra(mp, agno, &r);
irbp->ir_startino = r.ir_startino;
+ irbp->ir_holemask = r.ir_holemask;
+ irbp->ir_count = r.ir_count;
irbp->ir_freecount = r.ir_freecount;
irbp->ir_free = r.ir_free;
irbp++;
- icount += XFS_INODES_PER_CHUNK - r.ir_freecount;
+ icount += r.ir_count - r.ir_freecount;
}
error = xfs_btree_increment(cur, 0, &stat);
if (error || stat == 0) {
@@ -599,8 +603,7 @@ xfs_inumbers(
agino = r.ir_startino + XFS_INODES_PER_CHUNK - 1;
buffer[bufidx].xi_startino =
XFS_AGINO_TO_INO(mp, agno, r.ir_startino);
- buffer[bufidx].xi_alloccount =
- XFS_INODES_PER_CHUNK - r.ir_freecount;
+ buffer[bufidx].xi_alloccount = r.ir_count - r.ir_freecount;
buffer[bufidx].xi_allocmask = ~r.ir_free;
if (++bufidx == bcount) {
long written;
--
1.8.3.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-02-12 18:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 18:17 [PATCH v4 00/18] xfs: sparse inode chunks Brian Foster
2015-02-12 18:17 ` [PATCH v4 01/18] xfs: create individual inode alloc. helper Brian Foster
2015-02-12 18:17 ` [PATCH v4 02/18] xfs: update free inode record logic to support sparse inode records Brian Foster
2015-02-12 18:17 ` [PATCH v4 03/18] xfs: support min/max agbno args in block allocator Brian Foster
2015-02-12 18:17 ` [PATCH v4 04/18] xfs: add sparse inode chunk alignment superblock field Brian Foster
2015-02-12 18:17 ` [PATCH v4 05/18] xfs: use sparse chunk alignment for min. inode allocation requirement Brian Foster
2015-02-12 18:17 ` [PATCH v4 06/18] xfs: sparse inode chunks feature helpers and mount requirements Brian Foster
2015-02-12 18:17 ` [PATCH v4 07/18] xfs: add fs geometry bit for sparse inode chunks Brian Foster
2015-02-12 18:17 ` [PATCH v4 08/18] xfs: introduce inode record hole mask " Brian Foster
2015-02-12 18:17 ` Brian Foster [this message]
2015-02-12 18:17 ` [PATCH v4 10/18] xfs: pass inode count through ordered icreate log item Brian Foster
2015-02-12 18:17 ` [PATCH v4 11/18] xfs: handle sparse inode chunks in icreate log recovery Brian Foster
2015-02-12 18:17 ` [PATCH v4 12/18] xfs: helpers to convert holemask to/from generic bitmap Brian Foster
2015-02-12 18:17 ` [PATCH v4 13/18] xfs: allocate sparse inode chunks on full chunk allocation failure Brian Foster
2015-02-12 18:17 ` [PATCH v4 14/18] xfs: randomly do sparse inode allocations in DEBUG mode Brian Foster
2015-02-12 18:17 ` [PATCH v4 15/18] xfs: filter out sparse regions from individual inode allocation Brian Foster
2015-02-12 18:17 ` [PATCH v4 16/18] xfs: only free allocated regions of inode chunks Brian Foster
2015-02-12 18:17 ` [PATCH v4 17/18] xfs: skip unallocated regions of inode chunks in xfs_ifree_cluster() Brian Foster
2015-02-12 18:17 ` [PATCH v4 18/18] xfs: enable sparse inode chunks for v5 superblocks Brian Foster
2015-02-13 20:07 ` [PATCH v4 00/18] xfs: sparse inode chunks Brian Foster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1423765045-15791-10-git-send-email-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox