From: Jorge Guerra <jorge.guerra@gmail.com>
To: linux-xfs@vger.kernel.org
Cc: osandov@osandov.com, Jorge Guerra <jorgeguerra@fb.com>
Subject: [PATCH] xfs_db: Scan entire file system when using 'frag'
Date: Fri, 26 Apr 2019 15:59:20 -0700 [thread overview]
Message-ID: <20190426225920.34359-1-jorgeguerra@gmail.com> (raw)
From: Jorge Guerra <jorgeguerra@fb.com>
While running the 'frag' command of 'xfs_db' we noticed that the
tool is not scanning all the files in the file system. We noticed
this when we modified the tool to print the inodes of all the files
scanned. For example:
$ find /mnt/xfsdisk -type f | wc -l
1782674
$ xfs_db -r -c frag /dev/sdXX | grep MB | awk '{print $5}' | paste -s -d+ | bc
656818
Upon inspecting the code we noticed that the scanfunc_ino function
stops processing a given inode block once it encounters a free leaf.
However, in practice we see that inodes are necessarily always layed
out contiguously on the leaf node. This resulted in the 'frag'
command skipping some valid inodes.
In this change we modify the scanfunc_ino function to skip freed
inodes. With the change in place we ran the same experiment again
and noticed a more accurate file count:
$ find /mnt/d0 -type f | wc -l
1810442
$ xfs_db -r -c frag /dev/sdXX | grep MB | awk '{print $5}' | paste -s -d+ | bc
1810442
Signed-off-by: Jorge Guerra <jorgeguerra@fb.com>
---
db/frag.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/db/frag.c b/db/frag.c
index 5f33cb73..91395234 100644
--- a/db/frag.c
+++ b/db/frag.c
@@ -507,7 +507,7 @@ scanfunc_ino(
for (j = 0; j < inodes_per_buf; j++) {
if (XFS_INOBT_IS_FREE_DISK(&rp[i], ioff + j))
- goto next_buf;
+ continue;
dip = (xfs_dinode_t *)((char *)iocur_top->data +
((off + j) << mp->m_sb.sb_inodelog));
process_inode(agf, agino + ioff + j, dip);
--
2.13.5
next reply other threads:[~2019-04-26 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 22:59 Jorge Guerra [this message]
2019-04-27 0:13 ` [PATCH] xfs_db: Scan entire file system when using 'frag' Eric Sandeen
2019-04-27 1:24 ` Darrick J. Wong
2019-04-27 3:32 ` Jorge Guerra
2019-04-27 3:32 ` Jorge Guerra
2019-04-27 10:51 ` Eric Sandeen
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=20190426225920.34359-1-jorgeguerra@gmail.com \
--to=jorge.guerra@gmail.com \
--cc=jorgeguerra@fb.com \
--cc=linux-xfs@vger.kernel.org \
--cc=osandov@osandov.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