On Fri, 2007-06-15 at 17:20 +1000, Timothy Shimmin wrote:
> David Chinner wrote:
> > On Mon, Jun 11, 2007 at 08:51:32AM +0200, Johan Andersson wrote:
> >> Does anyone know of a good way to find one filename that points o a
> >> certain inode?
> >
> > We need an rmap....
> >
> > We have some prototype linux code that does parent pointers (i.e.
> > each inode has a back pointer to it's parent inode), but that, IIUC,
> > is a long way from prime-time. Tim?
> >
> > Cheers,
> >
> > Dave.
>
> I don't know about a "long way" (longer to fully supported, yes)
> Firstly, I need to move its hooks out of linux-2.6/xfs_iops.c which were
> referring to xfs inodes (instead of vnodes) probably back where they were in
> xfs_vnodeops.c.
>
> Nathan, did you have some other suggestion than this - unfortunately,
> I haven't looked at this code (until recently) for a while.
>
> Cheers,
> Tim.
>
I have another idea that i plan to try. The idea was to add an ioctl to
"clone" an inode. By using the original inode (the one to be
defragmented) as parent "directory" in the call to xfs_dir_ialloc(), the
new inode should be allocated near the original inode. The fsr can then
open the new inode with jdm_open and proceed as normal.
This would also solve another problem that I see with fsr, the mtime of
every directory in the fs is updated when fsr is run.
I do see one problem with this: If the defrag is aborted for some
reason, we can get orphaned inodes. Will fsck handle this?
/Johan Andersson
|