On Fri, Jan 9, 2015 at 10:00 AM, Sage Weil <[email protected]> wrote: > On Fri, 9 Jan 2015, Gregory Farnum wrote: >> On Fri, Jan 9, 2015 at 7:20 AM, Sage Weil <[email protected]> wrote: >> > Should we drop this entirely in hammer? >> >> Yes! >> >> > If I remember correctly all of >> > the layout stuff is fully supported using virtual xattrs and standard >> > tools. The only thing left is the tool that shows you how file blocks map >> > to objects map to OSDs (or something like that), which I've never used and >> > have never seen anyone use... >> >> ...oh, hmmm. Actually there have been people using that tool >> occasionally over the years, and I don't think we provide any other >> way to learn that information (besides calculating it yourself, >> obviously). >> Perhaps we could extend the vxattr interface to include that >> information as well? > > Actually, I think Andreas's librados stuff he's working on may be the > right path... it'll expose general information about object -> pg -> > osd mappings. Then a simple script could take the ino + file size, turn > it into object names, and use that. > > In any case, I don't mind nuking this and waiting for a complaint before > investing in replacing that bit of functionality since it's such a small > thing...
Yeah, that's fine with me, but I'd like some idea of how we'd suggest any users who complain do the implementation so we can point them at a ticket if they do complain. ;) -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
