linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Fixed subject: updatedb does not index separately mounted btrfs subvolumes
Date: Sun, 5 Nov 2017 07:02:16 -0700	[thread overview]
Message-ID: <CAJCQCtQdz0zEesU0SuHCs5-bhqohqT7zEnh7krY-aiVgHGfSKw@mail.gmail.com> (raw)
In-Reply-To: <pan$94157$844c1b67$c8d5af52$b34db269@cox.net>

On Sun, Nov 5, 2017 at 1:47 AM, Duncan <1i5t5.duncan@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

  reply	other threads:[~2017-11-05 14:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04  0:15 updatedb does not index /home when /home is Btrfs Chris Murphy
2017-11-04  4:49 ` Adam Borowski
2017-11-04  6:26   ` Andrei Borzenkov
2017-11-04  7:05     ` Adam Borowski
2017-11-04 18:27       ` Andrei Borzenkov
2017-11-04 18:55         ` Chris Murphy
2017-11-04 19:37           ` Nicholas D Steeves
2017-11-05  8:01           ` Andrei Borzenkov
2017-11-06 13:51             ` Austin S. Hemmelgarn
2017-11-06 18:35               ` Chris Murphy
2017-11-06 19:44                 ` Austin S. Hemmelgarn
2017-11-05  7:47 ` Fixed subject: updatedb does not index separately mounted btrfs subvolumes Duncan
2017-11-05 14:02   ` Chris Murphy [this message]
2017-11-06  0:27   ` Peter Grandi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJCQCtQdz0zEesU0SuHCs5-bhqohqT7zEnh7krY-aiVgHGfSKw@mail.gmail.com \
    --to=lists@colorremedies.com \
    --cc=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    --subject='Re: Fixed subject: updatedb does not index separately mounted btrfs subvolumes' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).