[opensuse] root partition overflowing during update
Hello listmates, I've got an interesting issue. usually, when I install Linux I break the disk up into partiotions; in case of OpenSuSe I usually end up with the following partitions: /(root) 2-4GB /usr 20-25GB /opt 8-12GB /var 8-12GB /srv 5-10 GB /tmp 5-10 GB /home whatever's left of the disk Usually, I end up with less than 1 GB (about 200-300 MB) filed up in my root partition. Yesterday, I attempted to install OpenSuSE 10.3 on a machine where I allocated 2 GB for the root partition. It installed fine, but then when I decided to do the auto update right away it filled the root partition! Has anyone else experienced that? Why would that happen - given that original packages installed only demanded about 200 MB in the / partition? So, in short - what am I doing wrong, what should I be doing? Thanks. Boris. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Sep 10, 2008 at 10:42 AM, Boris Epstein
Hello listmates,
I've got an interesting issue. usually, when I install Linux I break the disk up into partiotions; in case of OpenSuSe I usually end up with the following partitions:
/(root) 2-4GB /usr 20-25GB /opt 8-12GB /var 8-12GB /srv 5-10 GB /tmp 5-10 GB /home whatever's left of the disk
Usually, I end up with less than 1 GB (about 200-300 MB) filed up in my root partition.
Yesterday, I attempted to install OpenSuSE 10.3 on a machine where I allocated 2 GB for the root partition. It installed fine, but then when I decided to do the auto update right away it filled the root partition! Has anyone else experienced that? Why would that happen - given that original packages installed only demanded about 200 MB in the / partition?
So, in short - what am I doing wrong, what should I be doing?
Thanks.
Boris, I don't know the answer, but I can commiserate. I had a machine that had a 4GB root partition. Not sure how often it had been updated, but possibly from the 8.2 days. Upgrading from 10.2 to 11.0 overflowed root. My solution was to deselect all the X based apps (including Gnome, KDE, etc.) and then upgrade. That worked. After the upgrade I reinstalled KDE. In my case the computer was a fileserver primarily, so KDE etc. was a luxury anyway. If I would have had a lot of configuration files etc. associated with KDE, I assume they would have been reset to default by my process, but I did not worry about it. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg Freemyer pecked at the keyboard and wrote:
with the following partitions:
/(root) 2-4GB /usr 20-25GB /opt 8-12GB /var 8-12GB /srv 5-10 GB /tmp 5-10 GB /home whatever's left of the disk
Usually, I end up with less than 1 GB (about 200-300 MB) filed up in my root partition.
Yesterday, I attempted to install OpenSuSE 10.3 on a machine where I allocated 2 GB for the root partition. It installed fine, but then when I decided to do the auto update right away it filled the root partition! Has anyone else experienced that? Why would that happen - given that original packages installed only demanded about 200 MB in the / partition?
So, in short - what am I doing wrong, what should I be doing?
Thanks.
Boris,
I don't know the answer, but I can commiserate.
I had a machine that had a 4GB root partition. Not sure how often it had been updated, but possibly from the 8.2 days.
Upgrading from 10.2 to 11.0 overflowed root.
My solution was to deselect all the X based apps (including Gnome, KDE, etc.) and then upgrade. That worked.
After the upgrade I reinstalled KDE.
In my case the computer was a fileserver primarily, so KDE etc. was a luxury anyway. If I would have had a lot of configuration files etc. associated with KDE, I assume they would have been reset to default by my process, but I did not worry about it.
Greg
Two perfect examples of why you don't ( today anyway ) need many seperate partitions. Unless you can perfectly guess what sizes are needed to day and in the future for upgrades don't do it. At most I use 4 partitions, swap / /var and /tmp with most going to /. I don't need the headaches. As far as putting /home separate, when I upgrade I copy /home to a spare harddrive until the upgrade is complete and then copy it back. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2008/09/10 10:42 (GMT-0400) Boris Epstein composed:
I've got an interesting issue. usually, when I install Linux I break the disk up into partiotions; in case of OpenSuSe I usually end up with the following partitions:
/(root) 2-4GB /usr 20-25GB /opt 8-12GB /var 8-12GB /srv 5-10 GB /tmp 5-10 GB /home whatever's left of the disk
Usually, I end up with less than 1 GB (about 200-300 MB) filed up in my root partition.
Yesterday, I attempted to install OpenSuSE 10.3 on a machine where I allocated 2 GB for the root partition. It installed fine, but then when I decided to do the auto update right away it filled the root partition! Has anyone else experienced that? Why would that happen - given that original packages installed only demanded about 200 MB in the / partition?
So, in short - what am I doing wrong, what should I be doing?
I can only guess that what's wrong might be failure to mount the /var and/or /tmp partition(s). Regardless the cause of the immediate problem, you can make the space on your small / partitions more effectively utilized by making sure they get formatted with a small block size. The default for several years has been 4096 (8 sectors). On partitions less than 8-10G, I always set the block size to 1024 (2 sectors), which frees up a lot of space wasted on small files. -- "Unless the Lord builds the house, its builders labor in vain." Psalm 127:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 11 Sep 2008 00:55:55 Felix Miata wrote:
[...]
Yesterday, I attempted to install OpenSuSE 10.3 on a machine where I allocated 2 GB for the root partition. It installed fine, but then when I decided to do the auto update right away it filled the root partition! Has anyone else experienced that? Why would that happen - given that original packages installed only demanded about 200 MB in the / partition?
So, in short - what am I doing wrong, what should I be doing?
I can only guess that what's wrong might be failure to mount the /var and/or /tmp partition(s).
I"ve also seen this with multiple kernel versions installed - /lib ends up filling up the partition with multiple copies of all the shared libraries - one for each kernel version (this happened to me on a Fedora box with around 6 different kernel versions plus sources installed). /usr/bin and /usr/lib may also be using up a fair amount of space depending on what is installed. Filelight is your friend in this case - it will show you where your space is being gobbled up... -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== Why is the alphabet in that order? Is it because of that song?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-09-10 at 10:42 -0400, Boris Epstein wrote:
So, in short - what am I doing wrong, what should I be doing?
I had that problem once, when upgrading from 7.3 to 8.1, and it was because the upgrader failed to mount one or more of the needed partitions. Since them, I always check that the partitions are mounted, and if not, I mount them manually, before giving it the go ahead. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjH7pIACgkQtTMYHG2NR9VRaQCgivbyrJVEAyDBVw73a2wvXZ9z S6gAn3OrnqRPT3tZznfxthl2JJ2iv1zr =auUw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Sep 10, 2008 at 11:58 AM, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2008-09-10 at 10:42 -0400, Boris Epstein wrote:
So, in short - what am I doing wrong, what should I be doing?
I had that problem once, when upgrading from 7.3 to 8.1, and it was because the upgrader failed to mount one or more of the needed partitions. Since them, I always check that the partitions are mounted, and if not, I mount them manually, before giving it the go ahead.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkjH7pIACgkQtTMYHG2NR9VRaQCgivbyrJVEAyDBVw73a2wvXZ9z S6gAn3OrnqRPT3tZznfxthl2JJ2iv1zr =auUw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Actually, it wasn't even a release-to-release upgrade - just an update to get the newest RPM's for the release being installed (10.3). Boris. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-09-10 at 12:06 -0400, Boris Epstein wrote: (Please, prune the quotes)
Actually, it wasn't even a release-to-release upgrade - just an update to get the newest RPM's for the release being installed (10.3).
Ah? You mean you were runnin YOU or equivalent. Mmm... Then use one of those tools to find out where disk-space has gone to. I like "kdirstat" and "baobab" (kde/gnome). You may have to run them as root. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjH9JwACgkQtTMYHG2NR9X5mwCfSJGgPNcThmrVpe3ubQBWfOMo B9QAn0cPnxkHJ4EbmARp5RZONq8Kh7RQ =yMmp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2008-09-10 at 10:42 -0400, Boris Epstein wrote:
Hello listmates,
I've got an interesting issue. usually, when I install Linux I break the disk up into partiotions; in case of OpenSuSe I usually end up with the following partitions:
/(root) 2-4GB /usr 20-25GB /opt 8-12GB /var 8-12GB /srv 5-10 GB /tmp 5-10 GB /home whatever's left of the disk
Usually, I end up with less than 1 GB (about 200-300 MB) filed up in my root partition.
So, in short - what am I doing wrong, what should I be doing?
Hi Boris, You're not doing anything wrong, it's just a matter of what you're doing with the machine.... Normally, when i don't have the slightest idea how much i need for partitions, i do the installation twice: The first time just swap and /, and see how it fills up, specially when installing on machine with small disks. Nowadays i normally use this scheme: /boot 100mb ext2 all left on lvm Within lvm: / 500MB reiser /home 100MB ext3 (normally i have home imported from a nfs-server) /usr 2GB reiser /srv 2GB reiser (holds: ldap, mysql, tftp, www, ftp, common-data) /tmp 500MB reiser (auto-purge after 3 days, autoclean after booting) /opt 500MB reiser (larger if still using KDE3) /var 500MB reiser (space needed for rpm-cache) /var/spool 500MB reiser (for lpr, mail, ...) /var/log 500MB reiser /var/tmp is a symlink to /tmp It means that no run-away process or _sloppy-user_ can grow beyond its limits and harm the other processes. If i need any space (even during installation), i can grow any partition with lvextend and resize_reiserfs. I try to keep usr and opt at 70%. Only home and srv grow in time /var/log is controlled by logrotate. hw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Boris Epstein -
Carlos E. R. -
Felix Miata -
Greg Freemyer -
Hans Witvliet -
Ken Schneider -
Rodney Baker