Gavin Spomer
2008-Jun-06 20:04 UTC
6.2-STABLE => 7.0-STABLE Upgrade root partition more full
I successfully did my first FreeBSD upgrade yesterday after looking at the manual, and cross referencing with Googling and getting help from our network engineer here at CWU. Before the upgrade, running df showed: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 507630 77662 389358 17% / devfs 1 1 0 100% /dev /dev/da0s1e 507630 588 466432 0% /tmp /dev/da0s1f 268217320 4866120 241893816 2% /usr /dev/da0s1d 4298926 162066 3792946 4% /var Now it shows: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 507630 184834 282186 40% / devfs 1 1 0 100% /dev /dev/da0s1e 507630 426 466594 0% /tmp /dev/da0s1f 268217320 5514844 241245092 2% /usr /dev/da0s1d 4298926 187570 3767442 5% /var Notice the the increase in the root partition. Should I have made this partition bigger when I first installed? Is there any cleaning up I can do after version upgrades? I would've thought /usr would be the one that grew more, but then again my /usr partition is fairly sizeable. Does 7.0 just take up a lot more of the root partition than 6.2? - Gavin
Clifton Royston
2008-Jun-06 20:56 UTC
6.2-STABLE => 7.0-STABLE Upgrade root partition more full
On Fri, Jun 06, 2008 at 11:37:51AM -0700, Gavin Spomer wrote:> I successfully did my first FreeBSD upgrade yesterday after looking at the manual, and cross referencing with Googling and getting help from our network engineer here at CWU. Before the upgrade, running df showed: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 77662 389358 17% / > devfs 1 1 0 100% /dev > /dev/da0s1e 507630 588 466432 0% /tmp > /dev/da0s1f 268217320 4866120 241893816 2% /usr > /dev/da0s1d 4298926 162066 3792946 4% /var > > Now it shows: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 184834 282186 40% / > devfs 1 1 0 100% /dev > /dev/da0s1e 507630 426 466594 0% /tmp > /dev/da0s1f 268217320 5514844 241245092 2% /usr > /dev/da0s1d 4298926 187570 3767442 5% /var > > Notice the the increase in the root partition. Should I have made > this partition bigger when I first installed? Is there any cleaning > up I can do after version upgrades? I would've thought /usr would be > the one that grew more, but then again my /usr partition is fairly > sizeable. Does 7.0 just take up a lot more of the root partition than > 6.2?Yes, it just does. It should not keep expanding, though. IMHO, you should still be fine as long as you've got /tmp, /usr/, /var, and the home directories residing on other partitions. If you're using /home under / for home directories, you might want to move it to /usr/home and symlink /home to it. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services
Gavin Spomer wrote:> I successfully did my first FreeBSD upgrade yesterday after looking at the manual, and cross referencing with Googling and getting help from our network engineer here at CWU. Before the upgrade, running df showed: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 77662 389358 17% / > devfs 1 1 0 100% /dev > /dev/da0s1e 507630 588 466432 0% /tmp > /dev/da0s1f 268217320 4866120 241893816 2% /usr > /dev/da0s1d 4298926 162066 3792946 4% /var > > Now it shows: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 184834 282186 40% / > devfs 1 1 0 100% /dev > /dev/da0s1e 507630 426 466594 0% /tmp > /dev/da0s1f 268217320 5514844 241245092 2% /usr > /dev/da0s1d 4298926 187570 3767442 5% /var > > Notice the the increase in the root partition. Should I have made this partition bigger when I first installed? Is there any cleaning up I can do after version upgrades? I would've thought /usr would be the one that grew more, but then again my /usr partition is fairly sizeable. Does 7.0 just take up a lot more of the root partition than 6.2?7.0 installs debugging symbols for the kernel and modules by default. You can avoid that by defining INSTALL_NODEBUG during installkernel. If already installed, you can delete the symbol files without causing problems as long as you don't need to debug the kernel. Also, when you install a new kernel, the old kernel is saved as kernel.old so you now have 2 kernels in /boot instead of one. If you're positive the new kernel works fine, the old kernel can be removed as that's only used to recover from a new kernel with problems. But, your space really isn't that close to the limit, IMO. You appear to have enough space to have an old and new kernel installed both with symbols, so I'd leave it as is in case you need to debug something or boot the old kernel. You can always take care of it later if you're about to run out of space. Why do today what you can put off 'til tomorrow? Also, consider reading UPDATING before every upgrade. The entry for 20060118 covers this issue. -- Skip
Gavin Spomer
2008-Jun-09 18:33 UTC
6.2-STABLE => 7.0-STABLE Upgrade root partition more full
>>> Skip Ford <skip@menantico.com> 06/06/08 1:39 PM >>>Gavin Spomer wrote:> I successfully did my first FreeBSD upgrade yesterday after looking at the manual, and cross referencing with Googling and getting help from our network engineer here at CWU. Before the upgrade, running df showed: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 77662 389358 17% / > devfs 1 1 0 100% /dev > /dev/da0s1e 507630 588 466432 0% /tmp > /dev/da0s1f 268217320 4866120 241893816 2% /usr > /dev/da0s1d 4298926 162066 3792946 4% /var > > Now it shows: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 184834 282186 40% / > devfs 1 1 0 100% /dev > /dev/da0s1e 507630 426 466594 0% /tmp > /dev/da0s1f 268217320 5514844 241245092 2% /usr > /dev/da0s1d 4298926 187570 3767442 5% /var > > Notice the the increase in the root partition. Should I have made this partition bigger when I first installed? Is there any cleaning up I can do after version upgrades? I would've thought /usr would be the one that grew more, but then again my /usr partition is fairly sizeable. Does 7.0 just take up a lot more of the root partition than 6.2?7.0 installs debugging symbols for the kernel and modules by default. You can avoid that by defining INSTALL_NODEBUG during installkernel. If already installed, you can delete the symbol files without causing problems as long as you don't need to debug the kernel. Also, when you install a new kernel, the old kernel is saved as kernel.old so you now have 2 kernels in /boot instead of one. If you're positive the new kernel works fine, the old kernel can be removed as that's only used to recover from a new kernel with problems. But, your space really isn't that close to the limit, IMO. You appear to have enough space to have an old and new kernel installed both with symbols, so I'd leave it as is in case you need to debug something or boot the old kernel. You can always take care of it later if you're about to run out of space. Why do today what you can put off 'til tomorrow? Also, consider reading UPDATING before every upgrade. The entry for 20060118 covers this issue. -- Skip Thanks a bunch for the info, it is helpful. Also, sorry for the lateness of my reply. Any suggestions for selectively reading UPDATING? It IS a rather long file. I'd rather be reading a good R.A. Salvatore novel if I'm going to read for that long. ;) Thanks for you reply as well, Clifton. - Gavin