Ah, that would explain why the / filesystem is filling up quickly. Would the sizing from the cookbook support the upgrade processes? I expect the sizing was created for a fresh install. It might be the disk is too small to hold the required files during the upgrade. Some 300M would be enough to hold a required data for a Linux system but during an upgrade more space is needed.
I don't know if files in /lib are used during boot. If so then the boot will fail. If not then the directory might be eligible to be moved into its own minidisk. I have never tried that. Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Ram Jam Sent: Monday, January 25, 2016 4:44 PM To: [email protected] Subject: Re: Expand root filesystem, SLES 11 Looks like /lib/modules is pretty large compared to other subdirectories. Do you all think giving /lib its own filesystem would be a good idea? Forgot to mention. I'm testing an upgrade to SLES 12 and I received an error about the / filling up. This prompted the search into expanding /. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
