| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: REVIEW: xfs_reno #2 |
| From: | Vlad Apostolov <vapo@xxxxxxx> |
| Date: | Tue, 20 Nov 2007 09:08:12 +1100 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Timothy Shimmin <tes@xxxxxxx>, Barry Naujok <bnaujok@xxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>, xfs-dev <xfs-dev@xxxxxxx> |
| In-reply-to: | <4741B14D.8020004@xxxxxxxxxxx> |
| References: | <op.tznnweh23jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <473D32D9.2020500@xxxxxxx> <473D36AC.7040507@xxxxxxx> <20071119123918.GA15942@xxxxxxxxxxxxx> <4741B14D.8020004@xxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.6 (X11/20070728) |
Eric Sandeen wrote: It is a released and existing feature on XFS for Irix, that we are back porting toChristoph 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 :) Linux. You will see some patches soon. Regards, Vlad Vlad Apostolov wrote:When the XFS parent pointers feature is released...-Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS crash on linux raid, Alexander Bergolth |
|---|---|
| Next by Date: | Re: XFS crash on linux raid, Chris Wedgwood |
| Previous by Thread: | Re: REVIEW: xfs_reno #2, Eric Sandeen |
| Next by Thread: | Re: REVIEW: xfs_reno #2, Lachlan McIlroy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |