This sounds like you changed the block size used by mke2fs to create the file system on the initrd, and not the number of blocks to create. A long, long time ago, I discovered that the block size used must be 1024 for an initrd, and nothing else. Alan Cox confirmed the problem, but because it was in a touchy area of code, didn't think it was worth fixing.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Stewart Sent: Friday, March 31, 2006 9:05 AM To: [email protected] Subject: Re: Mkinitrd problem Thanks Hannes. That seems to change the number of times it runs out of space, but I cannot get it to a number that works. If I go to high, I get this error: mount: wrong fs type, bad option, bad superblock on /dev/loop1, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) failed to mount image rmdir: `/var/tmp/mkinitrd.i18473': Directory not empty If I go to low than I get the other errors, although the number does change. Also, it used to work fine and it does fine in my other images the way it is. I am wondering if there is something else that got messed up that affects the same thing. I'll keep trying things. Thanks again, Ryan ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
