https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #66 from tagwer...@innerjoin.org ---
Worth being aware of Bug 475919
The "one off" reindexing done after the fix also includes machines that did not
previously reindex the folders, basic ext4 setups for example.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #65 from Martin Steigerwald ---
Thank you dearly for fixing this long standing issue!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
Martin Steigerwald changed:
What|Removed |Added
CC||mar...@lichtvoll.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #64 from Matija Šuklje ---
Fixed in 5.111, sweet! Thank you! :D
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
Version Fixed In|6.0 |5.111
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #63 from tagwer...@innerjoin.org ---
(In reply to Matija Šuklje from comment #62)
> ... will it be backported to KF5 ...
There were two commit messages... the second mentions kf5
(In reply to Nate Graham from comment #61)
> Pushed by
https://bugs.kde.org/show_bug.cgi?id=402154
Matija Šuklje changed:
What|Removed |Added
CC||mat...@suklje.name
--- Comment #62 from Matija
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
Version Fixed In||6.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=402154
kilgore.tr...@idesmi.eu changed:
What|Removed |Added
CC||kilgore.tr...@idesmi.eu
--
You are
https://bugs.kde.org/show_bug.cgi?id=402154
Dmitrii Chermnykh changed:
What|Removed |Added
CC||chermnykh2...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=402154
Cristiano Canguçu changed:
What|Removed |Added
CC||cristiano.figue...@gmail.co
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #59 from Peter Hoeg ---
There has been nothing official from KDE about this patch getting merged, so
it’s too early to say anything about which release it will be in.
That being said, we will start carrying this in NixOS as it is a huge
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #58 from Joachim Wagner ---
For those of us who cannot install a patch, what version of KDE do we need to
wait for? Will it go into 5.27.6?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
CC||m...@elbmurf.de
--- Comment #57 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #56 from Peter Hoeg ---
(In reply to André M from comment #52)
> I've been testing the patch on NixOS on kf 5.106, and it's working great
FWIW, I've been running with this patch for some time now (also on NixOS) and
it works beautifully
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #55 from tagwer...@innerjoin.org ---
(In reply to André M from comment #54)
> ... the best way I know would be to replace the whole plasma5Packages scope
> using an overlay ...
Thank you. That looks way, way deeper than anything I've tried
https://bugs.kde.org/show_bug.cgi?id=402154
Jure Repinc changed:
What|Removed |Added
CC||j...@holodeck1.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #54 from André M ---
(In reply to tagwerk19 from comment #53)
> (In reply to André M from comment #52)
> > I've been testing the patch on NixOS on kf 5.106, and it's working great
> > across 3 reboots of a couple of mounted subvolumes.
>
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #53 from tagwer...@innerjoin.org ---
(In reply to André M from comment #52)
> I've been testing the patch on NixOS on kf 5.106, and it's working great
> across 3 reboots of a couple of mounted subvolumes.
Can you share how you've done this?
https://bugs.kde.org/show_bug.cgi?id=402154
RM changed:
What|Removed |Added
CC||r...@richardmay.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #52 from André M ---
I've been testing the patch on NixOS on kf 5.106, and it's working great across
3 reboots of a couple of mounted subvolumes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #51 from tagwer...@innerjoin.org ---
(In reply to Nate Graham from comment #49)
> Nice, please do submit it as a merge request!
Does sound good, not least because it's starting to affect Fedora BTRFS
systems. Used to be nearly always
https://bugs.kde.org/show_bug.cgi?id=402154
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #50 from Bug
https://bugs.kde.org/show_bug.cgi?id=402154
postix changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=455434|
--
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #49 from Nate Graham ---
Nice, please do submit it as a merge request!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
soredake changed:
What|Removed |Added
CC|broaden_acid002@simplelogin |
|.com|
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #48 from Tomas Trnka ---
Created attachment 159031
--> https://bugs.kde.org/attachment.cgi?id=159031=edit
Patch making Baloo use the FSID as device ID
Until somebody implements one of the fancy solutions proposed in the comments
above,
https://bugs.kde.org/show_bug.cgi?id=402154
Neal Gompa changed:
What|Removed |Added
CC||ngomp...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=402154
Tomas Trnka changed:
What|Removed |Added
CC||tomastr...@gmx.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=402154
Peter Hoeg changed:
What|Removed |Added
CC||pe...@hoeg.com
--- Comment #47 from Peter Hoeg
https://bugs.kde.org/show_bug.cgi?id=402154
Dennis Schridde changed:
What|Removed |Added
CC||devuran...@gmx.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=402154
Dennis Schridde changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
Component|Baloo File Daemon |general
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=402154
matteo savini changed:
What|Removed |Added
CC||masav...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=402154
postix changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=402154
Michael K. changed:
What|Removed |Added
CC|f4tm...@web.de |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=402154
postix changed:
What|Removed |Added
Keywords||efficiency
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=402154
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402154
André M changed:
What|Removed |Added
CC||andre.vma...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=402154
euphonis...@outlook.com changed:
What|Removed |Added
CC||euphonis...@outlook.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #46 from Lukas Ba. ---
Thank you, Joachim Wagner and tagwer...@innerjoin.org for your insightful
comments, and Stefan Brüns and all the contributors for your efforts.
My inputs:
We need a way to list all the filesystems that are part of
https://bugs.kde.org/show_bug.cgi?id=402154
Moritz Herrmann changed:
What|Removed |Added
CC||moritzherrmann09+kde.org@gm
https://bugs.kde.org/show_bug.cgi?id=402154
soredake changed:
What|Removed |Added
CC||ndrzj1...@relay.firefox.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=402154
soredake changed:
What|Removed |Added
CC|ndrzj1...@relay.firefox.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #45 from tagwer...@innerjoin.org ---
(In reply to Joachim Wagner from comment #44)
> ... This phrasing is likely to cause confusion ...
Accepted. There are many layers (and history) here, thanks for the explanation.
The challenge is to find
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #44 from Joachim Wagner ---
> [...] home drive mounted with different
> minor device numbers
This phrasing is likely to cause confusion. Better to refer to the value
`stat.st_dev` that is used by baloo and that does not have a "minor":
*
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #43 from tagwer...@innerjoin.org ---
(In reply to Lukas Ba. from comment #42)
> ... ArchLinux, with multiple BTRFS subvolumes ...
You could try the tests in Comment 12, Comment 13
Very likely that baloo is "seeing" your home drive mounted
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #42 from Lukas Ba. ---
(In reply to tagwerk19 from comment #41)
> (In reply to Lukas Ba. from comment #40)
> > My baloo index file is 32GiB large right now, more than any other folder on
> > my file system, and my file system is filled up
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #41 from tagwer...@innerjoin.org ---
(In reply to Lukas Ba. from comment #40)
> My baloo index file is 32GiB large right now, more than any other folder on
> my file system, and my file system is filled up by 100%, my PC crashed
> during an
https://bugs.kde.org/show_bug.cgi?id=402154
Lukas Ba. changed:
What|Removed |Added
CC||k...@web.de
--- Comment #40 from Lukas Ba. ---
My
https://bugs.kde.org/show_bug.cgi?id=402154
Jason Straight changed:
What|Removed |Added
CC||j.straight-...@straights.ne
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #39 from Joachim Wagner ---
(In reply to tagwerk19 from comment #38)
> Symlinks provide a bit of an edge case :-)
> [...]
> Does the "mount point" idea work here?
I don't know the internals of the indexer implementation so I cannot say for
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #38 from tagwer...@innerjoin.org ---
(In reply to Joachim Wagner from comment #37)
> (1) Symlinks to other folders: If the target folder is indexed anyway the
> link can be ignored. If not, the default probably should be not to follow
> the
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #37 from Joachim Wagner ---
(In reply to tagwerk19 from comment #35)
> Accepted.
> Although I think we need to look at "what we can trust most".
> [...]
> This would mean including the filesystem ID in your "I" table and careful
> making
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #36 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #35)
> ... mentioned Mandriva ...
Maybe Manjaro ...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #35 from tagwer...@innerjoin.org ---
(In reply to Joachim Wagner from comment #34)
> ... Hence my proposal
> to move away from system-provided IDs and to use the mount point
> as an identifier instead ...
Accepted.
Although I think we need
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #34 from Joachim Wagner ---
(In reply to tagwerk19 from comment #33)
> statvfs and "stat -f" give a 64 bit "Filesystem ID" and I was imagining you
> were talking about that.
No, I meant "baloo-internal filesystem ID", a sequentially
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #33 from tagwer...@innerjoin.org ---
(In reply to Joachim Wagner from comment #32)
> ... a given internal filesystem ID ...
Maybe that's where I'm getting muddled...
statvfs and "stat -f" give a 64 bit "Filesystem ID" and I was imagining
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #32 from Joachim Wagner ---
(In reply to tagwerk19 from comment #31)
> Apologies, I fear you'll have to step through your process for me. I'm
> somehow missing something...
> [...]
> The mapping would have to work when indexing (going from
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #31 from tagwer...@innerjoin.org ---
(In reply to Joachim Wagner from comment #29)
> An alternative to relying on UUIDs and sub-volume IDs is to assume mount
> points of filesystems do not change and to proceed as follows...
Apologies, I
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #30 from tagwer...@innerjoin.org ---
(In reply to Joachim Wagner from comment #28)
> https://github.com/util-linux/util-linux/issues/1562 .
Like :-)
Seems that there are two options here: a fix to filesystem/mount to permit a
"specified"
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #29 from Joachim Wagner ---
An alternative to relying on UUIDs and sub-volume IDs is to assume mount points
of filesystems do not change and to proceed as follows:
* Have a persistent table `I` mapping mount points to internal filesystem
https://bugs.kde.org/show_bug.cgi?id=402154
Joachim Wagner changed:
What|Removed |Added
CC||jwag...@computing.dcu.ie
--- Comment #28 from
https://bugs.kde.org/show_bug.cgi?id=402154
Massimiliano L changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=402154
Seqularise changed:
What|Removed |Added
CC||seqular...@outlook.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=402154
Rex Dieter changed:
What|Removed |Added
CC||rdie...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402154
Gurenko Alex changed:
What|Removed |Added
CC||agure...@protonmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=402154
Alexandre Bouvier changed:
What|Removed |Added
CC||abouv...@student.42.fr
--
You are
https://bugs.kde.org/show_bug.cgi?id=402154
Michael K. changed:
What|Removed |Added
CC||f4tm...@web.de
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402154
t.schmittla...@orlives.de changed:
What|Removed |Added
CC||t.schmittla...@orlives.de
---
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #26 from Stefan Brüns ---
Getting a stable ID is not the hard part, but changing everything in the
internals to use an indirection layer is.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #25 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #24)
> With further tests, too fragile :-(
Maybe the "subvolid" that findmnt gives you is better:
findmnt -T testfile.txt
reports the mount point, the filesystem
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #24 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #21)
> It is however possible to add "x-systemd.requires" options in the /etc/fstab
> that suggest "an order" that mounts are done in - and the device numbers
> seem to
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #23 from Stefan Brüns ---
There is nothing new to add here. Please refrain from any further comments, if
it does not any new information.
1. Baloo uses inodes and device ids as document IDs. inodes can be considered
stable on all supported
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #22 from Kai Krakow ---
(In reply to tagwerk19 from comment #20)
> (In reply to Kai Krakow from comment #18)
> > ... I suggest to
> > read that entirely to understand the problem ...
> I've done my best :-) Thank you for the info!
>
> In:
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #21 from tagwer...@innerjoin.org ---
As a workround in openSuse, my test install had a /etc/fstab:
UUID=19af1d21-f5c2-4518-a839-a3f2afdb199c / btrfs
defaults 0 0
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #20 from tagwer...@innerjoin.org ---
(In reply to Kai Krakow from comment #18)
> ... I suggest to
> read that entirely to understand the problem ...
I've done my best :-) Thank you for the info!
In:
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #19 from Kai Krakow ---
BTW: Such a UUID-to-deviceId mapping table would allow baloo to properly
support most yet unsupported filesystems, probably also zfs. With such an idea
implemented, the only requirement left to a supported filesystem
https://bugs.kde.org/show_bug.cgi?id=402154
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #18 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=402154
tagwer...@innerjoin.org changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #17 from tagwer...@innerjoin.org ---
Looks as if this is a long term issue...
Scroll down to the last posts in Bug 404057
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #16 from tagwer...@innerjoin.org ---
(In reply to Pierre Baldensperger from comment #14)
> Now hopefully somebody who knows the internals of baloo deduplication
> criteria might be able to understand where this behaviour is coming from,
>
https://bugs.kde.org/show_bug.cgi?id=402154
tagwer...@innerjoin.org changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #14 from Pierre Baldensperger
---
(In reply to tagwerk19 from comment #12)
>
> Try a simple test...
>
> (...)
>
> Interesting to know if the device number has changed, and whether the
> balooshow details have also changed...
Thank you
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #13 from tagwer...@innerjoin.org ---
This might also explain the instances of a search finding many copies or the
same file. Looking at the filesystem with many subvols:
$ df
Filesystem 1K-blocksUsed Available Use% Mounted
https://bugs.kde.org/show_bug.cgi?id=402154
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--- Comment
https://bugs.kde.org/show_bug.cgi?id=402154
Pierre Baldensperger changed:
What|Removed |Added
CC||baloo-bugs-n...@kde.org
https://bugs.kde.org/show_bug.cgi?id=402154
soredake changed:
What|Removed |Added
CC||ndrzj1...@relay.firefox.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #10 from Pierre Baldensperger
---
(In reply to Nate Graham from comment #5)
> You can thank Stefan for putting in tons and tons of work into Baloo. :)
>
> As of 5.76 I no longer have any problems like this. It currently gets stuck
> on
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #9 from Stefan Brüns ---
ZFS is not supported.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #8 from Eridani Rodríguez ---
My system seems to be affected too, in my case / is BTRFS while
/home/MyUser/Desktop or /home/MyUser/Music (and all other user folders) are on
separated ZFS datasets, none of them are encrypted, but both use
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
Version|5.57.0 |5.75.0
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Component|Baloo File Daemon
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #6 from Pierre Baldensperger
---
(In reply to Nate Graham from comment #5)
> You can thank Stefan for putting in tons and tons of work into Baloo. :)
>
> As of 5.76 I no longer have any problems like this. It currently gets stuck
> on one
https://bugs.kde.org/show_bug.cgi?id=402154
Nate Graham changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=402154
Eridani Rodríguez changed:
What|Removed |Added
CC||eridanired...@yahoo.com.mx
--
You are
https://bugs.kde.org/show_bug.cgi?id=402154
Pierre Baldensperger changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
1 - 100 of 105 matches
Mail list logo
