[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#445510: marked as done (initramfs-tools: please fail gracefully for ENOSPC)

Your message dated Sat, 5 Jan 2008 17:15:49 +0100
with message-id <20080105161549.GF17624@stro.at>
and subject line Bug#445510: initramfs-tools: please fail gracefully for ENOSPC
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: initramfs-tools
Version: 0.85h
Severity: wishlist

I recently set up a system with /boot being too small. While this is my
fault update-initramfs could handle this in a better way than backup the
old (working) initramfs and leave a truncated one for the next reboot
will fail. (Yes, it told me that my initramfs was broken afterwards!)

(According to my understanding of the scripts the bug also applies to
0.91b.)

I therefore suggest not creating the new initramfs directly, but create
a new file with a different name and then in the last step rename the
stuff if and only if no error occurred. By doing so the system will more
often be in a bootable state. Furthermore this will prevent making a
system unbootable by suspending the machine while updating the initramfs
(a DD reported this on planet.d.o).

Helmut

[extra info wiped as this bug occurred on a different system]

--- End Message ---
--- Begin Message --- 
Version: 0.86

On Sat, 06 Oct 2007, Helmut Grohne wrote:

> I recently set up a system with /boot being too small. While this is my
> fault update-initramfs could handle this in a better way than backup the
> old (working) initramfs and leave a truncated one for the next reboot
> will fail. (Yes, it told me that my initramfs was broken afterwards!)
> 
> (According to my understanding of the scripts the bug also applies to
> 0.91b.)
> 
> I therefore suggest not creating the new initramfs directly, but create
> a new file with a different name and then in the last step rename the
> stuff if and only if no error occurred. By doing so the system will more
> often be in a bootable state. Furthermore this will prevent making a
> system unbootable by suspending the machine while updating the initramfs
> (a DD reported this on planet.d.o).

newer update-initramfs restores the backup if the initramfs creation
failed due to not enough space.

christian perrier had a bad experience that was shared on planet.d.o
back in the times when we didn't even created a backup initramfs.


closing with appropriate versioning info.

happy hacking

-- 
maks

--- End Message ---
Reply to: