I just did a fresh install of 11.3 KDE x86_64 this afternoon. I started out with 4.* GiB used in /. Now a few hours later sysinfo and dolphin are showing that 8.5 GiB are used.
What I’ve done is add repos, update, ran SystemSettings and installed nvidia driver. What could have added 4 or so GiB to my / partition? I’ve installed a few extra packages like Thunderbird but not many. This is disturbing… FWIW I’m showing GiB used in separate /home partition.
So I sure do not know where another 4 GB of files could have come from but you might want to configure the automatic removal of temp files on reboot and then reboot to see if that might have been the problem. To make this change…
Open /etc/sysconfig/cron as root and search for a line saying
CLEAR_TMP_DIRS_AT_BOOTUP="no"
…and edit “no” to “yes”. This could also be done via GUI: YaST → “Editor for /etc/sysconfig”.
Or to edit this file as root manually enter the menu Run Command:
kdesu kwrite /etc/sysconfig/cron
Let us know if this did anything good for you.
Thank You,
Thanks for the tip. I tried that and rebooted with no change.
dwightpaige79 it is very hard to make the disk usage numbers add up. I see that some totals list the actual file sizes while others, relates to real disk space usage, the total disk space allocated, which is larger size. While you may figure it out, I am not sure it is something to worry about unless you are running out of disk space. I just checked my /home folder and in the “My Computer” it says it is using 22.2 GiB. Yet, in my home folder, and I have only one user besides root, is only 4.9 Gib in size. This is a big difference, however the whole thing sits on a 500 Gib drive and so the difference is small potatoes for now. I would suggest to get on with your discoveries in openSUSE while being on the lookout for any other clues.
Thank You,
On Fri July 16 2010 05:06 pm, jdmcdaniel3 wrote:
>
> So I sure do not know where another 4 GB of files could have come from
> but you might want to configure the automatic removal of temp files on
> reboot and then reboot to see if that might have been the problem. To
> make this change…
>
> Open /etc/sysconfig/cron as root and search for a line saying
>
>
> Code:
> --------------------
> CLEAR_TMP_DIRS_AT_BOOTUP=“no”
> --------------------
> …and edit “no” to “yes”. This could also be done via GUI: YaST →
> “Editor for /etc/sysconfig”.
>
> Or to edit this file as root manually enter the menu Run Command:
>
>
> Code:
> --------------------
> kdesu kwrite /etc/sysconfig/cron
> --------------------
> Let us know if this did anything good for you.
>
> Thank You,
>
Just a bit of added information. You can make changes to /etc/sysconfig via
YaST. YaST–>System–>/etc/sysconfig Editor. The Cron section is under
System.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
/tmp would hardly fill up after such a short time.
I think to answer the question “how?” one must answer the question “what?” first, that is to say to find out what files are filling that partition. Use ‘df’ and ‘du’ on the command line or apps like Filelight to find out about that.
what was the total of downloads for all the software you installed?
did you compile the nvidia driver (requiring kernel source download)?
did you manually install some or all of the bits (using rpm command,
compile from source, etc) or did you use YaST…
if you installed them manually: did you delete the rpm/source tar-ball
and compile directory once you ran the install? if not, then all that
unneeded stuff is still there (wherever you put it)!
if you installed via YaST: you have the ability to either save the
downloaded packages or not…if you save them then they are not only
expanded (unzipped) to their full installed size but also sitting on
your drive in their full downloaded size…
and, if you often (or ever) drag a folder somewhere and click to
‘copy’ it to the new location–you might have accidentally dropped
it in the wrong place and later see that and copy it again to the
right place…in which case the extra folder will remain hidden in
some wrong place, until you find and remove it…
oh, and if you initially installed just KDE and in your updating and
adding of software elected to install a Gnome app then the system had
to add a large portion of the Gnome base system to support even one
application…and, the same is true if you initially installed just
Gnome and then later added any KDE app…and, the same if you decided
to try LXDE, etc etc etc…
last: i can’t tell if you dual boot or not, but if you do i ask you to
compare the total size of your Linux system partition to the size of
the other system’s space, and take into account the programs each has
and ask if you don’t notice a great savings when comparing openSUSE to
OldBloat?
ps: thank you for rebuilding NOLA, one of my favorite cities on
earth…have spend many hours on the wooden bench (and floor in
front) of Preservation Hall…first marveled Sweet Emma, in the spring
of '64…i know what it means to miss Narlins . . .
–
Enjoy Packman’s benefits? Show your appreciation by donating at
http://se.unixheads.org/?donate
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
Thanks all for the input. I installed 11.3 x86_64 KDE from DVD adding only 32 bit runtime to default install. That installs 1274 packages. Immediately after install sysinfo and dolphin show 4.3 GB used on / partition [there is separate /home partition]. The ‘nouveau’ driver was quite buggy so I installed ‘nvidia’ driver ‘The Hard Way’. This does add some kernel packages and I did install some other packages. It had to be something I did or a glich or an error in what sysinfo and dolphin were reporting. I reinstalled yesterday exactly the same way except reformatting / partition only. I installed nvidia driver from this repo:
Index of /repositories/home:/Yareg/openSUSE_11.3
I have actually added more packages than in previous install yet sysinfo and dolphin report 5.6 GiB used on / partition and 9.7 GiB free. I ran GParted from SystemRescue CD and it, of course, shows something different. GParted shows / partition as 5.28 GiB used and 10.34 free. All in all what I’d expect at this point. My box is indeed multi-boot with / and /home partitions each for Fedora 13 x86_64 KDE4 and Mandriva 2010.1 x86_64 KDE4.
Should I encounter something like this again I’ve been studying the df and du commands and I found a rpm for Filelight 1.0-17.1-x86_64 that is KDE 3 dependent. I have downloaded the source tarball for a newer KDE 4 version:
but I’ll have to learn how to make a rpm from that. Or actually ask on openSuSE Build Service if anyone is working on that.
Thanks again.
I forgot to add this showing current disk usage of my current openSuSE install:
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 16G 5.0G 9.7G 34% /
devtmpfs 1.9G 232K 1.9G 1% /dev
tmpfs 2.0G 4.0K 2.0G 1% /dev/shm
/dev/sda15 492G 66G 401G 15% /data1
/dev/sdb1 294G 191M 279G 1% /data2
/dev/sda2 30G 413M 28G 2% /home
that looks normal to me. I see / using 5 G, not 8.5.
/var and /tmp tend to be the worst offenders for unnecessarily filling up drive space. I’d run (with sudo) these to check them:
du -sh /var (gives you total size of /var)
du -sh /tmp (gives you total size of /tmp)
du -sh /var/* (gives you size of /var’s contents)
du -sh /tmp/* (goves you size of /tmp’s contents)
You can run the “My Computer” function as root and apparently get a better disk usage for / & /home by using the menu Run Command:
kdesu kfmclient openProfile webbrowsing sysinfo:/
You can also use this command to create a “Link to Application” on your Desktop if you like to use the “My Computer” as root on a regular basis.
Thank You,
Here’s the difference (at least for a part). In the first install you compiled the driver yourself, needing the kernel-source amonst others. That only is .5 GB on disk.
And this one: have you been experimenting with a printer install? I gave some printer a try with my laptop (it did not work with 11.2), got it working, but once back home I discovered that a lot of the test printjobs were still there. Had to manually remove them.
That’s good info. And interesting. So thanks again!
:~> sudo du -sh /var
du: cannot access `/var/lib/ntp/proc/4900/task/4900/fd/4': No such file or directory
du: cannot access `/var/lib/ntp/proc/4900/task/4900/fdinfo/4': No such file or directory
du: cannot access `/var/lib/ntp/proc/4900/fd/4': No such file or directory
du: cannot access `/var/lib/ntp/proc/4900/fdinfo/4': No such file or directory
208M /var
:~> sudo du -sh /tmp
100K /tmp
:~> sudo du -sh /var/*
27M /var/adm
87M /var/cache
4.0K /var/crash
4.0K /var/games
du: cannot access `/var/lib/ntp/proc/4906/task/4906/fd/4': No such file or directory
du: cannot access `/var/lib/ntp/proc/4906/task/4906/fdinfo/4': No such file or directory
du: cannot access `/var/lib/ntp/proc/4906/fd/4': No such file or directory
du: cannot access `/var/lib/ntp/proc/4906/fdinfo/4': No such file or directory
54M /var/lib
32K /var/lock
29M /var/log
0 /var/mail
4.0K /var/opt
248K /var/run
128K /var/spool
13M /var/tmp
4.0K /var/X11R6
12K /var/yp
:~> sudo du -sh /tmp/*
28K /tmp/1450816653
4.0K /tmp/gpg-9zFt42
4.0K /tmp/hsperfdata_root
20K /tmp/kde-dwight
8.0K /tmp/kde-root
8.0K /tmp/ksocket-dwight
4.0K /tmp/ksocket-root
4.0K /tmp/orbit-dwight
4.0K /tmp/pulse-CcctT9RwKSB1
0 /tmp/qt_temp.KS5590
0 /tmp/qt_temp.Nh5590
0 /tmp/qt_temp.wN5590
0 /tmp/qt_temp.yp5590
I’d say that looks pretty clean. But it is a fresh install. ‘:~> sudo du -sh /var/lib/ntp/proc/*’ shows a bunch of zeros:
:~> sudo du -sh /var/lib/ntp/proc/*
0 /var/lib/ntp/proc/1
...
0 /var/lib/ntp/proc/acpi
0 /var/lib/ntp/proc/asound
0 /var/lib/ntp/proc/buddyinfo
0 /var/lib/ntp/proc/bus
0 /var/lib/ntp/proc/cmdline
0 /var/lib/ntp/proc/config.gz
0 /var/lib/ntp/proc/cpuinfo
0 /var/lib/ntp/proc/crypto
0 /var/lib/ntp/proc/devices
0 /var/lib/ntp/proc/diskstats
0 /var/lib/ntp/proc/dma
0 /var/lib/ntp/proc/driver
0 /var/lib/ntp/proc/execdomains
0 /var/lib/ntp/proc/fb
0 /var/lib/ntp/proc/filesystems
0 /var/lib/ntp/proc/fs
0 /var/lib/ntp/proc/interrupts
0 /var/lib/ntp/proc/iomem
0 /var/lib/ntp/proc/ioports
0 /var/lib/ntp/proc/irq
0 /var/lib/ntp/proc/kallsyms
0 /var/lib/ntp/proc/kcore
0 /var/lib/ntp/proc/kdb
0 /var/lib/ntp/proc/key-users
0 /var/lib/ntp/proc/kmsg
0 /var/lib/ntp/proc/kpagecount
0 /var/lib/ntp/proc/kpageflags
0 /var/lib/ntp/proc/latency_stats
0 /var/lib/ntp/proc/loadavg
0 /var/lib/ntp/proc/locks
0 /var/lib/ntp/proc/mdstat
0 /var/lib/ntp/proc/meminfo
0 /var/lib/ntp/proc/misc
0 /var/lib/ntp/proc/modules
0 /var/lib/ntp/proc/mounts
0 /var/lib/ntp/proc/mtrr
0 /var/lib/ntp/proc/net
0 /var/lib/ntp/proc/pagetypeinfo
0 /var/lib/ntp/proc/partitions
0 /var/lib/ntp/proc/reserve_info
0 /var/lib/ntp/proc/sched_debug
0 /var/lib/ntp/proc/schedstat
0 /var/lib/ntp/proc/scsi
0 /var/lib/ntp/proc/self
0 /var/lib/ntp/proc/slabinfo
0 /var/lib/ntp/proc/softirqs
0 /var/lib/ntp/proc/splash
0 /var/lib/ntp/proc/stat
0 /var/lib/ntp/proc/swaps
0 /var/lib/ntp/proc/sys
0 /var/lib/ntp/proc/sysrq-trigger
0 /var/lib/ntp/proc/sysvipc
0 /var/lib/ntp/proc/timer_list
0 /var/lib/ntp/proc/timer_stats
0 /var/lib/ntp/proc/tty
0 /var/lib/ntp/proc/uptime
0 /var/lib/ntp/proc/version
0 /var/lib/ntp/proc/vmallocinfo
0 /var/lib/ntp/proc/vmstat
0 /var/lib/ntp/proc/zoneinfo
So I’ve learned a bit more. Next time I see something like that I’ll know much better where and how to look. And there’s still Filelight to suss out.
As I remember the printer installed with no problem. So I don’t think there were a lot of unprinted jobs. But food for contemplation none the less.
Dwight-
I am a bit late on this thread, I realize …
For a quick “What’s chewing up my disk?” check, you can do:
From Application Launcher:
System -> File Manager -> Konqueror (file manager)
In Konqueror:
View -> View mode -> File Size View
It can take some time to walk the directory tree selected, but the resulting graph is nicely illustrative of storage usage.
HTH
Thanks. That IS interesting. Running sysinfo as root clearly does give different disk usage results than as user. But is it more accurate? If so why? I certainly like the results from running as root better and they actually make more sense. Except as soon as I typed the last sentence I have to ask myself “Why do those results make more sense?”. Guess I’m still learning… This thread has been an asset to that “learning thing” though. At least for me.
The 20 somethings in this house are right. Dwight will never get everything figured out.
Thanks dwightpaige79 for your comments on using sysinfo as root. I was wondering if anyone else had even tried this and noticed the difference in used space that is reported when run as root.
Thank You,
Permissions? There are directories that users cannot even enter, and hence cannot calculate how much room the files take up.
Looking at the properties of ‘/var’ for instance in Dolphin on one hand and Dolphin as root on the other hand yields totally different results:
326.9 MiB, 1,638 files, 480 sub-folders
vs
592.8 MiB, 1,968 files, 514 sub-folders
(YMMV on the exact numbers of course)