On Wed, 18 Dec 2013, Alexandre Oliva wrote: > On Dec 18, 2013, "Yan, Zheng" <ukernel@xxxxxxxxx> wrote: > > > On Tue, Dec 17, 2013 at 7:25 PM, Alexandre Oliva <oliva@xxxxxxx> wrote: > >> # setfattr -n ceph.parent /cephfs/mount/path/name Can we add an additional prefix indicating that this is a debug/developer kludge that is not intended to be supported in the long-term? ceph.dev.force_rewrite_backtrace or something? sage > > > This seems like a good solution for fixing cephfs that was created > > before dumpling. > > There's more to it than just that, actually. Renaming an entire subtree > won't update the parent attribute of files in there, so they will appear > to be incorrect (*). This patch introduces a mechanism that could be > used to force them to be updated. > > (*) I'm well aware that they contain enough information to find the > updated information, so the redundant info in this attribute can be > harmlessly out-of-date, but if someone plans to use the data for other > purposes (like I sometimes do), it's useful to have them fully up to > date. I also move large trees around, which makes this issue visible. > > -- > Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ > You must be the change you wish to see in the world. -- Gandhi > Be Free! -- http://FSFLA.org/ FSF Latin America board member > Free Software Evangelist Red Hat Brazil Compiler Engineer > -- > 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 > > -- 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
