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

Qubes disk free space not available #3907

Closed
leonardo-dc opened this Issue May 18, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@leonardo-dc

Qubes OS version:

R4.0

Affected component(s):

dom0 (qubes_dom0/pool00)


Steps to reproduce the behavior:

Free disk space does not increase/available (after files removal).

Expected behavior:

I must be able to use the free disk space again after deleting my files.

Actual behavior:

I just remove about 100GB of files from the Dom0.

But even after that, for example, in one of my VM I continue have a problem with an early filling of free space:

user@host:~$ df -h | egrep "/rw|Used"
Filesystem          Size  Used Avail Use% Mounted on
/dev/xvdb           260G  228G   33G  88% /rw


user@host:~$ sudo fallocate -l 9G /test
fallocate: fallocate failed: No space left on device


user@host:~$ sudo du -sh /test
6.7G	/test


user@host:~$ df -h | egrep "/rw|Used"
Filesystem          Size  Used Avail Use% Mounted on
/dev/xvdb           260G  228G   33G  88% /rw

These values are constant (free space decreases but does not increase [after removal files or VMs]):

user@dom0 ~ % sudo lvs qubes_dom0/pool00                  
  LV     VG         Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  pool00 qubes_dom0 twi-aotz-- 453.17g             91.85  41.55                           

General notes:

I have about 282GB date on my 453GB pool00 and the strange No space left on device error.

I ran a disk check with sudo fsck -f /dev/mapper/qubes_dom0-vm--my--vm--private
And also ran sudo pvck -v /dev/mapper/luks-efirowmc-ei3o-9381-9d93-d8209d0j3ice

Any help is appreciated. How-to free disk space for use?


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 18, 2018

Member

/test is not in /rw, so the above test isn't accurate.
Anyway, make sure you have 'discardoption enabled for/in dom0 and template(s) (/etc/fstab). It should be there for fresh 4.0 install, but if you've update from earlier release candidates it might be missing. Alternatively runfstrim` manually after removing files.

Member

marmarek commented May 18, 2018

/test is not in /rw, so the above test isn't accurate.
Anyway, make sure you have 'discardoption enabled for/in dom0 and template(s) (/etc/fstab). It should be there for fresh 4.0 install, but if you've update from earlier release candidates it might be missing. Alternatively runfstrim` manually after removing files.

@leonardo-dc

This comment has been minimized.

Show comment
Hide comment
@leonardo-dc

leonardo-dc May 19, 2018

You are right. The fstrim at dom0 helps me. Thank you!

user@dom0 ~ % sudo lvs qubes_dom0/pool00                  
  LV     VG         Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  pool00 qubes_dom0 twi-aotz-- 453.17g             66.43  31.15                           

You are right. The fstrim at dom0 helps me. Thank you!

user@dom0 ~ % sudo lvs qubes_dom0/pool00                  
  LV     VG         Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  pool00 qubes_dom0 twi-aotz-- 453.17g             66.43  31.15                           
@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 19, 2018

Member

Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.

Member

andrewdavidwong commented May 19, 2018

Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.

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