From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v2 13/20] xfsprogs/repair: account for finobt in ag 0 geometry pre-calculation
Date: Wed, 13 Nov 2013 10:56:15 -0500 [thread overview]
Message-ID: <1384358182-37967-14-git-send-email-bfoster@redhat.com> (raw)
In-Reply-To: <1384358182-37967-1-git-send-email-bfoster@redhat.com>
Account for the finobt in calc_mkfs().
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
repair/xfs_repair.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/repair/xfs_repair.c b/repair/xfs_repair.c
index a863337..fbc2d7d 100644
--- a/repair/xfs_repair.c
+++ b/repair/xfs_repair.c
@@ -404,6 +404,8 @@ calc_mkfs(xfs_mount_t *mp)
bcntbt_root = bnobt_root + 1;
inobt_root = bnobt_root + 2;
fino_bno = inobt_root + XFS_MIN_FREELIST_RAW(1, 1, mp) + 1;
+ if (xfs_sb_version_hasfinobt(&mp->m_sb))
+ fino_bno++;
/*
* If the log is allocated in the first allocation group we need to
--
1.8.1.4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-13 15:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 15:56 [PATCH v2 00/20] xfsprogs: introduce the free inode btree Brian Foster
2013-11-13 15:56 ` [PATCH v2 01/20] xfs: refactor xfs_ialloc_btree.c to support multiple inobt numbers Brian Foster
2013-11-13 15:56 ` [PATCH v2 02/20] xfs: reserve v5 superblock read-only compat. feature bit for finobt Brian Foster
2013-11-13 15:56 ` [PATCH v2 03/20] xfs: support the XFS_BTNUM_FINOBT free inode btree type Brian Foster
2013-11-13 15:56 ` [PATCH v2 04/20] xfs: update inode allocation/free transaction reservations for finobt Brian Foster
2013-11-13 15:56 ` [PATCH v2 05/20] xfs: insert newly allocated inode chunks into the finobt Brian Foster
2013-11-13 15:56 ` [PATCH v2 06/20] xfs: use and update the finobt on inode allocation Brian Foster
2013-11-13 15:56 ` [PATCH v2 07/20] xfs: refactor xfs_difree() inobt bits into xfs_difree_inobt() helper Brian Foster
2013-11-13 15:56 ` [PATCH v2 08/20] xfs: update the finobt on inode free Brian Foster
2013-11-13 15:56 ` [PATCH v2 09/20] xfs: report finobt status in fs geometry Brian Foster
2013-11-13 15:56 ` [PATCH v2 10/20] xfs: enable the finobt feature on v5 superblocks Brian Foster
2013-11-13 15:56 ` [PATCH v2 11/20] xfsprogs/mkfs: finobt mkfs support Brian Foster
2013-11-13 15:56 ` [PATCH v2 12/20] xfsprogs/db: finobt support Brian Foster
2013-11-13 15:56 ` Brian Foster [this message]
2013-11-13 15:56 ` [PATCH v2 14/20] xfsprogs/repair: phase 2 finobt scan Brian Foster
2013-11-13 15:56 ` [PATCH v2 15/20] xfsprogs/repair: pass btree block magic as param to build_ino_tree() Brian Foster
2013-11-13 15:56 ` [PATCH v2 16/20] xfsprogs/repair: pull the build_agi() call up out of the inode tree build Brian Foster
2013-11-13 15:56 ` [PATCH v2 17/20] xfsprogs/repair: helpers for finding in-core inode records w/ free inodes Brian Foster
2013-11-13 15:56 ` [PATCH v2 18/20] xfsprogs/repair: reconstruct the finobt in phase 5 Brian Foster
2013-11-13 15:56 ` [PATCH v2 19/20] xfsprogs/growfs: report finobt status in fs geometry (xfs_info) Brian Foster
2013-11-13 15:56 ` [PATCH v2 20/20] xfsprogs/db: add finobt support to metadump 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=1384358182-37967-14-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