dpkg: dependency problems

[ian-weisser]

When looking at "No space left on device" errors,
in addition to df for looking at space,
remember to also check df -i for looking at inodes.
Check both.

mapper and multiple kernels both use a lot of inodes, and there a *lot* of threads in this forum where "No space left" referred to inodes instead of disk space.

[LHammonds]

I don't mess with repo stuff. What is set is set by default.

This particular server is running MySQL and I have documented every step of its setup in my signature. Shouldn't be anything quirky going on that I know of.

Maybe the Quantal kernel got there because of my upgrade script which is designed to just get security updates using the following command:

aptitude safe-upgrade --assume-yes --target-release `lsb_release -cs`-security

The only time I have ever added a 3rd-party repo was a Minecraft server in order to get Oracle Java installed and updated on a normal basis.

I edited /etc/apt/sources.list and removed "us." from all entries on the MySQL server. Then did "aptitude update" and then "aptitude safe-upgrade" and it worked without error! Just as if there was nothing wrong. Didn't even need to do the fix command. Wow.

I was then able to do the "apt-get remove linux-image-3.5.0-44-generic" command without any errors and cleaned up all the old boot images (I always keep the latest two)

Being the curious sort, I then checked the Bugzilla server that was having the similar issue. I verified that it still had the issue by trying to remove an old kernel and it spit out the error I expected. I then did the "aptitude update" and "aptitude safe-upgrade" and was greeted with the familiar "quantal depends on quantal" error. At this point, I then edited the sources.list file and removed "us.", ran "aptitude update" and "aptitude safe-upgrade" but it did not fix the issue. The "apt-get install -f" also did not resolve the issue.

Still not sure what's going on but my plan of action will not change...still going to setup all new 14.04 servers and move over the data.

When looking at "No space left on device" errors,
in addition to df for looking at space,
remember to also check df -i for looking at inodes.
Check both.

mapper and multiple kernels both use a lot of inodes, and there a *lot* of threads in this forum where "No space left" referred to inodes instead of disk space.

True but the issue was resolved by increasing the volume and file system. The packages take up a lot of room in /usr during installation so it needs a lot of breathing room to operate. When I create my 14.04 install documents, I will setup /usr to have 1GB more than I have in the past.

Filesystem           Inodes  IUsed  IFree IUse% Mounted on
/dev/mapper/LVG-root 121920  12369 109551   11% /
udev                  60471    514  59957    1% /dev
tmpfs                 62877    464  62413    1% /run
none                  62877      8  62869    1% /run/lock
none                  62877      1  62876    1% /run/shm
/dev/sda1            146016    236 145780    1% /boot
/dev/mapper/LVG-home  48192     18  48174    1% /home
/dev/mapper/LVG-tmp  121920     24 121896    1% /tmp
/dev/mapper/LVG-usr  195072 166503  28569   86% /usr
/dev/mapper/LVG-var  121920   3245 118675    3% /var
/dev/mapper/LVG-srv   48192     13  48179    1% /srv
/dev/mapper/LVG-opt  257024    886 256138    1% /opt
/dev/mapper/LVG-bak  520192    552 519640    1% /bak

LHammonds