https://bugs.kde.org/show_bug.cgi?id=409587
Mads Peter Rommedahl <madspe...@rommedahl.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |madspe...@rommedahl.info
--- Comment #3 from Mads Peter Rommedahl <madspe...@rommedahl.info> ---
I'm not sure from the existing comments whether more info is needed, but I can
add that I encounter this bug as well.
I have a music collection of 1.4 TB on a NAS which is mounted to `~/Music` by
`/etc/fstab`. Baloo has successfully indexed everything and in my case, I can
easily start elisa without issues. The only time I encounter the bogus 'No
space left on device' errors is when going to elisa and clicking 'Refresh Music
Collection', as that seems to get elisa to start indexing everything from
scratch all over, and after the first few minutes of scanning, the "no space"
errors start cropping up.
--
You are receiving this mail because:
You are watching all bug changes.
