No space left on device

[Franz]

whonix was not working so tried to reinstall it for 3.2Qubes with this command

$ sudo qubes-dom0-update --enablerepo=qubes-templates-community --action=reinstall qubes-template-whonix-ws

However while it worked for whonix-gw I am getting the following error for whonix-ws after the long download:

 qfile-agent: Fatal error: File copy: No space left on device; Last file: qubes-template-whonix-ws-3.0.6-201608050146.noarch.rpm (error type: No space left on device)
'/usr/lib/qubes/qrexec-client-vm dom0 qubes.ReceiveUpdates /usr/lib/qubes/qfile-agent /var/lib/qubes/dom0-updates/packages/*.rpm' failed with exit code 1!

No space left on device? Running df -h on dom0 the most used item is:

/dev/dm-1  82%, used 189G available 43G which should be more than enough for a less than 700MB download

So where should I look for?

Best

Fran

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Template (and generally packages) is downloaded to
/var/lib/qubes/updates in dom0. Maybe you have something smaller mounted
there? You may want to try --clean option, to clean cache first.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJZ362XAAoJENuP0xzK19csSFoH/2+mrNpp/Wkq6YprpNvPZVD2
sRmkDaVqCgFDET+ZvoUQV96W3oojZIsBm7l6jT8HLKHuVu2lwQ/KaRyF9ITMU0zt
17uzZTYzIA0Mhh16A3G4xAsX/y/VZw3jU9RWi0hfVIX6BR1da75M8Ey8g7wqAJ12
dflzBdehM4jnBC1X0HTC+EUKuPJ9xSvkbtYXjwGUTMFyOzxZv9cKjSM+br1SuCej
893a3EnMUS0OKkFqg8EhzTy5vh1PrMpL7gjmTX+6H10UyrRNc0RUhsANLwb479T6
Ghct221AoauP5MdvCti3C9I6PO50kKFdISGXtNeXcblQCq7+a8sQBigqqpkEaY8=
=4RQ9
-----END PGP SIGNATURE-----

[Franz]

On Oct 13, 2017 19:32, "Marek Marczykowski-Górecki" <marm...@invisiblethingslab.com> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, Oct 13, 2017 at 06:27:31PM -0300, Franz wrote:
> whonix was not working so tried to reinstall it for 3.2Qubes with this
> command
>
> $ sudo qubes-dom0-update --enablerepo=qubes-templates-community
> --action=reinstall qubes-template-whonix-ws
>
> However while it worked for whonix-gw I am getting the following error
> for whonix-ws after the long download:
>
>  qfile-agent: Fatal error: File copy: No space left on device; Last
> file: qubes-template-whonix-ws-3.0.6-201608050146.noarch.rpm (error
> type: No space left on device)
> '/usr/lib/qubes/qrexec-client-vm dom0 qubes.ReceiveUpdates
> /usr/lib/qubes/qfile-agent /var/lib/qubes/dom0-updates/packages/*.rpm'
> failed with exit code 1!
>
>
> No space left on device? Running df -h on dom0 the most used item is:
>
> /dev/dm-1  82%, used 189G available 43G which should be more than
> enough for a less than 700MB download
>
> So where should I look for?

Template (and generally packages) is downloaded to
/var/lib/qubes/updates in dom0. Maybe you have something smaller mounted
there? 

There I found only the following: /var/lib/qubes/updates/rpm/qubes-template-whonix-ws-3.0.6-201...noarch.rpm

Doing 

du -h 

There gives 191M which is very smaller than the 43G I expected.

But the fact that some space is still available suggests that the template was fully downloaded and I do not have to download it again. Correct?

You

may want to try --clean option, to clean cache first.

It seems --clean is an option for a command. Which command?

Many thanks

[Franz]

On Oct 13, 2017 20:56, "Franz" <169...@gmail.com> wrote:

I understood, it is the same update command. But running it, it replies 0 files removed. So it may not help.

Is there a easy way to increase space?

[Franz]

I updated the template again using the --clean option, but I get the same "no space left" error.

But the situation is even worse. Now df -h shows that even the last 43G disappeared from /dev/dm-1. So zero available space left.

Hope there is a solution

Best

Fran

[Franz]

I removed some templates and everything worked again. It seems there is only a limited space allocated to templates and when this space fills up,  then it messes with the general space available in the system at /dev/dm-1 eating up all available space.