Pagina 1 di 3
Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 9:48
da domes
Ciao a tutti,
non capisco da dove o come si sia presentato improvvisamente questo problema.
Il filesystem è improvvisamente pieno quando è sempre stato sotto il 40% di utilizzo.
Ho una partizione per / di 20gb e una per la /home di 100gb.
L'unica cosa che ho fatto è istallare un secondo ssd
Ho trovato attraverso baobab che nella cartella /var/log ci sono due file di grandi dimensioni
Codice: Seleziona tutto
/var/log$ ls -l
totale 6378100
-rw-r--r-- 1 root root 3851 mag 7 13:46 alternatives.log
-rw-r--r-- 1 root root 33494 apr 29 12:14 alternatives.log.1
-rw-r----- 1 root adm 12288 mag 8 08:58 apport.log
-rw-r----- 1 root adm 2391 mag 1 15:12 apport.log.1
-rw-r----- 1 root adm 1105 apr 28 14:47 apport.log.2.gz
drwxr-xr-x 2 root root 4096 mag 8 09:01 apt
-rw-r----- 1 syslog adm 212932 mag 8 09:30 auth.log
-rw-r----- 1 syslog adm 352151 mag 3 08:58 auth.log.1
-rw------- 1 root root 265850 mag 8 08:58 boot.log
-rw------- 1 root root 165647 mag 3 08:58 boot.log.1
-rw------- 1 root root 171901 apr 29 08:35 boot.log.2
-rw-r--r-- 1 root root 104003 apr 23 09:33 bootstrap.log
-rw-rw---- 1 root utmp 0 mag 3 08:58 btmp
-rw-rw---- 1 root utmp 384 apr 29 12:16 btmp.1
drwxr-xr-x 2 root root 4096 mag 3 14:02 cups
drwxr-xr-x 2 root root 4096 mag 8 08:59 dist-upgrade
-rw-r--r-- 1 root adm 72797 mag 8 09:00 dmesg
-rw-r--r-- 1 root adm 73408 mag 8 08:58 dmesg.0
-rw-r--r-- 1 root adm 19198 mag 8 08:56 dmesg.1.gz
-rw-r--r-- 1 root adm 19234 mag 8 08:28 dmesg.2.gz
-rw-r--r-- 1 root adm 19181 mag 7 20:07 dmesg.3.gz
-rw-r--r-- 1 root adm 21918 mag 7 16:44 dmesg.4.gz
-rw-r--r-- 1 root root 68439 mag 8 09:02 dpkg.log
-rw-r--r-- 1 root root 1154784 apr 30 15:05 dpkg.log.1
-rw-r--r-- 1 root root 32032 apr 28 14:28 faillog
-rw-r--r-- 1 root root 11270 apr 29 08:36 fontconfig.log
drwx--x--x 2 root gdm 4096 ott 7 2019 gdm3
-rw-r--r-- 1 root root 1222 mag 8 09:00 gpu-manager.log
drwxr-xr-x 3 root root 4096 apr 23 09:36 hp
drwxrwxr-x 2 root root 4096 apr 26 10:44 installer
drwxr-sr-x+ 3 root systemd-journal 4096 apr 26 10:48 journal
-rw-r----- 1 syslog adm 3233646349 mag 8 09:00 kern.log
-rw-r----- 1 syslog adm 4296662 mag 3 08:58 kern.log.1
-rw-rw-r-- 1 root utmp 292292 apr 28 14:28 lastlog
drwxr-xr-x 2 root root 4096 set 5 2019 openvpn
drwx------ 2 root root 4096 apr 23 09:32 private
drwx------ 2 speech-dispatcher root 4096 gen 19 19:26 speech-dispatcher
-rw-r----- 1 syslog adm 3264466300 mag 8 09:36 syslog
-rw-r----- 1 syslog adm 23921443 mag 3 08:58 syslog.1
-rw-r----- 1 syslog adm 1619626 apr 29 08:35 syslog.2.gz
-rw------- 1 root root 0 apr 23 09:33 ubuntu-advantage.log
drwxr-x--- 2 root adm 4096 mag 3 08:58 unattended-upgrades
drwxrwxrwx 2 root root 4096 apr 26 12:30 wpslog
-rw-rw-r-- 1 root utmp 93312 mag 8 09:00 wtmp
-rw-r--r-- 1 root root 76494 mag 8 09:00 Xorg.0.log
-rw-r--r-- 1 root root 75580 mag 8 09:00 Xorg.1.log
Codice: Seleziona tutto
df -h
File system Dim. Usati Dispon. Uso% Montato su
udev 2,9G 0 2,9G 0% /dev
tmpfs 586M 1,9M 584M 1% /run
/dev/sdb1 19G 18G 136M 100% /
tmpfs 2,9G 184M 2,7G 7% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 2,9G 0 2,9G 0% /sys/fs/cgroup
/dev/sdb5 92G 24G 63G 28% /home
/dev/loop1 55M 55M 0 100% /snap/core18/1705
/dev/loop2 243M 243M 0 100% /snap/gnome-3-34-1804/27
/dev/loop4 50M 50M 0 100% /snap/snap-store/433
/dev/loop0 155M 155M 0 100% /snap/chromium/1143
/dev/loop3 63M 63M 0 100% /snap/gtk-common-themes/1506
/dev/loop7 28M 28M 0 100% /snap/snapd/7264
/dev/loop5 55M 55M 0 100% /snap/core18/1754
/dev/loop6 256M 256M 0 100% /snap/gnome-3-34-1804/33
tmpfs 586M 24K 586M 1% /run/user/125
tmpfs 586M 72K 586M 1% /run/user/1000
df -i
File system Inode IUsati ILiberi IUso% Montato su
udev 742357 491 741866 1% /dev
tmpfs 749024 942 748082 1% /run
/dev/sdb1 1220608 223846 996762 19% /
tmpfs 749024 268 748756 1% /dev/shm
tmpfs 749024 5 749019 1% /run/lock
tmpfs 749024 18 749006 1% /sys/fs/cgroup
/dev/sdb5 6111232 99990 6011242 2% /home
/dev/loop1 10765 10765 0 100% /snap/core18/1705
/dev/loop2 24323 24323 0 100% /snap/gnome-3-34-1804/27
/dev/loop4 15827 15827 0 100% /snap/snap-store/433
/dev/loop0 10769 10769 0 100% /snap/chromium/1143
/dev/loop3 62342 62342 0 100% /snap/gtk-common-themes/1506
/dev/loop7 459 459 0 100% /snap/snapd/7264
/dev/loop5 10764 10764 0 100% /snap/core18/1754
/dev/loop6 24339 24339 0 100% /snap/gnome-3-34-1804/33
tmpfs 749024 63 748961 1% /run/user/125
tmpfs 749024 102 748922 1% /run/user/1000
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 10:05
da Stealth
Riavvia, da grub entra con recovery e utente root, e rimuovi quei 2 files di log. Poi il sistema riparte, ma occupati subito di scoprire cosa abbia provocato tutto quel log, altrimenti ti ritroverai nella stessa situazione.
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 10:14
da domes
Stealth ha scritto: ↑venerdì 8 maggio 2020, 10:05
Riavvia, da grub entra con recovery e utente root, e rimuovi quei 2 files di log. Poi il sistema riparte, ma occupati subito di scoprire cosa abbia provocato tutto quel log, altrimenti ti ritroverai nella stessa situazione.
Grazie, li ho eliminati. Come posso scoprirlo?
Ho trovato questa cartella di 2gb
Codice: Seleziona tutto
/var/log/journal/c394ed0c0c9041a3b379a8f474ad6184$ ls -l
totale 1941880
-rw-r-----+ 1 root systemd-journal 25165824 mag 7 16:44 system@0005a50feb1c6e83-2ce97b20c239a30c.journal~
-rw-r-----+ 1 root systemd-journal 8388608 mag 4 05:44 system@00419a2070c244e9b9a282496ce5ace4-0000000000000001-0005a4ca580dd872.journal
-rw-r-----+ 1 root systemd-journal 50331648 mag 5 19:36 system@00419a2070c244e9b9a282496ce5ace4-0000000000000a91-0005a4ca5a084b8c.journal
-rw-r-----+ 1 root systemd-journal 16777216 mag 5 21:22 system@00419a2070c244e9b9a282496ce5ace4-0000000000030c1d-0005a4ea25d64fbf.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 5 21:22 system@00419a2070c244e9b9a282496ce5ace4-000000000005059b-0005a4eb9031186a.journal
-rw-r-----+ 1 root systemd-journal 33554432 mag 6 21:25 system@00419a2070c244e9b9a282496ce5ace4-000000000005085c-0005a4eb91480e92.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 7 16:44 system@00419a2070c244e9b9a282496ce5ace4-000000000005e5b3-0005a4ffb890a708.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 7 16:44 system@00419a2070c244e9b9a282496ce5ace4-0000000000096e20-0005a50fe7984edf.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 8 08:30 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000000001-0005a50feb1a39a7.journal
-rw-r-----+ 1 root systemd-journal 125829120 mag 8 08:30 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000000acda5-0005a51d2078e2ac.journal
-rw-r-----+ 1 root systemd-journal 125829120 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000000ea21f-0005a51d222932df.journal
-rw-r-----+ 1 root systemd-journal 125829120 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000127306-0005a51d23c53877.journal
-rw-r-----+ 1 root systemd-journal 41943040 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000164e17-0005a51d257ad00e.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001792dd-0005a51d26116e21.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000017b7e3-0005a51d262848fb.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000017dce9-0005a51d263eca32.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001801ef-0005a51d26546030.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001826f5-0005a51d266a14c7.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000184bfb-0005a51d267ee9f9.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000187101-0005a51d26a3d6bf.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000189607-0005a51d26c44fd4.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000018bb0d-0005a51d26e9d9ff.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000018e013-0005a51d27128bfa.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000190519-0005a51d27279417.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000192a1f-0005a51d273c999a.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000194f25-0005a51d275223d6.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000019742b-0005a51d27676c36.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000199931-0005a51d277be583.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000019be37-0005a51d279078d1.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000019e33d-0005a51d27a6306d.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a0843-0005a51d27bdeb3b.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a2d49-0005a51d27eda5a9.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a524f-0005a51d2818cf5c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a7755-0005a51d2848b25f.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a9c5b-0005a51d28632ae6.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ac161-0005a51d2875922b.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ae667-0005a51d28873a65.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b0b6d-0005a51d28990bce.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b3073-0005a51d28a7e3ef.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b5579-0005a51d28bacb79.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b7a7f-0005a51d28cdef6b.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b9f85-0005a51d28e19521.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001bc48b-0005a51d28f45b45.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001be991-0005a51d29075139.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001c0e97-0005a51d29194a80.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001c339d-0005a51d292bdcdf.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001c58a3-0005a51d293d95c4.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001c7da9-0005a51d295003ec.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ca2af-0005a51d2962d2e8.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001cc7b5-0005a51d29751e67.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001cecbb-0005a51d2986a21c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001d11c1-0005a51d299cca84.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001d36c7-0005a51d29b1b3cf.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001d5bc7-0005a51d29c84c3c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001d80cd-0005a51d29de350c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001da5d3-0005a51d29f3e31f.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001dcad9-0005a51d2a0919f4.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001defdf-0005a51d2a1fdf24.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001e14e5-0005a51d2a346c13.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001e39eb-0005a51d2a49e1b4.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001e5ef1-0005a51d2a5eab88.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001e83f7-0005a51d2a7409c7.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ea8fd-0005a51d2a885dd6.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ece03-0005a51d2a9ca68a.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ef309-0005a51d2ab2471f.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001f180f-0005a51d2ac80b91.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001f3d15-0005a51d2adb6beb.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001f621b-0005a51d2aef8066.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001f8721-0005a51d2b059b00.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001fac27-0005a51d2b1a6388.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001fd12d-0005a51d2b2f5661.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ff633-0005a51d2b447ef5.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000201b39-0005a51d2b5b0d12.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000020403f-0005a51d2b6fe644.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000206545-0005a51d2b83ea11.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000208a4b-0005a51d2baa70aa.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000020af51-0005a51d2bce4efd.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000020d457-0005a51d2bf44bee.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000020f95d-0005a51d2c183b69.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000211e63-0005a51d2c2e251c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000214369-0005a51d2c440d57.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000021686f-0005a51d2c5b4291.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000218d75-0005a51d2c6fc532.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000021b27b-0005a51d2c849b4a.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000021d781-0005a51d2c99e075.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:56 system@e331ac72c56243778849fc8b3bbf1bbf-0000000000000001-0005a51d7ee44967.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:59 system@e331ac72c56243778849fc8b3bbf1bbf-00000000000010da-0005a51d80c6fb47.journal
-rw-r-----+ 1 root systemd-journal 25165824 mag 8 10:11 system.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 4 05:44 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-0000000000000690-0005a4ca58cd41f2.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 5 19:36 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-0000000000000a94-0005a4ca5a1802e3.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 5 21:22 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-000000000002e950-0005a4ea16bb013d.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 5 21:22 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-0000000000050572-0005a4eb90301e97.journal
-rw-r-----+ 1 root systemd-journal 25165824 mag 6 21:25 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-000000000005085d-0005a4eb914b0204.journal
-rw-r-----+ 1 root systemd-journal 25165824 mag 7 16:43 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-000000000005e5b5-0005a4ffb89bcd86.journal
-rw-r-----+ 1 root systemd-journal 25165824 mag 8 08:30 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-000000000006ca9e-0005a50febcae204.journal
-rw-r-----+ 1 root systemd-journal 16777216 mag 8 10:11 user-1000.journal
posso eliminarla?
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 10:22
da domes
Cosa sono tutti quei loop?
Codice: Seleziona tutto
df
File system 1K-blocchi Usati Disponib. Uso% Montato su
udev 2969428 0 2969428 0% /dev
tmpfs 599220 1736 597484 1% /run
/dev/sdb1 19091704 11631376 6467480 65% /
tmpfs 2996096 166132 2829964 6% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 2996096 0 2996096 0% /sys/fs/cgroup
/dev/loop0 56320 56320 0 100% /snap/core18/1705
/dev/loop1 158080 158080 0 100% /snap/chromium/1143
/dev/loop2 248320 248320 0 100% /snap/gnome-3-34-1804/27
/dev/loop6 56320 56320 0 100% /snap/core18/1754
/dev/loop3 261760 261760 0 100% /snap/gnome-3-34-1804/33
/dev/loop5 63616 63616 0 100% /snap/gtk-common-themes/1506
/dev/loop4 51072 51072 0 100% /snap/snap-store/433
/dev/loop7 27776 27776 0 100% /snap/snapd/7264
/dev/sdb5 95629732 24953392 65775528 28% /home
tmpfs 599216 36 599180 1% /run/user/1000
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 10:25
da giulux
Sono applicazioni snap di cui - IMHO - faresti bene a liberarti sostituendole con la versione deb, anche per recuperare un po' di spazio.
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 10:32
da frapox
domes ha scritto: ↑venerdì 8 maggio 2020, 10:14
Stealth ha scritto: ↑venerdì 8 maggio 2020, 10:05
Riavvia, da grub entra con recovery e utente root, e rimuovi quei 2 files di log. Poi il sistema riparte, ma occupati subito di scoprire cosa abbia provocato tutto quel log, altrimenti ti ritroverai nella stessa situazione.
Grazie, li ho eliminati. Come posso scoprirlo?
Chiaramente avresti fatto meglio a ispezionare
/var/log/syslog e
/var/log/kern.log prima di cancellarli...
Ispeziona il journal (che è la stessa cosa del log, solo più potente) e verifica eventuali messaggi ripetuti con
puoi filtrare i messaggi per visualizzare solo errori o peggio:
domes ha scritto: ↑venerdì 8 maggio 2020, 10:14
Ho trovato questa cartella di 2gb
Codice: Seleziona tutto
/var/log/journal/c394ed0c0c9041a3b379a8f474ad6184$ ls -l
totale 1941880
-rw-r-----+ 1 root systemd-journal 25165824 mag 7 16:44 system@0005a50feb1c6e83-2ce97b20c239a30c.journal~
-rw-r-----+ 1 root systemd-journal 8388608 mag 4 05:44 system@00419a2070c244e9b9a282496ce5ace4-0000000000000001-0005a4ca580dd872.journal
-rw-r-----+ 1 root systemd-journal 50331648 mag 5 19:36 system@00419a2070c244e9b9a282496ce5ace4-0000000000000a91-0005a4ca5a084b8c.journal
-rw-r-----+ 1 root systemd-journal 16777216 mag 5 21:22 system@00419a2070c244e9b9a282496ce5ace4-0000000000030c1d-0005a4ea25d64fbf.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 5 21:22 system@00419a2070c244e9b9a282496ce5ace4-000000000005059b-0005a4eb9031186a.journal
-rw-r-----+ 1 root systemd-journal 33554432 mag 6 21:25 system@00419a2070c244e9b9a282496ce5ace4-000000000005085c-0005a4eb91480e92.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 7 16:44 system@00419a2070c244e9b9a282496ce5ace4-000000000005e5b3-0005a4ffb890a708.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 7 16:44 system@00419a2070c244e9b9a282496ce5ace4-0000000000096e20-0005a50fe7984edf.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 8 08:30 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000000001-0005a50feb1a39a7.journal
-rw-r-----+ 1 root systemd-journal 125829120 mag 8 08:30 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000000acda5-0005a51d2078e2ac.journal
-rw-r-----+ 1 root systemd-journal 125829120 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000000ea21f-0005a51d222932df.journal
-rw-r-----+ 1 root systemd-journal 125829120 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000127306-0005a51d23c53877.journal
-rw-r-----+ 1 root systemd-journal 41943040 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000164e17-0005a51d257ad00e.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001792dd-0005a51d26116e21.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000017b7e3-0005a51d262848fb.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000017dce9-0005a51d263eca32.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001801ef-0005a51d26546030.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001826f5-0005a51d266a14c7.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000184bfb-0005a51d267ee9f9.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000187101-0005a51d26a3d6bf.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000189607-0005a51d26c44fd4.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000018bb0d-0005a51d26e9d9ff.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000018e013-0005a51d27128bfa.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000190519-0005a51d27279417.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000192a1f-0005a51d273c999a.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:31 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000194f25-0005a51d275223d6.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000019742b-0005a51d27676c36.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000199931-0005a51d277be583.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000019be37-0005a51d279078d1.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000019e33d-0005a51d27a6306d.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a0843-0005a51d27bdeb3b.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a2d49-0005a51d27eda5a9.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a524f-0005a51d2818cf5c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a7755-0005a51d2848b25f.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001a9c5b-0005a51d28632ae6.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ac161-0005a51d2875922b.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ae667-0005a51d28873a65.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b0b6d-0005a51d28990bce.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b3073-0005a51d28a7e3ef.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b5579-0005a51d28bacb79.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b7a7f-0005a51d28cdef6b.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001b9f85-0005a51d28e19521.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001bc48b-0005a51d28f45b45.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001be991-0005a51d29075139.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001c0e97-0005a51d29194a80.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001c339d-0005a51d292bdcdf.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001c58a3-0005a51d293d95c4.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001c7da9-0005a51d295003ec.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ca2af-0005a51d2962d2e8.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001cc7b5-0005a51d29751e67.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001cecbb-0005a51d2986a21c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001d11c1-0005a51d299cca84.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001d36c7-0005a51d29b1b3cf.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001d5bc7-0005a51d29c84c3c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001d80cd-0005a51d29de350c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001da5d3-0005a51d29f3e31f.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001dcad9-0005a51d2a0919f4.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001defdf-0005a51d2a1fdf24.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001e14e5-0005a51d2a346c13.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001e39eb-0005a51d2a49e1b4.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001e5ef1-0005a51d2a5eab88.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001e83f7-0005a51d2a7409c7.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ea8fd-0005a51d2a885dd6.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ece03-0005a51d2a9ca68a.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ef309-0005a51d2ab2471f.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001f180f-0005a51d2ac80b91.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001f3d15-0005a51d2adb6beb.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:32 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001f621b-0005a51d2aef8066.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001f8721-0005a51d2b059b00.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001fac27-0005a51d2b1a6388.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001fd12d-0005a51d2b2f5661.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-00000000001ff633-0005a51d2b447ef5.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000201b39-0005a51d2b5b0d12.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000020403f-0005a51d2b6fe644.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000206545-0005a51d2b83ea11.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000208a4b-0005a51d2baa70aa.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000020af51-0005a51d2bce4efd.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000020d457-0005a51d2bf44bee.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000020f95d-0005a51d2c183b69.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000211e63-0005a51d2c2e251c.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000214369-0005a51d2c440d57.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000021686f-0005a51d2c5b4291.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-0000000000218d75-0005a51d2c6fc532.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000021b27b-0005a51d2c849b4a.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:33 system@50f7b5b04a2d474a84c4b49ac0ccd33f-000000000021d781-0005a51d2c99e075.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:56 system@e331ac72c56243778849fc8b3bbf1bbf-0000000000000001-0005a51d7ee44967.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 8 08:59 system@e331ac72c56243778849fc8b3bbf1bbf-00000000000010da-0005a51d80c6fb47.journal
-rw-r-----+ 1 root systemd-journal 25165824 mag 8 10:11 system.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 4 05:44 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-0000000000000690-0005a4ca58cd41f2.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 5 19:36 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-0000000000000a94-0005a4ca5a1802e3.journal
-rw-r-----+ 1 root systemd-journal 134217728 mag 5 21:22 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-000000000002e950-0005a4ea16bb013d.journal
-rw-r-----+ 1 root systemd-journal 8388608 mag 5 21:22 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-0000000000050572-0005a4eb90301e97.journal
-rw-r-----+ 1 root systemd-journal 25165824 mag 6 21:25 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-000000000005085d-0005a4eb914b0204.journal
-rw-r-----+ 1 root systemd-journal 25165824 mag 7 16:43 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-000000000005e5b5-0005a4ffb89bcd86.journal
-rw-r-----+ 1 root systemd-journal 25165824 mag 8 08:30 user-1000@dd19d9797fd34b3bba421ddc9fa106f5-000000000006ca9e-0005a50febcae204.journal
-rw-r-----+ 1 root systemd-journal 16777216 mag 8 10:11 user-1000.journal
posso eliminarla?
È la cartella del journal. Dopo averlo esaminato puoi eliminare i file in essa contenuti. In realtà questo lo puoi applicare a tutto il contenuto della cartella
/var/log, in quanto non è vitale per il sistema.
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 11:29
da Stealth
frapox ha scritto: ↑venerdì 8 maggio 2020, 10:32
Chiaramente avresti fatto meglio a ispezionare
/var/log/syslog e
/var/log/kern.log prima di cancellarli...
Chiaramente hai ragione, e temo che la cronologia delle mie istruzioni non fosse esattamente esatta
Per fortuna niente è perduto, basta aspettare che il sistema ricominci a spammare in /var/log per individuare il responsabile
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 14:19
da domes
Stealth ha scritto: ↑venerdì 8 maggio 2020, 11:29
frapox ha scritto: ↑venerdì 8 maggio 2020, 10:32
Chiaramente avresti fatto meglio a ispezionare
/var/log/syslog e
/var/log/kern.log prima di cancellarli...
Chiaramente hai ragione, e temo che la cronologia delle mie istruzioni non fosse esattamente esatta
Per fortuna niente è perduto, basta aspettare che il sistema ricominci a spammare in /var/log per individuare il responsabile
Infatti è successo di nuovo, non sono riuscito a vedere cosa era successo ed ho dovuto cancellare i file .log da recovery
Codice: Seleziona tutto
journalctl -p 3
-- Logs begin at Fri 2020-05-08 10:49:47 CEST, end at Fri 2020-05-08 14:06:58 C>
mag 08 10:50:03 danieledell-Inspiron-N5110 wpa_supplicant[891]: dbus: wpa_dbus_>
-- Reboot --
mag 08 10:50:24 danieledell-Inspiron-N5110 gdm-password][1427]: gkr-pam: unable>
mag 08 10:57:51 danieledell-Inspiron-N5110 systemd[1434]: Failed to start Appli>
mag 08 11:13:06 danieledell-Inspiron-N5110 systemd[1434]: Failed to start Appli>
mag 08 11:49:16 danieledell-Inspiron-N5110 wpa_supplicant[853]: dbus: wpa_dbus_>
mag 08 11:49:16 danieledell-Inspiron-N5110 kernel: Bluetooth: hci0: unexpected >
mag 08 11:49:20 danieledell-Inspiron-N5110 wpa_supplicant[853]: dbus: wpa_dbus_>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: r>
lines 1-23...skipping...
-- Logs begin at Fri 2020-05-08 10:49:47 CEST, end at Fri 2020-05-08 14:06:58 CEST. --
mag 08 10:50:03 danieledell-Inspiron-N5110 wpa_supplicant[891]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/In>
-- Reboot --
mag 08 10:50:24 danieledell-Inspiron-N5110 gdm-password][1427]: gkr-pam: unable to locate daemon control file
mag 08 10:57:51 danieledell-Inspiron-N5110 systemd[1434]: Failed to start Application launched by gnome-shell.
mag 08 11:13:06 danieledell-Inspiron-N5110 systemd[1434]: Failed to start Application launched by gnome-shell.
mag 08 11:49:16 danieledell-Inspiron-N5110 wpa_supplicant[853]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/In>
mag 08 11:49:16 danieledell-Inspiron-N5110 kernel: Bluetooth: hci0: unexpected event for opcode 0x0000
mag 08 11:49:20 danieledell-Inspiron-N5110 wpa_supplicant[853]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/In>
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
mag 08 11:49:21 danieledell-Inspiron-N5110 kernel: r8169 0000:05:00.0 enp5s0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 14:39
da domes
Ho già una discussione aperta per un problema di freeze di sistema e di accumulo di ram
viewtopic.php?f=30&t=639343
Ha qualcosa a che fare con questo?
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 14:45
da frapox
Non si vede niente dall'estratto che hai incollato qui perché i messaggi sono tagliati, inoltre sono pochi... Per vederli tutti devi togliere "-p 3", e se vuoi incollarli qua ti conviene usare "--no-pager > file.txt" così che ti esporti tutti i messaggi in un file di txt. Ma ovviamente saranno migliaia di righe quindi forse ti conviene prima scorrere il log e vedere quel che si ripete... Ci saranno sicuramente messaggi ripetuti se si riempie così velocemente.
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 15:05
da domes
frapox ha scritto: ↑venerdì 8 maggio 2020, 14:45
Non si vede niente dall'estratto che hai incollato qui perché i messaggi sono tagliati, inoltre sono pochi... Per vederli tutti devi togliere "-p 3", e se vuoi incollarli qua ti conviene usare "--no-pager > file.txt" così che ti esporti tutti i messaggi in un file di txt. Ma ovviamente saranno migliaia di righe quindi forse ti conviene prima scorrere il log e vedere quel che si ripete... Ci saranno sicuramente messaggi ripetuti se si riempie così velocemente.
Codice: Seleziona tutto
journalctl
-- Logs begin at Fri 2020-05-08 10:49:47 CEST, end at Fri 2020-05-08 15:04:51 C>
mag 08 10:49:47 danieledell-Inspiron-N5110 systemd[1]: systemd-hostnamed.servic>
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_get_mapp>
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_is_visib>
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_show_int>
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_set_opac>
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_queue_dr>
mag 08 10:49:49 danieledell-Inspiron-N5110 gnome-shell[1837]: Could not create >
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_get_mapp>
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_is_visib>
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_set_opac>
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_queue_dr>
mag 08 10:49:59 danieledell-Inspiron-N5110 variety.desktop[23806]: Schema «org.>
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: vte-spawn-fd0618c6-ba>
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: gnome-terminal-server>
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: Started Application l>
mag 08 10:50:01 danieledell-Inspiron-N5110 dbus-daemon[853]: [system] Activatin>
mag 08 10:50:01 danieledell-Inspiron-N5110 systemd[1]: Starting PackageKit Daem>
mag 08 10:50:01 danieledell-Inspiron-N5110 PackageKit[23828]: daemon start
mag 08 10:50:01 danieledell-Inspiron-N5110 dbus-daemon[853]: [system] Successfu>
mag 08 10:50:01 danieledell-Inspiron-N5110 systemd[1]: Started PackageKit Daemo>
mag 08 10:50:01 danieledell-Inspiron-N5110 gnome-shell[1837]: endSessionDialog:>
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: ERROR: 2020-0>
lines 1-23...skipping...
-- Logs begin at Fri 2020-05-08 10:49:47 CEST, end at Fri 2020-05-08 15:04:51 CEST. --
mag 08 10:49:47 danieledell-Inspiron-N5110 systemd[1]: systemd-hostnamed.service: Succeeded.
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_show_internal: assertion 'GDK_IS_WINDOW (window)' failed
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:49 danieledell-Inspiron-N5110 gnome-shell[1837]: Could not create transient scope for PID 23708: GDBus.Error:org.freedesktop.DBus.Error.UnixProce>
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:59 danieledell-Inspiron-N5110 variety.desktop[23806]: Schema «org.cinnamon.desktop.background» inesistente
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: vte-spawn-fd0618c6-ba22-4332-829c-7faeee7ed579.scope: Succeeded.
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: gnome-terminal-server.service: Succeeded.
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: Started Application launched by gnome-shell.
mag 08 10:50:01 danieledell-Inspiron-N5110 dbus-daemon[853]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.servi>
mag 08 10:50:01 danieledell-Inspiron-N5110 systemd[1]: Starting PackageKit Daemon...
mag 08 10:50:01 danieledell-Inspiron-N5110 PackageKit[23828]: daemon start
mag 08 10:50:01 danieledell-Inspiron-N5110 dbus-daemon[853]: [system] Successfully activated service 'org.freedesktop.PackageKit'
mag 08 10:50:01 danieledell-Inspiron-N5110 systemd[1]: Started PackageKit Daemon.
mag 08 10:50:01 danieledell-Inspiron-N5110 gnome-shell[1837]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: ERROR: 2020-05-08 10:50:01,791: download_one_from() 'Could not download wallpaper:'
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: Traceback (most recent call last):
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/VarietyWindow.py", line 1156, in download_one>
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: file = downloader.download_one()
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/plugins/downloaders/DefaultDownloader.py", li>
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: items = self.fill_queue()
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/plugins/builtin/downloaders/ChromeOSWallpaper>
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: manifest = Util.fetch_json(MANIFEST_URL)
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/Util.py", line 643, in fetch_json
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: return Util.request(url, data, **request_kwargs).json()
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/Util.py", line 622, in request
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: r.raise_for_status()
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/requests/models.py", line 940, in raise_for_status
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: raise HTTPError(http_error_msg, response=self)
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://storage.googleap>
mag 08 10:50:02 danieledell-Inspiron-N5110 systemd[1476]: gnome-launched-gnome-session-quit-23825.scope: Succeeded.
mag 08 10:50:02 danieledell-Inspiron-N5110 systemd[1476]: Stopped target GNOME Power management handling.
mag 08 10:50:02 danieledell-Inspiron-N5110 systemd[1476]: Stopped target GNOME Date & Time handling.
mag 08 10:50:02 danieledell-Inspiron-N5110 systemd-logind[889]: System is rebooting.
mag 08 10:50:02 danieledell-Inspiron-N5110 gsd-print-notif[1997]: Source ID 5 was not found when attempting to remove it
lines 1-42
-- Logs begin at Fri 2020-05-08 10:49:47 CEST, end at Fri 2020-05-08 15:04:51 CEST. --
mag 08 10:49:47 danieledell-Inspiron-N5110 systemd[1]: systemd-hostnamed.service: Succeeded.
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_show_internal: assertion 'GDK_IS_WINDOW (window)' failed
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:48 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:49 danieledell-Inspiron-N5110 gnome-shell[1837]: Could not create transient scope for PID 23708: GDBus.Error:org.freedesktop.DBus.Error>
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:50 danieledell-Inspiron-N5110 nautilus[23368]: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
mag 08 10:49:59 danieledell-Inspiron-N5110 variety.desktop[23806]: Schema «org.cinnamon.desktop.background» inesistente
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: vte-spawn-fd0618c6-ba22-4332-829c-7faeee7ed579.scope: Succeeded.
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: gnome-terminal-server.service: Succeeded.
mag 08 10:50:00 danieledell-Inspiron-N5110 systemd[1476]: Started Application launched by gnome-shell.
mag 08 10:50:01 danieledell-Inspiron-N5110 dbus-daemon[853]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packag>
mag 08 10:50:01 danieledell-Inspiron-N5110 systemd[1]: Starting PackageKit Daemon...
mag 08 10:50:01 danieledell-Inspiron-N5110 PackageKit[23828]: daemon start
mag 08 10:50:01 danieledell-Inspiron-N5110 dbus-daemon[853]: [system] Successfully activated service 'org.freedesktop.PackageKit'
mag 08 10:50:01 danieledell-Inspiron-N5110 systemd[1]: Started PackageKit Daemon.
mag 08 10:50:01 danieledell-Inspiron-N5110 gnome-shell[1837]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: ERROR: 2020-05-08 10:50:01,791: download_one_from() 'Could not download wallpaper:'
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: Traceback (most recent call last):
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/VarietyWindow.py", line 1156, in do>
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: file = downloader.download_one()
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/plugins/downloaders/DefaultDownload>
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: items = self.fill_queue()
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/plugins/builtin/downloaders/ChromeO>
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: manifest = Util.fetch_json(MANIFEST_URL)
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/Util.py", line 643, in fetch_json
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: return Util.request(url, data, **request_kwargs).json()
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/variety/Util.py", line 622, in request
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: r.raise_for_status()
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: File "/usr/lib/python3/dist-packages/requests/models.py", line 940, in raise_for>
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: raise HTTPError(http_error_msg, response=self)
mag 08 10:50:01 danieledell-Inspiron-N5110 variety.desktop[3398]: requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://storag>
lines 1-37
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 15:07
da frapox
Hai rifatto lo stesso errore di prima...
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 16:14
da domes
frapox ha scritto: ↑venerdì 8 maggio 2020, 15:07
Hai rifatto lo stesso errore di prima...
non riesco a inserire un file .txt
Re: Filesystem improvvisamente pieno
Inviato: venerdì 8 maggio 2020, 22:58
da Stealth
Vabbè dai, leggilo te, non dovrebbe essere difficile individuare una cosa, qualsiasi cosa sia, ripetuta mille miliardi di volte. Trova quella riga e postala qui. E se proprio non ci riesci incolla tutto qua
https://pastebin.com/
e poi incolla qui il link
Re: Filesystem improvvisamente pieno
Inviato: sabato 9 maggio 2020, 9:48
da domes
... qualsiasi cosa sia, ripetuta mille miliardi di volte. Trova quella riga e postala qui.
Per esempio questo risulta da
journalctl
Codice: Seleziona tutto
message repeated 7 times: [file '/var/log/syslog'[7] write error - see https://www.rsyslo>
mag 08 13:54:27 danieledell-Inspiron-N5110 rsyslogd[845]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be proc>
mag 08 13:54:27 danieledell-Inspiron-N5110 rsyslogd[845]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write->
mag 08 13:54:27 danieledell-Inspiron-N5110 rsyslogd[845]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be proc>
mag 08 13:54:27 danieledell-Inspiron-N5110 rsyslogd[845]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write->
e anche:
Codice: Seleziona tutto
start X Wayland
mag 08 13:54:29 danieledell-Inspiron-N5110 systemd[991]: Failed to start Tracker metadata extractor.
mag 08 13:54:29 danieledell-Inspiron-N5110 systemd[991]: Failed to start GNOME Shell on Wayland.
mag 08 13:54:30 danieledell-Inspiron-N5110 systemd[991]: Failed to start Tracker file system data miner.
mag 08 13:54:30 danieledell-Inspiron-N5110 systemd[991]: Failed to start Tracker file system data miner.
mag 08 13:54:30 danieledell-Inspiron-N5110 systemd[991]: Failed to start Tracker metadata extractor.
mag 08 13:54:30 danieledell-Inspiron-N5110 systemd[991]: Failed to start Tracker metadata database store and lookup manager.
mag 08 13:54:30 danieledell-Inspiron-N5110 systemd[991]: Failed to start Tracker metadata database store and lookup manager.
mag 08 13:54:34 danieledell-Inspiron-N5110 rsyslogd[845]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write->
mag 08 13:54:34 danieledell-Inspiron-N5110 rsyslogd[845]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be proc>
e anche:
Codice: Seleziona tutto
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: Loaded firmware version: 18.168.6.1
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | OK
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | uPc
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | branchlink1
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | branchlink2
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | interruptlink1
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | interruptlink2
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | data1
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | data2
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | line
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | beacon time
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | tsf low
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | tsf hi
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | time gp1
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | time gp2
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | time gp3
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | uCode version
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | hw version
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | board version
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | hcmd
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | isr0
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | isr1
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | isr2
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | isr3
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | isr4
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | isr_pref
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | wait_event
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | l2p_control
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | l2p_duration
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | l2p_mhvalid
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | l2p_addr_match
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | lmpm_pmg_sel
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | timestamp
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: 0x00000000 | flow_handler
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: Start IWL Event Log Dump: nothing in log
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: Failed to run INIT ucode: -5
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: Unable to initialize device.
mag 08 13:56:47 danieledell-Inspiron-N5110 kernel: iwlwifi 0000:09:00.0: Hardware error detected. Restarting.
e alla fine:
Codice: Seleziona tutto
-- Reboot --
mag 08 14:00:08 danieledell-Inspiron-N5110 kernel: Bluetooth: hci0: unexpected event for opcode 0x0000
mag 08 14:01:09 danieledell-Inspiron-N5110 kernel: hdaudio hdaudioC0D3: Unable to bind the codec
mag 08 14:04:55 danieledell-Inspiron-N5110 wpa_supplicant[909]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supp>
-- Reboot --
mag 08 14:05:17 danieledell-Inspiron-N5110 gdm-password][1444]: gkr-pam: unable to locate daemon control file
mag 08 14:16:39 danieledell-Inspiron-N5110 systemd[1451]: Failed to start Application launched by gnome-shell.
mag 08 14:16:44 danieledell-Inspiron-N5110 systemd[1451]: Failed to start Application launched by gnome-shell.
mag 08 14:17:49 danieledell-Inspiron-N5110 kernel: uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -110 (exp. 1).
mag 08 14:18:02 danieledell-Inspiron-N5110 systemd[1451]: Failed to start Application launched by gnome-shell.
mag 08 14:20:14 danieledell-Inspiron-N5110 systemd[1451]: Failed to start Application launched by gnome-shell.
mag 08 14:21:28 danieledell-Inspiron-N5110 wpa_supplicant[852]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supp>
mag 08 14:23:39 danieledell-Inspiron-N5110 systemd[1451]: Failed to start Application launched by gnome-shell.
mag 08 14:24:05 danieledell-Inspiron-N5110 systemd[1451]: Failed to start Application launched by gnome-shell.
mag 08 14:24:42 danieledell-Inspiron-N5110 wpa_supplicant[852]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supp>
-- Reboot --
mag 08 14:25:17 danieledell-Inspiron-N5110 kernel: Bluetooth: hci0: unexpected event for opcode 0x0000
mag 08 14:25:26 danieledell-Inspiron-N5110 gdm-password][1453]: gkr-pam: unable to locate daemon control file
mag 08 14:58:29 danieledell-Inspiron-N5110 systemd[1478]: Failed to start Application launched by gnome-shell.
mag 08 14:59:20 danieledell-Inspiron-N5110 wpa_supplicant[852]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supp>
-- Reboot --
mag 08 14:59:47 danieledell-Inspiron-N5110 gdm-password][1574]: gkr-pam: unable to locate daemon control file
mag 08 15:12:35 danieledell-Inspiron-N5110 wpa_supplicant[859]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supp>
-- Reboot --
mag 08 15:43:40 danieledell-Inspiron-N5110 kernel: Bluetooth: hci0: unexpected event for opcode 0x0000
mag 08 15:43:48 danieledell-Inspiron-N5110 gdm-password][1432]: gkr-pam: unable to locate daemon control file
mag 08 15:51:25 danieledell-Inspiron-N5110 kernel: uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -110 (exp. 1).
lines 10893-10929/10929 (END)
Re: Filesystem improvvisamente pieno
Inviato: domenica 10 maggio 2020, 12:09
da domes
domes ha scritto: ↑venerdì 8 maggio 2020, 9:48
L'unica cosa che ho fatto è istallare un secondo ssd
I problemi sono iniziati da quanto ho istallato questo
https://www.amazon.it/gp/product/B07KB2 ... UTF8&psc=1 con un altro ssd nel bay del cd-rom e sembrano essere scomparsi da quando l'ho tolto.....peccato perchè funzionava benissimo......
Re: Filesystem improvvisamente pieno
Inviato: martedì 12 maggio 2020, 11:08
da domes
Purtroppo oggi si è ripresentato il problema. Ho trovato il filesystem all'80%.
Sono riuscito a copiare il file syslog e kern.log di dimensioni di 2.3gb e 2.7gb ma nel momento di aprirli nel consultarli tutto il sistema va in freeze e non posso fare altro che un reboot.
Re: Filesystem improvvisamente pieno
Inviato: martedì 12 maggio 2020, 11:23
da frapox
domes ha scritto: ↑martedì 12 maggio 2020, 11:08
Purtroppo oggi si è ripresentato il problema. Ho trovato il filesystem all'80%.
Sono riuscito a copiare il file syslog e kern.log di dimensioni di 2.3gb e 2.7gb ma nel momento di aprirli nel consultarli tutto il sistema va in freeze e non posso fare altro che un reboot.
Prova ad aprirli con
less da terminale:
Occhio che quei Caddy lì possono dare problemi con linux, ne ho avuti anche io, e spammarti i log fino alla morte... controlla sempre i commenti e la compatibilità con linux prima di comprare.
Re: Filesystem improvvisamente pieno
Inviato: venerdì 22 maggio 2020, 20:45
da domes
Dopo qualche tempo che il problema non si era ripresentato, negli ultimi giorni mi sono accorto in un paio di occasioni che il filesystem si riempiva improvvisamente dopo un lungo uso del computer.......semplicemente ho risolto rapidamente con
Questo ovviamente non risolveva il problema ma mi permetteva di lavorare.
Negli ultimi giorni però si stà ripetendo molto piu spesso e soprattutto al primo avvio. Ho notato che in questi primi avvii in cui i due file
kern.log e
syslog diventavano giganti rapidamente da 500mb a qualche Gyga, anche la wifi non riusciva a trovare la rete di casa e non si poteva connetere. Tutto si conclude con un freeze del sistema e sono costretto al reboot dal pulsante di avvio. Una volta cancellata tutta la cartella
/var/log anche il wifi riprende normalmente a funzionare e ricevere senza problemi e posso lavorare per ore.
Sono riuscito un paio di volte ad aver tempo di copiare i due file ma sinceramente non riesco a capire dove devo guardare.
Avevo visto ripetersi delle righe con errori di Variety una app che cambia lo sfondo a intervalli regolari, che uso da molti anni, ma ho notato che disistallandolo il problema resta.
Che cosa posso fare?
Re: Filesystem improvvisamente pieno
Inviato: venerdì 22 maggio 2020, 21:55
da Stealth
Abbi pazienza, ma te quei files non li vuoi leggere e non vuoi farli leggere a noi perchè non li posti. Ti ho anche indicato pastebin... ma niente. E secondo te cosa dovremmo capire? La prima cosa che devi fare è sistemare il logrotate
http://guide.debianizzati.org/index.php ... ca_dei_log
e ti metti al riparo dal blocco del sistema. Così avrai tempo e modo di indagare meglio, perchè in questo modo non se ne viene fuori