Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk quota exceeded when just doing a 80MB apt-get upgrade #62

Open
akarasulu opened this issue Sep 18, 2017 · 4 comments
Open

Disk quota exceeded when just doing a 80MB apt-get upgrade #62

akarasulu opened this issue Sep 18, 2017 · 4 comments
Assignees
Milestone

Comments

@akarasulu
Copy link
Contributor

This cannot be true even for the tiny container size:

Unpacking vim-tiny (2:7.4.052-1ubuntu3.1) over (2:7.4.052-1ubuntu3) ...
dpkg: unrecoverable fatal error, aborting:
 unable to install updated status of `vim-tiny': Disk quota exceeded
E: Sub-process /usr/bin/dpkg returned an error code (2)
E: Failed to write temporary StateFile /var/lib/apt/extended_states.tmp
root@Container4:~# df -h
Filesystem                Size  Used Avail Use% Mounted on
/dev/mapper/ubuntu-btrfs  100G  2.3G   97G   3% /
none                      492K  4.0K  488K   1% /dev
/dev/mapper/ubuntu-btrfs  100G  2.3G   97G   3% /home
/dev/mapper/ubuntu-btrfs  100G  2.3G   97G   3% /opt
/dev/mapper/ubuntu-btrfs  100G  2.3G   97G   3% /var
udev                      5.7G     0  5.7G   0% /dev/tty
none                      1.2G  288K  1.2G   1% /run
none                      4.0K     0  4.0K   0% /sys/fs/cgroup
none                      5.0M     0  5.0M   0% /run/lock
none                      5.8G     0  5.8G   0% /run/shm
none                      100M     0  100M   0% /run/user
root@Container4:~#
@soffokl
Copy link
Contributor

soffokl commented Oct 2, 2017

Tested it with a tiny container, and apt-get upgrade successfully finished for me without any complaint about disk quota.
@akarasulu do you remember what was the template for your container? Or maybe any steps to reproduce this behavior?

@absidish
Copy link

We still facing it.
steps to reproduce:

  1. create container with HUGE type
  2. ssh into container
  3. generate random file by 10GB

Result:
first time I generated 150GB which is over than 100GB
second time I generated 20GB file it start giving error Disk quota exceeded but there were 80 GB free space according to quota rules.

@samsonbek
Copy link
Member

did you delete 150GB from that container, and then generated 20GB? @absidish

@absidish
Copy link

absidish commented Apr 11, 2018

first time I generated 150GB which is over than 100GB

this is in environment A

second time I generated 20GB file it start giving error Disk quota exceeded but there were 80 GB free

this is environment B

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants