Greetings,

A few minutes ago, I upgraded a development server to 2.6.15 (final release), from 2.6.14. My upgrade path was the same as previous kernel upgrades:

1. run a make oldconfig based on the 2.6.14 .config file.
2. run make menuconfig to make sure nothing major had changed.
3. run make, make install.
4. move my bzImage into /boot with a unique name, modify lilo.conf to boot off of the new image, and reboot.

I do not use modules - everything is compiled into the kernel.

Upon boot, I found that all partitions are the same size now:

for instance:

/dev/sda2              3789240   3508436     85216  98% /
/dev/sda3              3789240   3508436     85216  98% /bin

... and so on. Any partition that had been larger than this before is still present as a mount point, but is now empty. Parititions that were smaller than this limit are present (although incorrectly reported by tools like df).

I booted back onto 2.6.14, but the paritition issue remains. Has something changed in 2.6.15 to cause this behaviour?

Thank you.

The machine is running Slackware 9.