Full Disk Warning

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »

I completed the 3 rm commands and / is now at 24% used of +-75GB. I guess that is about normal for a new installation. I haven't created or run the file yet but, will do so soon.
I still have issues with /home which is far larger than it should be. I think the problem is with the Timeshift folder which contains more than 1 million items and is 144GB in size. It is not causing any problems yet. I'll do some learning about it and post a new question if needed.

Thanks for all the help. I'll let you know if the log files cause any more issues.
pbear
Level 14
Level 14
Posts: 5206
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Full Disk Warning

Post by pbear »

YoMan wrote:
Tue May 26, 2020 1:05 pm
... 144GB in size.
According to what? Some ways of calculating space-used are fooled by hard links. Whereas your actual space used for Timeshift snapshots should be in the 10 to 20 GB range. Did you modify any of the settings?
YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning [solved]

Post by YoMan »

Just looked at properties. That appears to be mostly in one folder within Timeshift; 110GB for "snapshots" which contains 4 folders that appear to be daily snapshots. The only changes I've made is to have the snapshots saved in /home and to make weekly snapshots rather than daily. Currently, there is one "weekly" folder of 32 bytes. Any harm in deleting the dailys?
pbear
Level 14
Level 14
Posts: 5206
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Full Disk Warning [solved]

Post by pbear »

Bear in mind, your earlier du report says the /timeshift directory is modest:

Code: Select all

bill@wiliam-Yoga:~$ sudo [b]du[/b] -h / | grep -P '^[0-9\.]+G'
[sudo] password for bill:        
2.0G	/home/timeshift/snapshots/2020-05-23_10-00-01/localhost/usr/share
1.1G	/home/timeshift/snapshots/2020-05-23_10-00-01/localhost/usr/lib/x86_64-linux-gnu
2.3G	/home/timeshift/snapshots/2020-05-23_10-00-01/localhost/usr/lib
4.7G	/home/timeshift/snapshots/2020-05-23_10-00-01/localhost/usr
6.3G	/home/timeshift/snapshots/2020-05-23_10-00-01/localhost
6.4G	/home/timeshift/snapshots/2020-05-23_10-00-01
6.6G	/home/timeshift/snapshots
6.6G	/home/timeshift
So, don't do anything with the snapshots yet. Besides, the space liberated by deleting snapshots is relatively small, because the additional space consumed by each snapshot is small. That's the main point of using a snapshot backup method. Take a look this test I did, showing the difference between two snapshots and six. In a nutshell, the marginal cost of a snapshot seems to be about 250 MB, plus whatever unique packages are contained in that snapshot. Not trivial, but takes four of 'em to get a GB. Not the source of your problem, if indeed you have a problem.

Notice also this follow-up post in the same thread describing how Timeshift plays out on my system. Even my absurdly deep backup flash drive, with eight months of snapshots, comes in at 37.5 GB. So, if you actually have 144 GB in snapshots, something is wrong.

ETA: Please post a screenshot of the drive as shown in GParted. You'll have to install it, but that's easy: apt install gparted. Use Alt-PrScr to snap just the GParted window. Then the file should be small enough to upload as an attachment (tab below text entry window). If it's too large, upload to an image hosting service and link to the image location (not the download link) with [rimg] tags. This will display it in your post.
Last edited by pbear on Tue May 26, 2020 4:31 pm, edited 2 times in total.
User avatar
LanceM
Level 9
Level 9
Posts: 2843
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning [solved]

Post by LanceM »

Do you have Timeshift set to include all of Home? If so, that's a very poor idea. If you do, try setting it as the picture, that way it will exclude your data, which you can backup with something like Grsync
Ignores-Data-In-Home.jpg
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php
YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning [solved]

Post by YoMan »

I ran the command:

Code: Select all

du -h /home/timeshift/snapshots
I not exactly sure what it means but, I wanted to bring attention to the number at the beginning of the very last line. The whole run is very long. So, I have only included the last page.

Code: Select all

0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/linux-sound-base
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/cryptsetup/checks
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/cryptsetup/scripts
12K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/cryptsetup
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/x86_64-linux-gnu/device-mapper
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/x86_64-linux-gnu/security
20K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/x86_64-linux-gnu
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/hdparm
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib/security
9.5M	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/lib
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/sys
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/cdrom
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/media
4.0K	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost/tmp
47G	/home/timeshift/snapshots/2020-05-25_16-00-01/localhost
47G	/home/timeshift/snapshots/2020-05-25_16-00-01
103G	/home/timeshift/snapshots
I have added a gparted image as an attachment.

Timeshift settings were set at default for "exclude all". I have changed it to "include all" for root and "include hidden" for /home. I'm not sure what you mean by saving Timeshift as a picture.
Attachments
Selection_003.png
User avatar
LanceM
Level 9
Level 9
Posts: 2843
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning [solved]

Post by LanceM »

I meant the picture I included for an example in my post.
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php
YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning [solved]

Post by YoMan »

Oh. pbear asked for the gparted screen shot.
Attachments
Screenshot from 2020-05-26 19-46-42.png
pbear
Level 14
Level 14
Posts: 5206
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Full Disk Warning [solved]

Post by pbear »

YoMan wrote:
Tue May 26, 2020 8:50 pm
Oh. pbear asked for the gparted screen shot.
Sure did. Of the 140 GB of files in /home, how many can you account for as bona fide data files (documents, pictures, music, games, etc.)
YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning [solved]

Post by YoMan »

Here are results of running the script:

Code: Select all

bill@wiliam-Yoga:~/Documents/Computer/Scripts$ ./clean-logs.sh
find: cannot delete ‘/var/log/Xorg.0.log.old’: Permission denied
find: ‘/var/log/speech-dispatcher’: Permission denied
find: cannot delete ‘/var/log/syslog.3.gz’: Permission denied
find: cannot delete ‘/var/log/cups/access_log.2.gz’: Permission denied
find: cannot delete ‘/var/log/cups/access_log.3.gz’: Permission denied
find: cannot delete ‘/var/log/cups/error_log.2.gz’: Permission denied
find: ‘/var/log/speech-dispatcher’: Permission denied
find: cannot delete ‘/var/log/lightdm/x-0.log.2.gz’: Permission denied
find: cannot delete ‘/var/log/lightdm/lightdm.log.1.gz’: Permission denied
find: cannot delete ‘/var/log/lightdm/x-0.log.1.gz’: Permission denied
find: cannot delete ‘/var/log/lightdm/seat0-greeter.log.1.gz’: Permission denied
find: cannot delete ‘/var/log/lightdm/seat0-greeter.log.2.gz’: Permission denied
find: cannot delete ‘/var/log/lightdm/lightdm.log.2.gz’: Permission denied
find: cannot delete ‘/var/log/lightdm/lightdm.log.3.gz’: Permission denied
find: cannot delete ‘/var/log/lightdm/seat0-greeter.log.3.gz’: Permission denied
find: cannot delete ‘/var/log/lightdm/x-0.log.3.gz’: Permission denied
find: cannot delete ‘/var/log/installer/initial-status.gz’: Permission denied
find: cannot delete ‘/var/log/syslog.1’: Permission denied
find: cannot delete ‘/var/log/auth.log.1’: Permission denied
find: cannot delete ‘/var/log/cups/error_log.1’: Permission denied
find: cannot delete ‘/var/log/cups/access_log.1’: Permission denied
find: ‘/var/log/speech-dispatcher’: Permission denied
find: ‘/var/log/speech-dispatcher’: Permission denied
find: ‘/var/log/speech-dispatcher’: Permission denied
find: ‘/var/log/speech-dispatcher’: Permission denied
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@0005a66dd3f92475-04fc85b2f8b3e639.journal~'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@0005a66f419e8cfe-86f5abc778070166.journal~'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@50dd51d8acca4f0d9b68679387e43373-0000000000000001-0005a66dd3f7fba7.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021bc550-0005a66dc8437bd0.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021bea56-0005a66dc84ca965.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021c0b9a-0005a66dc8564096.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021c30a0-0005a66dc85ff1ae.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021c5333-0005a66dc8695e79.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021c73ad-0005a66dc8734e79.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021c98b3-0005a66dc87e65ee.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021cbdb9-0005a66dc8896511.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021ce0d0-0005a66dc894f3e3.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021d05d6-0005a66dc89e821c.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021d2adc-0005a66dc8a7dc04.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021d4fe2-0005a66dc8b0cf5b.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021d71c2-0005a66dc8ba6d2c.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021d96c8-0005a66dc8c37cdc.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021dbbce-0005a66dc8cc9047.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021de0d4-0005a66dc8d50b74.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021e05da-0005a66dc8de112b.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021e2a9e-0005a66dc8e7d927.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021e4fa4-0005a66dc8f1510b.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021e74aa-0005a66dc8fa827c.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021e99b0-0005a66dc9037708.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021ebeb6-0005a66dc90c6519.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021ee3bc-0005a66dc9157ee8.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021f08c2-0005a66dc91f2e95.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021f2dc8-0005a66dc9281f5d.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021f500d-0005a66dc931c9fc.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021f7513-0005a66dc93adb07.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021f9a19-0005a66dc94440aa.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021fbf1f-0005a66dc94d7bae.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000021fdea1-0005a66dc956da1d.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000022003a7-0005a66dc9605229.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002202402-0005a66dc969bf42.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002204908-0005a66dc972910d.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002206e0e-0005a66dc97b1ccd.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002209314-0005a66dc983e4db.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000220b81a-0005a66dc98d10d1.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000220dd20-0005a66dc995e18d.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002210226-0005a66dc99e8da8.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000221272c-0005a66dc9a7f681.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002214c32-0005a66dc9b1a47c.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002217138-0005a66dc9bae702.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000221963e-0005a66dc9c3b404.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000221bb44-0005a66dc9ccdc6e.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000221e04a-0005a66dc9d60d6c.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002220550-0005a66dc9df4e08.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002222a56-0005a66dc9e8ede1.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002224b49-0005a66dc9f26371.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002226d1b-0005a66dc9fbe096.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002229221-0005a66dca04bf67.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000222b363-0005a66dca0e170b.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000222d461-0005a66dca1767e0.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000222f967-0005a66dca207bbc.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002231e6d-0005a66dca2951ff.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002234373-0005a66dca326806.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002236879-0005a66dca3c210f.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002238d7f-0005a66dca44d8b7.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000223b285-0005a66dca4dc8e1.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000223d78b-0005a66dca56f61c.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000223f9cc-0005a66dca60d344.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002241ed2-0005a66dca69f679.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000022443d8-0005a66dca72e550.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000022468de-0005a66dca7bee25.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002248de4-0005a66dca856a90.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000224aec4-0005a66dca8ecdd8.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000224cfef-0005a66dca985135.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000224f4f5-0005a66dcaa1cb62.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-00000000022519fb-0005a66dcaaa998e.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002253f01-0005a66dcab450f3.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002256407-0005a66dcabd30bf.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000225890d-0005a66dcac6227a.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000225a827-0005a66dcacf72cb.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000225cd2d-0005a66dcad85820.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000225f233-0005a66dcae19cb2.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002261739-0005a66dcaeb6560.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002263c3f-0005a66dcaf47fbb.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002266145-0005a66dcafd99cc.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000226864b-0005a66dcb06616c.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000226ab51-0005a66dcb0f3fdf.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000226d057-0005a66dcb181684.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000226f1f1-0005a66dcb217ab2.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002271533-0005a66dcb2b4c68.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002273a39-0005a66dcb346365.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002275f3f-0005a66dcb3d0903.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002278445-0005a66dcb45f5ce.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000227a94b-0005a66dcb4f1b74.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000227cb31-0005a66dcb58afcb.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000227f037-0005a66dcb6288d8.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000228153d-0005a66dcb6b7373.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002283a43-0005a66dcb74cf13.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-0000000002285f49-0005a66dcb7ddb4e.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000228844f-0005a66dcb871222.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000228a955-0005a66dcb90678a.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000228ca78-0005a66dcb99f31f.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system@a6c81dc0e9a34d4e84140b33278e2989-000000000228ef7e-0005a66dcba2da11.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/system.journal'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/user-1000@0005a6701e40dc01-754a1698b4a929f6.journal~'? 
rm: remove write-protected regular file '/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a/user-1000.journal'? 
rm: remove write-protected regular file '/var/backups/alternatives.tar.1.gz'? 
rm: remove write-protected regular file '/var/backups/dpkg.arch.1.gz'? 
rm: remove write-protected regular file '/var/backups/dpkg.arch.2.gz'? 
rm: remove write-protected regular file '/var/backups/dpkg.diversions.1.gz'? 
rm: remove write-protected regular file '/var/backups/dpkg.diversions.2.gz'? 
rm: remove write-protected regular file '/var/backups/dpkg.statoverride.1.gz'? 
rm: remove write-protected regular file '/var/backups/dpkg.statoverride.2.gz'? 
rm: remove write-protected regular file '/var/backups/dpkg.status.1.gz'? 
rm: remove write-protected regular file '/var/backups/dpkg.status.2.gz'? 
pbear, All of my data files are in /home/bill. All of those were recently moved from my old system except for a bunch of hidden files that Mint has created. The latter are small. /home contains only the Timeshift folders.
pbear
Level 14
Level 14
Posts: 5206
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Full Disk Warning [solved]

Post by pbear »

YoMan wrote:
Tue May 26, 2020 10:55 pm
pbear, All of my data files are in /home/bill. All of those were recently moved from my old system except for a bunch of hidden files that Mint has created. The latter are small. /home contains only the Timeshift folders.
I don't understand this answer. Plainly, /home/bill is in /home, so those files would be part of the 140 GB used space which GParted reports.

Also, I'm puzzled that you keep getting different answers when you query for space used. When I check my system by different methods, I get same order-of-magnitude answers by four methods. By the way, from my notes, I see that you want to run the command as sudo du -hs /timeshift. The -s flag means summary, and spares you the file-by-file readout.

Anyhoo, as you can't think of anything you modified, I think you should delete all your snapshots, purge Timeshift, and reinstall it. Don't do it right away. Let's wait to see whether Lance has a better solution.
User avatar
smurphos
Level 17
Level 17
Posts: 7132
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Full Disk Warning [solved]

Post by smurphos »

The timeshift snapshots are going to be huge, because they have been snapshoting the hugely inflated log files.

Yoman - you first priority should be identifying what is spamming your logs or you'll be back to a full disc again.

Run the command below and leaving it running in a terminal - it monitors new lines being added to syslog. Are there a rapidly repeating message(s)? If so what are they?

Code: Select all

tail -f /var/log/syslog
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
pbear
Level 14
Level 14
Posts: 5206
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Full Disk Warning [solved]

Post by pbear »

smurphos wrote:
Wed May 27, 2020 12:34 am
The timeshift snapshots are going to be huge, because they have been snapshoting the hugely inflated log files.
Guess I've always assumed those were filtered. Is there a good reason for including logs in snapshots?
User avatar
smurphos
Level 17
Level 17
Posts: 7132
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Full Disk Warning [solved]

Post by smurphos »

To ensure they accurately reflect the state and history of the system post timeshift restore I guess.
/var/logs normally isn't a massive space hog - I don't clean up mine at all and this current install is about 6 months old - it's about 600MB
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
pbear
Level 14
Level 14
Posts: 5206
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Full Disk Warning [solved]

Post by pbear »

YoMan wrote:
Tue May 26, 2020 3:06 pm
Any harm in deleting the dailys?
In light of smurphos' comments, I think the time has come to delete all the snapshots, but don't bother purging and reinstalling Timeshift itself. Once you have deleted the current snapshots, open Settings, go to Filters, click Add Folder, navigate to /var/log, and select. Pretty sure that will keep logs from blowing up Timeshift again. Later, once you you've solved the log problem, this filter can be removed. Meanwhile, you'll have Timeshift active and available for its primary purpose, i.e., restoring the system if an update (or operator error) creates a problem.

Heed smurphos' advice. Runaway logs don't generally resolve themselves. You've marked the thread [solved] prematurely.
By the way, what does sudo du -hs /var/log report this morning?
User avatar
LanceM
Level 9
Level 9
Posts: 2843
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning [solved]

Post by LanceM »

I'm definitely with deleting all the snapshots. Also as for controlling log size, I use the tips in section 10. https://easylinuxtipsproject.blogspot.c ... .html#ID10 of the following link. I've done this for almost a year and it has worked very well. Once done, you can create a new snapshot. In addition to those tips, I also edit this file and modify accordingly:

Code: Select all

xed admin:/// /etc/systemd/journald.conf 

Code: Select all

SystemMaxUse=50M
SystemKeepFree=100M
Make sure to remove the # in from of each one to activate it. Save and then run

Code: Select all

sudo systemctl restart systemd-journald.service
That's my 2 cents worth.
Edit:
As far as space used, I like:

Code: Select all

sudo baobab
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php
YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning [solved]

Post by YoMan »

I don't understand this answer. Plainly, /home/bill is in /home, so those files would be part of the 140 GB used space which GParted reports.
Sorry. That was just me trying to answer your question: "how many can you account for as bonafide data files (documents, pictures, music, games, etc.)".
Also, I'm puzzled that you keep getting different answers when you query for space used. When I check my system by different methods, I get same order-of-magnitude answers by four methods. By the way, from my notes, I see that you want to run the command as sudo du -hs /timeshift. The -s flag means summary, and spares you the file-by-file readout.
I have no answer for that except to say that, when checking folder properties, I get 34GB for /home/bill, where my personal data files are located, and I get 110GB for /home/Timeshift, where Timeshift files are located. Most all of that space within Timeshift is in 4 daily snapshots. If it will do no harm, I'm not adverse to deleting all of the Timeshift folders and resetting it to put snanpshots on an external drive.

I assume that this "disk full" situation is not normal and it appears that no one can say for sure what the cause is. This is a brand new installation and, rather than having to nurse it along and futz with it until a reason/solution is found, i would not be adverse to starting over with a new re-installation. Does anyone think that this is a solution? Or, are the same issues likely to return anyway? Can I be reasonably assured that the issues are not hardware related?
YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »

Sorry. I was writing the above post as you (Lance, pbear) were posting. Here are results of sudo du -hs /var/log this morning:

Code: Select all

bill@wiliam-Yoga:~$ sudo du -hs /var/log
[sudo] password for bill:        
859M	/var/log
Thanks for the suggestions. I will certainly try to put them to use. I am not very command line adept. So, I have got some learning to do.
pbear
Level 14
Level 14
Posts: 5206
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Full Disk Warning [solved]

Post by pbear »

YoMan wrote:
Wed May 27, 2020 11:48 am
This is a brand new installation and, rather than having to nurse it along and futz with it until a reason/solution is found, i would not be adverse to starting over with a new re-installation. Does anyone think that this is a solution? Or, are the same issues likely to return anyway?
My advice would be, plan to reinstall but spend another couple days seeing whether you can figure out what went wrong. On the other hand, if you'd rather just get on with it, go ahead and reinstall now. Same issue is unlikely to return, but that's not a promise or guaranty.
User avatar
LanceM
Level 9
Level 9
Posts: 2843
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning

Post by LanceM »

I think if you do those little fixes I posted, it should resolve the low disk space issue. You can try it and see. I'd say to leave the snapshot location the same for the time beig so you know it worked.
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php
Post Reply

Return to “Installation & Boot”