Vicidial /boot partion is 100 % full

[deansys]

I have a Vicidial installation that is running on a centos box. the server usually hangs once or twice each day and has to be rebooted.
I have noticed that the /boot partion is full that is the partiotion is 100% full , as can be seen from the below info.

Filesystem Size Used Avail Use% Mounted on
/dev/hdb2 225G 69G 145G 33% /
/dev/hdb1 10M 10M 0 100% /boot
tmpfs 996M 0 996M 0% /dev/shm

I am thinking of resizing and encreasing the partion . would this improve my server's perfoirmance.
and can any of you share any tips or steps to follow to achieve this


regards

Eric

[steffen123]

I don't know Vicidial well at all yet, but I do have a fairly good level on Linux, and I really can't see any way in which /boot being full could affect performance. The "only" problems from that that I can see would be boot problems and/or problems related to updating the kernel. Ofc those can be big problems. As for how to do it, parted magic (not to be mistaken for partition magic, which used to be good but IMHO has become rather bad) is a good tool. Well I was going to give you the link but the forum decided that it's spam to post offsite links...

[williamconley]

any partition 100% full is a bad thing. find out what is on it and delete something ... or enlarge the partition to a larger number. also seriously consider a stock installation which would have made that decision for you.

since you are a newbie ... here are your newbie suggestions!

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

[gardo]

Increasing your /boot partition is highly recommended. Though this really doesn't have any effect on your system performance. Only kernel images and grub/lilo files are stored in /boot. If your /boot is 100% full you won't be able to upgrade your kernel. Try increasing it to 100MB to be safe. That's the default size set by most Linux distribution installers.

[deansys]

thank you all for the suggestions and pointers so far . this is a production server . and the /boot partition that is 100 % full has kernel images .i would like to minimize down time when doing the partition resizing .
can any of you guys provide me with links / tutorials or steps to follow.
i have been reading and noticed that parted might be able to do the resizing .

regards


Eric

[deansys]

I have managed to free up about 26 % of the /boot partition and it now shows that it has only used 76 % used.