From: Timothy Shimmin <tes@sgi.com>
To: "Daniele P." <daniele@interline.it>
Cc: xfs@oss.sgi.com
Subject: Re: xfsdump -s unacceptable performances
Date: Thu, 17 Aug 2006 11:31:01 +1000 [thread overview]
Message-ID: <44E3C6D5.2080704@sgi.com> (raw)
In-Reply-To: <200608162001.10342.daniele@interline.it>
Daniele P. wrote:
> But xfsdump still doesn't scale down well with a small subtree on a
> large filesystem.
That is very true.
It is really designed for dumping whole filesystems (or at least,
large parts of them).
For dumping small subtrees, I'd be looking at using something else.
That was one of the 1st things I noticed when looking at the xfsdump
code on IRIX a while back, was all the scans it does and how for a subtree
it will do another scan and prune the data - i.e. implemented
like an afterthought :)
It is built around bulkstat which walks all the inodes which is great
for dumping them all out.
But if you want a small directory walk then you need something else IMHO.
Cheers,
--Tim
next prev parent reply other threads:[~2006-08-17 1:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 13:15 xfsdump -s unacceptable performances Daniele P.
2006-08-16 14:38 ` Klaus Strebel
2006-08-16 18:01 ` Daniele P.
2006-08-17 1:31 ` Timothy Shimmin [this message]
2006-08-17 6:58 ` Daniele P.
2006-08-17 12:29 ` Peter Grandi
2006-08-16 16:38 ` Bill Kendall
2006-08-16 18:05 ` Daniele P.
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=44E3C6D5.2080704@sgi.com \
--to=tes@sgi.com \
--cc=daniele@interline.it \
--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