| 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> |
| In-reply-to: | <473D36AC.7040507@sgi.com> |
| References: | <op.tznnweh23jf8g2@pc-bnaujok.melbourne.sgi.com> <473D32D9.2020500@sgi.com> <473D36AC.7040507@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.3i |
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> |
|---|---|---|
| ||
| Previous by Date: | Re: REVIEW: xfs_reno #2, Lachlan McIlroy |
|---|---|
| Next by Date: | Re: REVIEW: xfs_reno #2, Eric Sandeen |
| Previous by Thread: | Re: REVIEW: xfs_reno #2, Vlad Apostolov |
| Next by Thread: | Re: REVIEW: xfs_reno #2, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |