November 14, 2026
Ubuntu Disk Full Again? How I Found Ubuntu’s file-search indexer Bug & Recovered 40 GiB
My Ubuntu 24.04 disk kept filling despite daily deletions. With Codex, I investigated the growth to its source and resolved to get back…

By Anindya Majumder
2 min read
My Ubuntu 24.04 disk kept filling despite daily deletions. With Codex, I investigated the growth to its source and resolved to get back around 40GB.
Every day, I deleted something to make room. A download, a cache, whatever I could spare.
The free space returned briefly, then disappeared again.
A week earlier, storage hadn't been a problem. Now I was deleting files just to keep working. I asked Codex to help investigate.
I started by checking the disk:
df -h /df -h /99% full. Roughly 1.5 GiB available.
Docker, npm, and browser caches were obvious suspects. I ran these commands to find where the space was going:
sudo du -xhd1 / | sort -h
sudo du -xhd1 /var | sort -h
sudo du -xhd1 /var/log | sort -hsudo du -xhd1 / | sort -h
sudo du -xhd1 /var | sort -h
sudo du -xhd1 /var/log | sort -hSystem logs occupied 40.5 GiB. One file, /var/log/syslog.1, accounted for 35.58 GiB.
I had been deleting personal files while Ubuntu kept writing gigabytes of logs.
I checked what it was writing, and the same errors repeated:
Could not get mimetype … No such file or directory
Failed to update ignored file … ambiguous column name: ROWIDCould not get mimetype … No such file or directory
Failed to update ignored file … ambiguous column name: ROWIDThey came from Tracker, GNOME's file-search indexer.
Tracker was processing a temporary HTML file that no longer existed. Its attempt to mark the file as ignored failed with a database error, so it kept retrying. One sample contained 10,000 consecutive Tracker messages in 4.7 seconds.
With Codex, I measured log growth at roughly 39 MiB per minute. Deleting 1 GiB bought me about 27 minutes.
That explained the disappearing space, and the package history helped explain the timing:
grep ‘upgrade libsqlite3–0’ /var/log/dpkg.log
dpkg-query -W libsqlite3–0 libtracker-sparql-3.0–0 tracker-miner-fsgrep ‘upgrade libsqlite3–0’ /var/log/dpkg.log
dpkg-query -W libsqlite3–0 libtracker-sparql-3.0–0 tracker-miner-fsSQLite had been upgraded on November 7, from 3.45.1–1ubuntu2.8 to 3.45.1–1ubuntu2.9. The first retained ROWID error appeared that night.
An Ubuntu bug report described the same versions and endless retries. GNOME had also documented the Tracker/SQLite compatibility issue. The evidence strongly pointed to a package regression.
My available package lists still showed affected versions. I chose a reversible workaround: disable the faulty indexer.
systemctl — user mask — now tracker-miner-fs-3.service
systemctl — user show tracker-miner-fs-3.service -p ActiveState -p UnitFileStatesystemctl — user mask — now tracker-miner-fs-3.service
systemctl — user show tracker-miner-fs-3.service -p ActiveState -p UnitFileStateThe service reported inactive and masked, preventing it from restarting through systemd.
I checked the log again: about 2 KiB in 98 seconds.
The flood had stopped. Now cleanup could actually last.
After confirming both oversized logs contained the same errors, I saved diagnostic samples and cleared them. These commands reproduce that step:
(
set -e
backup=$(mktemp -d)
sudo tail -n 2000 /var/log/syslog > “$backup/syslog.tail”
sudo tail -n 2000 /var/log/syslog.1 > “$backup/syslog.1.tail”
# Permanently clears these logs; confirm the same issue first.
sudo truncate -s 0 /var/log/syslog /var/log/syslog.1
)(
set -e
backup=$(mktemp -d)
sudo tail -n 2000 /var/log/syslog > “$backup/syslog.tail”
sudo tail -n 2000 /var/log/syslog.1 > “$backup/syslog.1.tail”
# Permanently clears these logs; confirm the same issue first.
sudo truncate -s 0 /var/log/syslog /var/log/syslog.1
)I then reduced archived journals and cleared downloaded package caches:
sudo journalctl — rotate
sudo journalctl — vacuum-size=1G
sudo apt-get cleansudo journalctl — rotate
sudo journalctl — vacuum-size=1G
sudo apt-get cleanThis removes older diagnostic history and cached downloads. It doesn't uninstall applications or establish a permanent journal limit.
The final disk check showed:
About 40 GiB recovered. The package incompatibility still needs a compatible update. Until then, Tracker-backed indexed file search stays disabled. I verified the persistent mask, but didn't test a reboot.
Seeing the error loop stop gave me a reason to expect that space to last.