https://bugs.kde.org/show_bug.cgi?id=333433
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #6 from tagwer...@innerjoin.org ---
(In reply to Torsten Eichstädt from comment #5)
> I guess Linux and other BSD have such unionfs, too. Would be helpful to
> track down the root cause of the issue, if s/o can fire up baloo on a setup
> like mine.
I've encountered something similar with mergerfs, see Bug 420939, comments from
49 onwards.
The issue was that the inode values "handed up" by mergerfs to baloo kept
changing. Baloo keeps thinking it's got new files.
The test is to do a
stat filename
You'll get something like:
$ stat 1.ts
File: 1.ts
Size: 41416704 Blocks: 80896 IO Block: 4096 regular file
Device: fc01h/64513d Inode: 794964 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 1000/ test) Gid: ( 1000/ test)
Access: 2021-07-24 22:50:57.838161084 +0200
Modify: 2021-07-24 22:50:57.838161084 +0200
Change: 2021-07-24 22:51:42.686181710 +0200
Birth: -
It's the "Device" and "Inode" numbers that you need to keep you eye on. The:
Device: fc01h/64513d Inode: 794964
If these values keep changing then you've pinned down the issue.
The solution with mergerfs was that it needed an "use_ino" option in the
/etc/fstab file
https://github.com/trapexit/mergerfs#inodecalc
I don't know if unionfs has or needs the equivalent but it would be something
to look at.
--
You are receiving this mail because:
You are watching all bug changes.
