Public bug reported:

I installed Kubuntu 7.04 »Feisty Fawn« using the Alternate Install CD
since I needed the RAID capabilities provided by it. The machine I
installed has two 80GiB SATA drives. Since I use XFS for /, I needed a
separate /boot-partition because GRUB cannot read XFS file systems.

The partition tables are as follows:


Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          16      128488+  fd  Linux raid autodetect
/dev/sda2              17         138      979965   82  Linux swap / Solaris
/dev/sda3             139        9729    77039707+  fd  Linux raid autodetect

Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1          16      128488+  fd  Linux raid autodetect
/dev/sdb2              17         138      979965   82  Linux swap / Solaris
/dev/sdb3             139        9729    77039707+  fd  Linux raid autodetect

I created two RAID devices: md0 (/dev/sda1 and /dev/sdb1 mirrored) and
md1 (/dev/sda3 and /dev/sdb3 mirrored). md1 is for / and md0 is for
/boot. I choose ext2 for /boot and XFS for /. Installation of Kubuntu
went fine.

Two days ago I tried to update the kernel to the newest version offered
by the repository. I persistently got the following error:

dpkg: error processing 
/var/cache/apt/archives/linux-image-2.6.20-16-generic_2.6.20-16.29_i386.deb 
(--unpack):
 unable to create `./boot/vmlinuz-2.6.20-16-generic': No space left on device

This is very odd because there is *lots* of free space on the
partitions:

[EMAIL PROTECTED]:~$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md1              147G  2.0G  145G   2% /
varrun                506M  104K  506M   1% /var/run
varlock               506M     0  506M   0% /var/lock
procbususb            506M  108K  506M   1% /proc/bus/usb
udev                  506M  108K  506M   1% /dev
devshm                506M     0  506M   0% /dev/shm
lrm                   506M   33M  473M   7% 
/lib/modules/2.6.20-15-generic/volatile
/dev/md0              126M   16M  109M  13% /boot

The solution is quite simple: partman created the ext2 file system on
/dev/md0 with only 32 inodes:

[EMAIL PROTECTED]:/$ sudo e2fsck /dev/md0
e2fsck 1.40-WIP (14-Nov-2006)
boot: clean, 32/32 files, 4109/32096 blocks

This means that this partition can only hold 32 files (directories,
links, ...) which is obviously not enough to have grub and more than one
kernel on this partition.

I think this behavior of partman is quite odd and should be corrected.

To add some more oddness, this error(?) occurred on two machines with an
identical hardware-setup and partition scheme, while a third machine
with the same hardware and identical partition scheme had no problems
upgrading to the new kernel; on this machine, the /boot partition was
created with more inodes.

Please have a look at http://ubuntuforums.org/showthread.php?t=484030
where I originally posted the problem and its solution. Please do not
hesitate to contact me if you need any more information.

** Affects: partman (Ubuntu)
     Importance: Undecided
         Status: New

-- 
The alternate install CD creates a /boot partition with only 32 inodes
https://bugs.launchpad.net/bugs/122563
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to