Critical space on sda3 - Growing fast

In the morning I could not turn on my computer because sda3 was 100% full.
To solve the problem soon, I erased the oldest snapshots in order to have room to be able to connect my computer in graphics mode.
After making the cleaning of snapshots, my sda3 got 80% used. 40 minutes after sda3 was already 85% used.
What is growing so fast? Logs? Temporary files? How do I filter it to delete unnecessary files?
Increase partition / to 100gb will improve in my case?

df -h command follows:

df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        7.8G     0  7.8G   0% /dev
tmpfs           7.8G  5.3M  7.8G   1% /dev/shm
tmpfs           7.8G  2.2M  7.8G   1% /run
tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
/dev/sda3        21G   16G  3.0G  84% /
/dev/sda3        21G   16G  3.0G  84% /.snapshots
/dev/sda3        21G   16G  3.0G  84% /srv
/dev/sda3        21G   16G  3.0G  84% /usr/local
/dev/sda3        21G   16G  3.0G  84% /tmp
/dev/sda3        21G   16G  3.0G  84% /var/tmp
/dev/sda3        21G   16G  3.0G  84% /var/spool
/dev/sda1       156M  4.6M  152M   3% /boot/efi
/dev/sda3        21G   16G  3.0G  84% /opt
/dev/sda3        21G   16G  3.0G  84% /boot/grub2/x86_64-efi
/dev/sda3        21G   16G  3.0G  84% /var/opt
/dev/sda3        21G   16G  3.0G  84% /var/log
/dev/sda3        21G   16G  3.0G  84% /var/crash
/dev/sda3        21G   16G  3.0G  84% /var/lib/pgsql
/dev/sda3        21G   16G  3.0G  84% /var/lib/named
/dev/sda3        21G   16G  3.0G  84% /var/lib/mailman
/dev/sda3        21G   16G  3.0G  84% /var/lib/mysql
/dev/sda3        21G   16G  3.0G  84% /var/lib/mariadb
/dev/sda3        21G   16G  3.0G  84% /var/lib/libvirt/images
/dev/sda3        21G   16G  3.0G  84% /boot/grub2/i386-pc
/dev/sda4       895G  170G  725G  19% /home

Update:
After removing the snapshots I restarted the computer and I can not start some vms in virtualbox.
I tried to reinstall virtualbox and when I tried to install now, I received the following error.
I tried to install other packages to test and I’m with this error for any installation on the opensuse. What might be happening?
Below the error when I tried to install some package:

Subprocess failed. Error: RPM failed: error: rpmdb: Packages page 20635 is on free list with type 7error: rpmdb: PANIC: Invalid argument
error: db4 error(-30974) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) adding header #3675 record
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->c_close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: virtualbox-guest-kmp-default-5.0.10_k4.1.12_1-10.1.x86_64: install failed
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: rpmdb: File handles still open at environment close
error: rpmdb: Open file handle: /var/lib/rpm/Packages
error: rpmdb: Open file handle: /var/lib/rpm/Name
error: rpmdb: Open file handle: /var/lib/rpm/Basenames
error: rpmdb: Open file handle: /var/lib/rpm/Group
error: rpmdb: Open file handle: /var/lib/rpm/Requirename
error: rpmdb: Open file handle: /var/lib/rpm/Providename
error: rpmdb: Open file handle: /var/lib/rpm/Conflictname
error: rpmdb: Open file handle: /var/lib/rpm/Obsoletename
error: rpmdb: Open file handle: /var/lib/rpm/Triggername
error: rpmdb: Open file handle: /var/lib/rpm/Dirnames
error: rpmdb: Open file handle: /var/lib/rpm/Installtid
error: rpmdb: Open file handle: /var/lib/rpm/Sigmd5
error: rpmdb: Open file handle: /var/lib/rpm/Sha1header
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery

df does not really work for btrfs partitions. Use the “btrfs” command instead, e.g.:

btrfs filesystem df /

And 21GB is a liitle small IMHO. I recommend 40GB.

To repair your damaged rpm database:

rpm --rebuilddb

Hendrik

The problem with rpm was solved ran:

rpm --rebuilddb

Hi
Edit the /etc/snapper/configs/root file to reduce the number of snapshots, then manually run the snapper cleanup and then btrfs maintenance job a couple of times;


/etc/cron.daily/suse.de-snapper
/etc/cron.weekly/btrfs-balance.sh

The df command whilst an indicator, btrfs uses some different tools;


btrfs filesystem show /
btrfs fi df /
btrfs fi usage /

There is further information here;
https://www.suse.com/documentation/sles11/stor_admin/data/trbl_btrfs_volfull.html
https://btrfs.wiki.kernel.org/index.php/Problem_FAQ

I run the commands you asked, but my machine is still 95% of space in sda3.
Already I deleted all snapshots and still I’m out of space.
How can what is ‘eating up’ my space.

On Thu 11 Feb 2016 11:56:01 AM CST, rafaelfrazao wrote:

malcolmlewis;2751578 Wrote:
> Hi
> Edit the /etc/snapper/configs/root file to reduce the number of
> snapshots, then manually run the snapper cleanup and then btrfs
> maintenance job a couple of times;
> >
Code:

> >
> /etc/cron.daily/suse.de-snapper
> /etc/cron.weekly/btrfs-balance.sh
>

> >
> The df command whilst an indicator, btrfs uses some different tools;
> >
Code:

> >
> btrfs filesystem show /
> btrfs fi df /
> btrfs fi usage /
> >
Code:

> >
> There is further information here;
>
SUSE Documentation
> Problem FAQ - btrfs Wiki > > >
>
> I run the commands you asked, but my machine is still 95% of space
in sda3. > Already I deleted all snapshots and still I’m out of space.
> How can what is ‘eating up’ my space.

Hi
So what does the following command show?


btrfs fi usage /


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.51-60.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

On Thu 11 Feb 2016 11:56:01 AM CST, rafaelfrazao wrote:

malcolmlewis;2751578 Wrote:
> Hi
> Edit the /etc/snapper/configs/root file to reduce the number of
> snapshots, then manually run the snapper cleanup and then btrfs
> maintenance job a couple of times;
> >
Code:

> >
> /etc/cron.daily/suse.de-snapper
> /etc/cron.weekly/btrfs-balance.sh
>

> >
> The df command whilst an indicator, btrfs uses some different tools;
> >
Code:

> >
> btrfs filesystem show /
> btrfs fi df /
> btrfs fi usage /
> >
Code:

> >
> There is further information here;
>
SUSE Documentation
> Problem FAQ - btrfs Wiki > > >
>
> I run the commands you asked, but my machine is still 95% of space
in sda3. > Already I deleted all snapshots and still I’m out of space.
> How can what is ‘eating up’ my space.

Hi
So what does the following command show?


btrfs fi usage /


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.51-60.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!