Since you are using LVM, the lvextend and lgextend commands may be of use.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Stuart J. Newman Engineer 4; Systems Solar Dynamics Observatory (SDO) Honeywell Technology Solutions Inc NASA/Goddard Space Flight Center Building 14, Room E222 Mail Stop 428.2 Greenbelt, MD 20771 Office: (301) 286-5145 EMail: [email protected] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please notify the sender at once, and you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bob Cochran Sent: Monday, July 02, 2012 20:19 To: [email protected] Subject: Re: [cobbler] Persistent crashes in 'cobbler reposync' On 7/2/12 8:02 PM, James Cammarata wrote: > On Mon, Jul 2, 2012 at 6:45 PM, Bob Cochran<[email protected]> wrote: >> I now think that 'cobbler reposync' has bugs, at least in the github >> version of the code. >> >> Consider these messages which appear in /var/log/messages: >> >> >> Jul 2 14:01:41 cobbler1 python: abrt: detected unhandled Python >> exception in /usr/bin/yum Jul 2 14:01:41 cobbler1 abrtd: New client >> connected Jul 2 14:01:41 cobbler1 abrt-server[1851]: Can't create >> directory >> '/var/spool/abrt/pyhook-2012-07-02-14:01:41-1823.new': No space left >> on device Jul 2 14:01:41 cobbler1 abrt-server[1851]: Error creating >> crash dump /var/spool/abrt/pyhook-2012-07-02-14:01:41-1823.new >> >> [not sure if the above are meaningful to this problem, however I >> started my 'cobbler reposync' at about this time] > No, that has nothing to do with cobbler. The abrt daemon is logging > crash dumps, but /var is probably full so it's reporting it. That > could probably be the same issue you're having with reposync, since > everything goes to /var/www/cobbler. Oh! I understand now. /var on my box is indeed full. I guess I need to look for some way to resize var upwards. Maybe gparted understands how to work with LVM. If not, then I guess I need to reinstall CentOS 6.2 but modify the partition layout, and start again. I have no problem giving /var a lot of space. I will see what I can do... Bob _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
