I saw that. But the disk is far from full. Don't know what's up with
the /snap loopback devices. The hard drive itself is at 35%. Here's
the df output:
On 03/25/2018 10:59 PM, Daniel van Vugt wrote:
> Your log is showing "No space left on device"
>
> So one of your disks is full, which may be the problem. Please check by
> running:
>
> df -h
>
--
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039
I saw that. But the disk is far from full. Don't know what's up with
the /snap loopback devices. The hard drive itself is at 35%. Here's
the df output:
Filesystem Size Used Avail Use% Mounted on .Private 450G 148G 279G 35% /home/weinberg
udev 3.8G 0 3.8G 0% /dev
tmpfs 767M 1.9M 765M 1% /run
/dev/sda5 450G 148G 279G 35% /
tmpfs 3.8G 4.0K 3.8G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/loop1 163M 163M 0 100% /snap/spotify/6
/dev/loop0 82M 82M 0 100% /snap/core/4206
tmpfs 767M 16K 767M 1% /run/user/120
tmpfs 767M 36K 767M 1% /run/user/1000
/home/weinberg/
On 03/25/2018 10:59 PM, Daniel van Vugt wrote:
> Your log is showing "No space left on device"
>
> So one of your disks is full, which may be the problem. Please check by
> running:
>
> df -h
>
--
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039