cramfs as initrd still fails in 2.4.27-pre2 [PATCH]
Hi!
I've been trying to use the cramfs to hold my initrd images and it works ok in 2.6.6, but when testing it in 2.4.26 or 2.4.27rc2 I get this problem:
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 2128 blocks [1 disk] into ram disk... done. Freeing initrd memory: 2128k freed
cramfs: wrong magic
In Debian official kernel packages cramfs is being used as the initrd, so I had a look at Debian's kernel patches and extracted this one that makes initrd work for me in 2.4.26 and 2.4.27-pre2:
fs/block_dev.c +1 -1
@@ -95,7 +95,7 @@sync_buffers (dev,2 ); blksize_size[MAJOR (dev)][MINOR (dev)] = size; bdev->bd_inode->i_blkbits =blksize_bits (size); -kill_bdev (bdev); +invalidate_bdev (bdev,1 );bdput (bdev);return 0 ; }
I think this patch or some other fix should be applied.
Regards...
Signature · 1 line
Manty/BestiaTester -> http://manty.net
Quoted 3 lines · Santiago Garcia Mantinan
In Debian official kernel packages cramfs is being used as the initrd, so I had a look at Debian's kernel patches and extracted this one that makes initrd work for me in 2.4.26 and 2.4.27-pre2:
Patch in debian kernel package is a mindless crap. cramfs has no business messing with block size (or buffer cache in general, to start with). 2.6 has it fixed the right way, there's a backport to 2.4 and IIRC it was scheduled for inclusion.
Quoted 9 lines · Santiago Garcia Mantinan
Hi!
I've been trying to use the cramfs to hold my initrd images and it works ok in 2.6.6, but when testing it in 2.4.26 or 2.4.27rc2 I get this problem:
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 2128 blocks [1 disk] into ram disk... done. Freeing initrd memory: 2128k freed
cramfs: wrong magic
I just put ramdisk_blocksize=4096 on my kernel command line for kernel.org linux (debian's linux seems to work as is).
It would be nice if 2.4 didn't need that though.
Signature · 4 lines
Jeremy Jackson Coplanar Networks (519)897-1516 http://www.coplanar.net