|To:||Timothy Shimmin <tes@xxxxxxx>|
|Subject:||Re: REVIEW: xfs_reno #2|
|From:||Christoph Hellwig <hch@xxxxxxxxxxxxx>|
|Date:||Mon, 19 Nov 2007 12:39:18 +0000|
|Cc:||Vlad Apostolov <vapo@xxxxxxx>, Barry Naujok <bnaujok@xxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>, xfs-dev <xfs-dev@xxxxxxx>|
|References:||<firstname.lastname@example.org> <473D32D9.email@example.com> <473D36AC.firstname.lastname@example.org>|
On Fri, Nov 16, 2007 at 05:20:28PM +1100, Timothy Shimmin wrote: > Vlad Apostolov wrote: > > > >When the XFS parent pointers feature is released we would need to find > >out to update the EA to point to the new inode parent directory. This may > >not be that easy though. > > > Really? > Apart from the swapping of extents, reno uses standard calls doesn't it, > in which case any movement of inodes will have the parent pointers > updated by the normal vnode ops (e.g. mkdir, rename) in the kernel. What parent pointers?
|<Prev in Thread]||Current Thread||[Next in Thread>|