From: Ruben Porras <ruben.porras@linworks.de>
To: xfs@oss.sgi.com
Subject: porting xfs_reno to linux
Date: Tue, 13 Nov 2007 19:20:59 +0100 [thread overview]
Message-ID: <4739EB0B.6030407@linworks.de> (raw)
Let's go back to the shrink xfs theme.
> 2. Move inodes out of offline AGs
> - On Irix, we have a program called 'xfs_reno' which
> converts 64 bit inode filesystems to 32 bit inode
> filesystems. This needs to be:
> - released under the GPL (should not be a problem).
done
> - ported to linux
Do you mean, rewrite the program to work on kernel space, or just port it to glibc?
Doing most of it on user land is easier, xfs_reno is already there, but it requires the AGs of the file system which are going to disappear to be traversed several times. It is needed to traverse each 'marked' AG one time to find its list of inodes. Then these inodes are going to be looked up during xfs_reno operation again several times (e.g. while copying attributes, linking and unlinking files...)
is these information cached?
On the other side on kernel space it can be done without going through the ioctls.
> - modified to understand inodes sit in certain
> AGs and to move them out of those AGs as needed.
> - requires filesystem traversal to find all the
> inodes to be moved.
To accomplish this I would write a function that traverses all the 'marked' AGs and return the list of ids to reallocate. These list could be exported through an ioctl to user space if needed. I don't find any function that traverses an AG, I've only seen functions to look up the records of an inode. Is there any function that do something similar or do I need to write if from scratch? Where can I find examples of it? is xfs_inobt_lookup the best one?
Thanks.
--
Rubén Porras
LinWorks GmbH
next reply other threads:[~2007-11-13 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 18:20 Ruben Porras [this message]
2007-11-13 21:00 ` porting xfs_reno to linux David Chinner
2007-11-14 14:19 ` Ruben Porras
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=4739EB0B.6030407@linworks.de \
--to=ruben.porras@linworks.de \
--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