From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v4 17/20] xfsprogs/repair: helpers for finding in-core inode records w/ free inodes
Date: Wed, 7 May 2014 08:21:56 -0400 [thread overview]
Message-ID: <1399465319-65066-18-git-send-email-bfoster@redhat.com> (raw)
In-Reply-To: <1399465319-65066-1-git-send-email-bfoster@redhat.com>
Add the findfirst_free_inode_rec() and next_free_ino_rec() helpers
to assist scanning the in-core inode records for records with at
least one free inode. These will be used to determine what records
are included in the free inode btree.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
repair/incore.h | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/repair/incore.h b/repair/incore.h
index 5419884..5f8c188 100644
--- a/repair/incore.h
+++ b/repair/incore.h
@@ -381,6 +381,33 @@ void clear_uncertain_ino_cache(xfs_agnumber_t agno);
((ino_tree_node_t *) ((ino_node_ptr)->avl_node.avl_forw))
/*
+ * finobt helpers
+ */
+static inline ino_tree_node_t *
+findfirst_free_inode_rec(xfs_agnumber_t agno)
+{
+ ino_tree_node_t *ino_rec;
+
+ ino_rec = findfirst_inode_rec(agno);
+
+ while (ino_rec && !ino_rec->ir_free)
+ ino_rec = next_ino_rec(ino_rec);
+
+ return ino_rec;
+}
+
+static inline ino_tree_node_t *
+next_free_ino_rec(ino_tree_node_t *ino_rec)
+{
+ ino_rec = next_ino_rec(ino_rec);
+
+ while (ino_rec && !ino_rec->ir_free)
+ ino_rec = next_ino_rec(ino_rec);
+
+ return ino_rec;
+}
+
+/*
* Has an inode been processed for phase 6 (reference count checking)?
*
* add_inode_refchecked() is set on an inode when it gets traversed
--
1.8.3.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-07 12:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 12:21 [PATCH v4 00/20] xfsprogs: introduce the free inode btree Brian Foster
2014-05-07 12:21 ` [PATCH v4 01/20] xfs: refactor xfs_ialloc_btree.c to support multiple inobt numbers Brian Foster
2014-05-07 12:21 ` [PATCH v4 02/20] xfs: reserve v5 superblock read-only compat. feature bit for finobt Brian Foster
2014-05-07 12:21 ` [PATCH v4 03/20] xfs: support the XFS_BTNUM_FINOBT free inode btree type Brian Foster
2014-05-07 12:21 ` [PATCH v4 04/20] xfs: update inode allocation/free transaction reservations for finobt Brian Foster
2014-05-07 12:21 ` [PATCH v4 05/20] xfs: insert newly allocated inode chunks into the finobt Brian Foster
2014-05-07 12:21 ` [PATCH v4 06/20] xfs: use and update the finobt on inode allocation Brian Foster
2014-05-07 12:21 ` [PATCH v4 07/20] xfs: refactor xfs_difree() inobt bits into xfs_difree_inobt() helper Brian Foster
2014-05-07 12:21 ` [PATCH v4 08/20] xfs: update the finobt on inode free Brian Foster
2014-05-07 12:21 ` [PATCH v4 09/20] xfs: report finobt status in fs geometry Brian Foster
2014-05-07 12:21 ` [PATCH v4 10/20] xfs: enable the finobt feature on v5 superblocks Brian Foster
2014-05-07 12:21 ` [PATCH v4 11/20] xfsprogs/mkfs: finobt mkfs support Brian Foster
2014-05-07 12:21 ` [PATCH v4 12/20] xfsprogs/db: finobt support Brian Foster
2014-05-07 12:21 ` [PATCH v4 13/20] xfsprogs/repair: account for finobt in ag 0 geometry pre-calculation Brian Foster
2014-05-07 12:21 ` [PATCH v4 14/20] xfsprogs/repair: phase 2 finobt scan Brian Foster
2014-05-07 12:21 ` [PATCH v4 15/20] xfsprogs/repair: pass btree block magic as param to build_ino_tree() Brian Foster
2014-05-07 12:21 ` [PATCH v4 16/20] xfsprogs/repair: pull the build_agi() call up out of the inode tree build Brian Foster
2014-05-07 12:21 ` Brian Foster [this message]
2014-05-07 12:21 ` [PATCH v4 18/20] xfsprogs/repair: reconstruct the finobt in phase 5 Brian Foster
2014-05-07 12:21 ` [PATCH v4 19/20] xfsprogs/growfs: report finobt status in fs geometry (xfs_info) Brian Foster
2014-05-07 12:21 ` [PATCH v4 20/20] xfsprogs/db: add finobt support to metadump Brian Foster
2014-05-26 22:40 ` [PATCH v4 00/20] xfsprogs: introduce the free inode btree Dave Chinner
2014-05-27 12:06 ` 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=1399465319-65066-18-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