From: Martin Steigerwald <martin@lichtvoll.de>
To: NeilBrown <neilb@suse.de>
Cc: linux-block@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: Assumption on fixed device numbers in Plasma's desktop search Baloo
Date: Sat, 26 Jun 2021 10:51:59 +0200 [thread overview]
Message-ID: <1769070.0rzTUBzp5V@ananda> (raw)
In-Reply-To: <162466884942.28671.6997551060359774034@noble.neil.brown.name>
NeilBrown - 26.06.21, 02:54:09 CEST:
> > And that Baloo needs an "invariant" for
>
> > a file. See comment #11 of that bug report:
> That is really hard to provide in general. Possibly the best approach
> is to use the statfs() systemcall to get the "f_fsid" field. This is
> 64bits. It is not supported uniformly well by all filesystems, but I
> think it is at least not worse than using the device number. For a
> lot of older filesystems it is just an encoding of the device number.
>
> For btrfs, xfs, ext4 it is much much better.
Thank you for the clear statement and for your alternative suggestion. I
will forward this to Baloo upstream.
I think the main focus of Baloo would be to work on currently mostly in
use Linux filesystem which should be BTRFS, XFS, EXT4 and probably F2FS.
--
Martin
prev parent reply other threads:[~2021-06-26 8:52 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
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 [this message]
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=1769070.0rzTUBzp5V@ananda \
--to=martin@lichtvoll.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).