public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-block@vger.kernel.org, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Assumption on fixed device numbers in Plasma's desktop search Baloo
Date: Sat, 26 Jun 2021 12:18:26 +0200	[thread overview]
Message-ID: <3602587.1ANNM6WTHT@ananda> (raw)
In-Reply-To: <d24989e1-c8e0-d6c7-706e-2b5b8e9b124c@gmx.com>

Qu Wenruo - 26.06.21, 11:33:17 CEST:
> > I am not aware of an option for fstab to mount this one first and
> > then the other second, but I could set the second mount to noauto
> > and mount it when I need it.
> > 
> >> But this also means, all later subvolumes not in the fixed
> >> mount/read sequence can not get a fixed number.
> > 
> > I somehow thought this would get complicated.
> 
> It's already complicated.
> 
> So this just proves Neil is right, device number is only reliable at
> the lifespan of the fs, nothing else.

Thank you again.

I informed upstream about the conclusions from this thread.

Let's see what they come up with.

They have an energy efficiency goal, for that it would be desirable to 
stop indexing files twice or thrice or even more times. :)

Best,
-- 
Martin



  reply	other threads:[~2021-06-26 10:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 19:06 Assumption on fixed device numbers in Plasma's desktop search Baloo Martin Steigerwald
2021-06-26  0:27 ` Qu Wenruo
2021-06-26  8:49   ` Martin Steigerwald
2021-06-26  9:33     ` Qu Wenruo
2021-06-26 10:18       ` Martin Steigerwald [this message]
2021-06-26  0:54 ` NeilBrown
2021-06-26  3:38   ` Bart Van Assche
2021-06-26  5:17     ` NeilBrown
2021-06-26  6:14       ` Andrei Borzenkov
2021-06-26  6:24         ` Qu Wenruo
2021-06-26  8:51   ` Martin Steigerwald

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=3602587.1ANNM6WTHT@ananda \
    --to=martin@lichtvoll.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox