kernel ln 2.6.11-1.1286 hoses the filesystem.

[philippo]

Hi,

I just installed FC4 yesterday - it worked fine until I updated the system (blech, no apt) and got the new kernel (2.6.11-1.1286). The next reboot the volume group was read-only and the system promptly crashed on login! Subsiquent reboots required a manual fsck (which crashed on first run) to get the disk into a workable state.

I booted into 1226 and it worked fine again, so I gave 1286 another try - same result. 1286 is gone.

I've got a thinkpad t40 (intel 1.5ghz x86). anybody else had that problem?

[davidbrohall]

yes,
my problem was that I uninstalled the other versions because my 300MB /boot was full. So I made a complete reinstallation... this time in x86_64 istead of i386.

[brisray]

How many other versions did you have loaded? According to Sytem Properties my /boot is 13.6 Mb used, 74.4Mb free. System Monitor shows 19.2Mb used, 79.5Mb free.

du -a -k -c --total in Terminal shows 14055 kb used.

I let Linux format the drive when I first loaded 1226. I've downloaded 1286 which went without problems and 1287 works OK too.

uname -a says the system is i696 Athlon i386

The PC uses a 1.4GHz AMD processor with 256Mb of memory.

Ray

[davidbrohall]

I had about 40-50 versions of kernel loaded on /boot (cron.daily yum)

=)

[davidbrohall]

40-50 version with both kernel and kernel-smp, which makes 80-100...

[AndyGreen]

rpmlibs have some ancient bugs which makes them act very slowly with a large number of versions of the same large package. I dread to think how long an rpm -e on one of those kernel versions will take... maybe hours.