xfs
[Top] [All Lists]

Re: REVIEW: xfs_reno #2

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: REVIEW: xfs_reno #2
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 19 Nov 2007 09:52:45 -0600
Cc: Timothy Shimmin <tes@xxxxxxx>, Vlad Apostolov <vapo@xxxxxxx>, Barry Naujok <bnaujok@xxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>, xfs-dev <xfs-dev@xxxxxxx>
In-reply-to: <20071119123918.GA15942@xxxxxxxxxxxxx>
References: <op.tznnweh23jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <473D32D9.2020500@xxxxxxx> <473D36AC.7040507@xxxxxxx> <20071119123918.GA15942@xxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
Christoph Hellwig wrote:
> 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?
> 
> 

The ones not yet released I guess :)

>> Vlad Apostolov wrote:
>>> When the XFS parent pointers feature is released...

-Eric


<Prev in Thread] Current Thread [Next in Thread>