Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@IntrusionCM I took a video of me checking the size of the file this morning (sorry about the tiktok, it's the easiest I could think of at the moment)
https://vm.tiktok.com/ZSe8cdWbh/ -
@NoOneCares yes, that's the one. I wouldn't be too quick to blame Baloo though, this is from a failing disk after all.
zpool status doesn't show any corruption on this file though and the disk started failing at the time I installed and tried to start the plasma desktop. It's very possible that other disk issues causes Baloo to fill this file with 0's or something repeating, hence the insane compression.
I am the reference. Like a Boss :)
Finally, tar compression for crowded families!
I was copying data from a failing zfs drive with rsync and I noticed that it spent a long time on the file ~/.local/share/Baloo/index
du -h index showed a 500ish MB file which didn't seem large enough to take this long.
I recalled that du shows disk usage, not file size and since I was using zfs compression they could be quite different.
so I added -A for apparent size:
du -hA index and it comes back with 1.7E
The file was 1.7 exabytes...
rant
failing drive
baloo
freebsd
compression
ssd
zfs