From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: reduce bb_numrecs in bno/cnt btrees when log consumes all agf space
Date: Mon, 18 Mar 2013 18:29:11 -0400 [thread overview]
Message-ID: <51479537.7010905@redhat.com> (raw)
In-Reply-To: <1363642689-17718-1-git-send-email-bfoster@redhat.com>
On 03/18/2013 05:38 PM, Brian Foster wrote:
> The mkfs code currently creates a single free space extent record
> for each of the bno and cnt btrees in each AG. The start block of
> the record is pushed forward on the AG that hosts an internal log.
> If the log happens to consume all available space in the AG, the
> start block becomes equal to sb->sb_agblocks and thus invalid.
> This causes xfs_repair to complain.
>
> For example, the following sequence:
>
> mkfs.xfs -d file,name=./fs.img,size=50g,agsize=16m
> xfs_repair ./fs.img
>
> ... produces the following xfs_repair output:
>
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - scan filesystem freespace and inode maps...
> invalid start block 4096 in record 0 of bno btree block 1600/1
> invalid start block 4096 in record 0 of cnt btree block 1600/2
> - found root inode chunk
> ...
>
> xfs_repair appears to correct the numrecs value such that subsequent
> checks are successful. The sequence above is pulled from xfstests
>
For some reason my commit log got munged here. :/ This should say this
was "pulled from xfstests #250, which fails due to this behavior." I'll
send out a v2 with at least a new commit log when this gets some review...
Brian
> Modify mkfs.xfs such that we check the block count value of the
> free space record for the log AG after the log is accounted for. If
> no space is left for the record, reset the record count to 0.
>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
> mkfs/xfs_mkfs.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index c84448e..c4ae15b 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -2594,6 +2594,9 @@ an AG size that is one stripe unit smaller, for example %llu.\n"),
> }
> arec->ar_blockcount = cpu_to_be32(agsize -
> be32_to_cpu(arec->ar_startblock));
> + if (!arec->ar_blockcount)
> + block->bb_numrecs = cpu_to_be16(0);
> +
> libxfs_writebuf(buf, LIBXFS_EXIT_ON_FAILURE);
>
> /*
> @@ -2627,6 +2630,9 @@ an AG size that is one stripe unit smaller, for example %llu.\n"),
> }
> arec->ar_blockcount = cpu_to_be32(agsize -
> be32_to_cpu(arec->ar_startblock));
> + if (!arec->ar_blockcount)
> + block->bb_numrecs = cpu_to_be16(0);
> +
> libxfs_writebuf(buf, LIBXFS_EXIT_ON_FAILURE);
>
> /*
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-18 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 21:38 [PATCH] xfsprogs: reduce bb_numrecs in bno/cnt btrees when log consumes all agf space Brian Foster
2013-03-18 22:29 ` Brian Foster [this message]
2013-03-18 23:16 ` Dave Chinner
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=51479537.7010905@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