On Fri, Aug 23, 2013 at 4:00 AM, Alexandre Oliva <oliva@xxxxxxx> wrote: > On Aug 22, 2013, "Yan, Zheng" <ukernel@xxxxxxxxx> wrote: > >> This is not bug. Only the tail entry of the path encoded in the parent xattrs >> need to be updated. (the entry for inode's parent directory) > > Why store the others, if they're not usable, then? IMHO it just > introduces a risk of their being accidentally misused. We want to write a correct path whenever we touch the file, but we don't want to have to go out to each file's object in order to complete a directory rename. So for a given file object we consider only the immediate parent to be authoritative, but keep around the full path for disaster recovery. This is why each path is versioned. If we are touching the file's ancestor xattr and not updating the whole thing, that would be a bug, but I don't think that's what you're describing? -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
