file system larger than partition in pre-built omap4 image

[scott douglass]

Hi,

I was looking at a recent, pre-built Pandaboard image <http://cdimage.ubuntu.com/ubuntu-netbook/daily-preinstalled/current/natty-preinstalled-netbook-armel+omap4.img.gz> (retrieved on 11 Feb 2011).

It has two partitions that don't quite fill the image file:

# gunzip natty-preinstalled-netbook-armel+omap4.img.gz
# sfdisk -uS -l natty-preinstalled-netbook-armel+omap4.img
Disk natty-preinstalled-netbook-armel+omap4.img: cannot get geometry

Disk natty-preinstalled-netbook-armel+omap4.img: 247 cylinders, 255 heads, 63 sectors/track
Units = sectors of 512 bytes, counting from 0

   Device Boot Start End #sectors Id System
natty-preinstalled-netbook-armel+omap4.img1 * 63 144584 144522 c W95 FAT32 (LBA)
natty-preinstalled-netbook-armel+omap4.img2 144585 3968054 3823470 83 Linux
natty-preinstalled-netbook-armel+omap4.img3 0 - 0 0 Empty
natty-preinstalled-netbook-armel+omap4.img4 0 - 0 0 Empty
# echo $((3823470 * 512))
1957616640

The second partition size is 3823470 sectors (1957616640 bytes), but it contains a ext3 filesystem that is larger than the partition (479269*4096 = 1963085824 bytes):

# losetup --show --find --offset $((144585*512)) --sizelimit $((3823470*512)) natty-preinstalled-netbook-armel+omap4.img
/dev/loop0

# e2fsck /dev/loop0
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 479269 blocks
The physical size of the device is 477933 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? y
yes
# tune2fs -l /dev/loop0
...
Block count: 479269
...
Block size: 4096
...
# echo $((479269 * 4096))
1963085824

Is this the right place to file a bug report about this?

[
Fortunately the filesystem does end before the end of the image file:
# ls -l natty-preinstalled-netbook-armel+omap4.img
-rw-r--r-- 1 xxxxxxxx xxxxxxxx 2038583296 2011-02-11 12:44 natty-preinstalled-netbook-armel+omap4.img
# echo $((144585*512 + 1963085824))
2037113344

And e2fsck is happy if I leave out the --sizelimit. But the --sizelimit is valid.
]

[Oliver Grawert (ogra)]

this should not cause any problems, given that the whole partition table is wiped and recreated with proper settings for the SD card on first boot of the image (during the expansion phase of the second partiton from initramfs)
indeed it is ugly and should be fixed but it wont harm functionallity.