On 2017-04-07 22:03, Marc Chamberlin wrote:
Well this is one of those times I wish software designers would have followed the KISS principal, and design the Linux system in a way that is easily understandable, sigh... A recent set of updates broke, on one of my OpenSuSE Leap 42.2 x64 servers because of lack of disk space in the partition for the root partition for /. My investigations showed that the contents of /usr was taking up the lion's share of space (8GB) of the partition on which / is mounted, which only had 10GB of total space allocated to it.
My /usr contains 32 GB of files.
In other words, the /usr directory was not mounted in a separate partition, it was just a sub directory. So I thought the solution would be to simply create a separate partition on another disk drive, copy everything from /usr to the new partition, edit fstab to mount the new partition as /usr, rename the old /usr directory to something different like /usr_tmp, reboot and then delete the old /usr_tmp directory if everything worked OK,
Delete after rebooting, not before.
to get more space for /. Easy as pie right? WRONG! Things went badly haywire when I tried to reboot! Apparently something within the boot loader or early in the boot process/system startup phase (which I admit I poorly understand) is referencing /usr and got very unhappy about my attempt to move /usr to it's own partition. So much for the KISS principal...
Once the change is activated (fstab), you need to run mkinitrd to change the boot ramdisk. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)