From: bzzz.tomas at gmail.com <bzzz.tomas@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] changelog for whole filesystem?
Date: Wed, 27 Oct 2010 17:17:31 +0400 [thread overview]
Message-ID: <4CC8266B.8020903@gmail.com> (raw)
In-Reply-To: <855B43E2-1D24-4095-ABE7-643A3ADAD67D@oracle.com>
On 10/27/10 5:06 PM, Andreas Dilger wrote:
> I had an interesting idea today during a discussion on HSM. One of the issues with enabling HSM today is that a full-filesystem scan must be done initially to populate the policy engine database.
>
> I was thinking that it would be useful to have a virtual changelog that provides a feed from internally traversing the whole filesystem in an efficient manner. For bug 22741 we have implemented a virtual index in the OSD which will return all of the in-use ldiskfs inodes in inode-number order (which is the fastest way to read/stat all of the inodes). It probably wouldn't be too hard to hook this OSD callback into the changelog API, so that reading a special changelog file would return all of the files in the filesystem. It is possible to generate the full pathnames of these inodes via the "link" xattr, if that is needed.
probably you meant to iterate over OI ?
thanks, z
next prev parent reply other threads:[~2010-10-27 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 13:06 [Lustre-devel] changelog for whole filesystem? Andreas Dilger
2010-10-27 13:17 ` bzzz.tomas at gmail.com [this message]
2010-10-28 9:04 ` Andreas Dilger
2010-10-27 15:28 ` LEIBOVICI Thomas
2010-10-28 9:15 ` Andreas Dilger
2010-10-28 13:43 ` LEIBOVICI Thomas
2010-10-29 16:50 ` Eric Barton
2010-11-02 6:42 ` Andreas Dilger
2010-11-11 4:15 ` Nathan Rutman
2010-11-11 18:10 ` Eric Barton
2010-11-12 23:41 ` Robert Read
2010-11-12 23:58 ` Andreas Dilger
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=4CC8266B.8020903@gmail.com \
--to=bzzz.tomas@gmail.com \
--cc=lustre-devel@lists.lustre.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.