On Sun, Nov 5, 2017 at 1:47 AM, Duncan <1i5t5.dun...@cox.net> wrote: > Chris Murphy posted on Fri, 03 Nov 2017 18:15:53 -0600 as excerpted: > >> Ancient bug, still seems to be a bug. >> https://bugzilla.redhat.com/show_bug.cgi?id=906591 >> >> The issue is that updatedb by default will not index bind mounts, but by >> default on Fedora and probably other distros, put /home on a subvolume >> and then mount that subvolume which is in effect a bind mount. > > <gripe-mode: inaccurate subject lines> > > So the issue isn't /home being btrfs (as you said in the subject), but > rather, it's /home being an explicitly mounted subvolume, since btrfs > uses bind-mounts internally for subvolume mounts. > > Makes a difference for folks like me who have /home on a fully separate > btrfs. You had me wondering for a moment, tho as it happens I don't use > updatedb either, but I was still wondering what weird bug and how it > might otherwise affect me. An accurate subject line would have helped...
It is accurate, it's an exactly copied title from the bug report. That the bug report's title is confusing is sorta beside the point, I certainly can't do anything about that. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
