Installing: kernel-source-3.1.10-1.13.1 [error]
Installation of kernel-source-3.1.10-1.13.1 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: installing package kernel-source-3.1.10-1.13.1.noarch needs 57MB on the / filesystem
No known reason what caused this error.
Skipped over this package, continued to install the remaining packages scheduled for updating without problem.
So far, no runtime issues (I wouldn’t expect since it’s only the kernel source package), but of course I’m concerned for down the road if I install another package that requires kernel modification.
After updating all that could be updated, re-ran zypper up to try to catch this package, but failed with same error.
Available free space on the boot/root partition is slightly less than 500mb.
On 06/24/2012 02:06 PM, tsu2 wrote:
>
> openSUSE 12.1
> running zypper up
>
>
> Code:
> --------------------
>
> Installing: kernel-source-3.1.10-1.13.1 [error]
> Installation of kernel-source-3.1.10-1.13.1 failed:
> (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: installing package kernel-source-3.1.10-1.13.1.noarch needs 57MB on the / filesystem
>
> --------------------
>
>
> No known reason what caused this error.
> Skipped over this package, continued to install the remaining packages
> scheduled for updating without problem.
> So far, no runtime issues (I wouldn’t expect since it’s only the kernel
> source package), but of course I’m concerned for down the road if I
> install another package that requires kernel modification.
>
> After updating all that could be updated, re-ran zypper up to try to
> catch this package, but failed with same error.
>
> Available free space on the boot/root partition is slightly less than
> 500mb.
You do realize that 500 millibits is not much space. In addition, I have no
idea what you mean by the boot/root partition. Do you mean /?
Thx.
Hmmmm… I’d always glazed over the “Millibytes” as a non-critical bug since it didn’t make sense to me and likely really meant “megabytes.” But, maybe not.
Will look at this further, I’ve tried to free up space by removing applications and one of the older kernels on this multi-kernel system, but so far despite expecting to recover megabytes of space am only seeing millibytes of space recovered.
On 06/25/2012 04:06 PM, tsu2 wrote:
>
> Thx.
> Hmmmm… I’d always glazed over the “Millibytes” as a non-critical bug
> since it didn’t make sense to me and likely really meant “megabytes.”
> But, maybe not.
>
> Will look at this further, I’ve tried to free up space by removing
> applications and one of the older kernels on this multi-kernel system,
> but so far despite expecting to recover megabytes of space am only
> seeing millibytes of space recovered.
To me, mb is millibits!
Where is the output of df? If you really want help, then you NEED to supply
the requested info.
Issues seems to have automatically resolved itself with a reboot.
After I rebooted, I re-ran zypper up and not seeing anything, I inspected installed RPMs and verified the problem RPM was installed.
So,
Despite the error text, I suspect the problem had more to do with heap resource exhaustion or more specifically memory resources in general rather than anything to do with disk space.
I dug around further wherever openSUSE/KDE reports disk usage and I remain convinced that “MiB” or anything similar refers to “megabytes” and not “millibytes.” Adding and removing hundreds of megabytes of files changes the number of, but not the unit measure.
On 06/26/2012 04:46 PM, tsu2 wrote:
>
> Issues seems to have automatically resolved itself with a reboot.
> After I rebooted, I re-ran zypper up and not seeing anything, I
> inspected installed RPMs and verified the problem RPM was installed.
>
> So,
> 1. Despite the error text, I suspect the problem had more to do with
> heap resource exhaustion or more specifically memory resources in
> general rather than anything to do with disk space.
> 2. I dug around further wherever openSUSE/KDE reports disk usage and I
> remain convinced that “MiB” or anything similar refers to “megabytes”
> and not “millibytes.” Adding and removing hundreds of megabytes of files
> changes the number of, but not the unit measure.
Yes, upper-case M refers to Mega, and upper-case B refers to bytes; however,
lower-case m means milli and lower-case b means bits. In your original post, you
wrote mb! You do the math.
On 2012-06-27 00:02, Larry Finger wrote:
> On 06/26/2012 04:46 PM, tsu2 wrote:
>> So,
>> 1. Despite the error text, I suspect the problem had more to do with
>> heap resource exhaustion or more specifically memory resources in
>> general rather than anything to do with disk space.
No, the error message would have said so.
>> 2. I dug around further wherever openSUSE/KDE reports disk usage and I
>> remain convinced that “MiB” or anything similar refers to “megabytes”
>> and not “millibytes.” Adding and removing hundreds of megabytes of files
>> changes the number of, but not the unit measure.
>
> Yes, upper-case M refers to Mega, and upper-case B refers to bytes;
> however, lower-case m means milli and lower-case b means bits. In your
> original post, you wrote mb! You do the math.
And MiB is Mibibytes, 2^20 bytes. Mib is Mibibits, 2^20 bits. The letters
and their case have their importance.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 06/26/2012 11:46 PM, tsu2 wrote:
> Issues seems to have automatically resolved itself with a reboot.
i suspect that you previously took steps to clean out your /tmp during
each reboot…and, that /tmp was full of kernel source and other stuff
before the reboot…causing the out of space error “needs 57MB”…
you can confirm whether or not /tmp is routinely cleaned on boot with:
sudo cat /var/log/messages | grep tmp
if cleaning, there will be a line like this, for every boot:
Jun 26 11:31:39 linux-os114 run-crons[7098]: suse.de-clean-tmp: OK