From: David Chinner <dgc@sgi.com>
To: Fong Vang <sudoyang@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_check and xfs_repair internal working details
Date: Tue, 22 Apr 2008 08:02:21 +1000 [thread overview]
Message-ID: <20080421220221.GQ108924158@sgi.com> (raw)
In-Reply-To: <4f52331f0804211257n47c1d21fiffb6d07235c5b302@mail.gmail.com>
On Mon, Apr 21, 2008 at 12:57:22PM -0700, Fong Vang wrote:
> I would like to find how how xfs_check and xfs_repair do their work
> internally. I need to find answers to the following questions:
Read the source code - the answers are all there.
> a) assuming the amount of data is the same for file systems, does it take
> longer for xfs_check and xfs_repair to check/repair a file system with a lot
> more files than one that has fewer? Assuming two file systems are 1TB each
> completely filled. One of the file systems is filled with very large files
> while the other one is filled with very small files, does it take longer to
> check and repair the latter?
The obvious thing here is to try it and measure it. Or perhaps go download
the slides/video/audio from this talk:
http://linux.conf.au/programme/detail?TalkID=135
The slides:
http://mirror.linux.org.au/pub/linux.conf.au/2008/slides/135-fixing_xfs_faster.pdf
And that should answer your question.
> b) does xfs_check and repair check only the used blocks or does it check
> everything? I think there's a free list as well so I'm assuming it checks
> that list as well.
Pretty much everything is checked and/or repaired. If it is not, then that's
a bug.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-04-21 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 19:57 xfs_check and xfs_repair internal working details Fong Vang
2008-04-21 22:02 ` David Chinner [this message]
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=20080421220221.GQ108924158@sgi.com \
--to=dgc@sgi.com \
--cc=sudoyang@gmail.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