Hi Eric,
I'm actually getting similar errors. Here's an
overview of what I did (loading ramdisk to the
Assabet)and the errors I got:
1. Recompiled the kernel to allow the ramdisk to be
greater than 4MB. Set it to 10MB instead.
2. dd if=/dev/zero of=/dev/ram bs=1k count=10240
3. mke2fs -vm0 /dev/ram 10240
4. mount -o loop -t ext2 ramdisk /mnt/new-ramdisk
5. mount -o loop -t ext2 ramdisk_old /mnt/old-ramdisk
6. copied all stuff from the old-ramdisk directory to
the new-ramdisk directory
7. umount /mnt/new-ramdisk
8. cat ramdisk | gzip -v9 > ramdisk.gz
However, after downloading the ramdisk to the Assabet
using angelboot, I got the following error messages
upon starting Minicom.
...
...
VFS: Mounted root (ext2 filesystem)
Freeing init memory: 64K
attempt to access beyond end of device
01:00: rw=0, want=8205, limit=8192
EXT2-fs error (device ramdisk(1,0)): ext2_read_inode:
unable to read inode block - inode=1324, block=8204
attempt to access beyond end of device
01:00: rw=0, want=8220, limit=8192
EXT2-fs error (device ramdisk(1,0)): ext2_read_inode:
unable to read inode block - inode=1461, block=8192
INIT: version 2.74 booting
INIT: No inittab file found INIT: Can't open
(/etc/ioctl.save, O_WRONGLY): Input/output error
...
...
Here's the angelboot configuration i'm using:
base 0xc0008000
entry 0xc0008000
r0 0x00000000
r1 0x00000019
device /dev/ttyS0
options "9600 8N1"
baud 115200
otherfile ramdisk.gz
otherbase 0xc0800000
You said that the ramdisk driver is limited to 8MB but
I recompiled the kernel to allow 10MB. If it did allow
only 8MB then I wouldn't be able to execute the
following statement successfully isn't it?
dd if=/dev/zero of=/dev/ram bs=1k count=10240
I just found some info from
http://www.tux.org/lkml/#ss2. Just wondering if it's
got anything to do with what's mentioned below:
"What is the maximum file size/filesystem size?
(REG) Maximum file size depends on the block size on
your filesystem. For ext2 (and UFS, SysVFS and similar
filesystems), the limits are:
Block size Maximum file size (GiBytes)
512 B 2
1 kiB 16
2 kiB 128
4 kiB 1024
8 kiB 8192 (PAGE_SIZE must be >= 8 kiB)
plus a small amount. The limitation is due to the
classic triply-indirect addressing scheme. In the
future, ext2 will have extent-based addressing, which
will overcome this problem.
The limit for a single filesystem (partition) on a 32
bit CPU is 4 Gi blocks. Each block is 512 Bytes, so
that works out to 2 TiB. For 64 bit CPUs, the limits
are bigger than you can imagine."
I used to ext2fs with a block size of 1kB...so that
would mean I should be able to create a file with a
maximum size of 16GB!! hmmmm....so what IS going on
here? :)
Regards,
Supriyo
--- Eric Jorgensen <[EMAIL PROTECTED]> wrote: >
Sounds like the ramdisk driver is limited to 8 meg
> ramdisks. See the
> kernel configuration (under block devices) for more
> details.
>
> - Eric
>
> #YANG XIAOYONG# wrote:
> >
> > Hi,
> > Thanks for your suggestion.
> > I have created a 10 MB ramdisk. But when I load it
> to the Assabet. Some
> > error came out after I execute minicom" Enter
> runlevel:" I tried 2. Then"
> > INIT: can't open (/etc/ioct1.save, O_ WORNGLY):
> Input/ouput error INIT:
> > Entering runlevel:2 INIt nomore proceeses left in
> this runlevel attempt to
> > access beyond end of device 01:00: rw= 0 want 8205
> limit= 8192
> > EXT@-fs error ( device
> ramdisk(1,0)):ext2_write_inode:unable o read inode
> > blo4
> > attempt to access beyond end of device 01:00: rw=
> 0 want 8235 limit= 8192
> > EXT@-fs error ( device
> ramdisk(1,0)):ext2_write_inode:unable o read inode
> > blo4"
> > Can you please give me some more suggestion?
> > For Assabet should I make the ramdisk into certian
> special format?
> > Is it because of my angelboot configuration?
> > Here is my setting:
> > base 0xc0008000
> > entry 0xc0008000
> > r0 0x00000000
> > r1 0x00000019
> > device /dev/ttyS0
> > options "9600 8N1"
> > baud 115200
> > otherfile ramdisk_img.gz
> > otherbase 0xc0800000
> > Regards,
> > Xiaoyong
> >
> > _______________________________________________
> >
>
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
> > Please visit the above address for information on
> this list.
>
> _______________________________________________
>
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
> Please visit the above address for information on
> this list.
__________________________________________________
Do You Yahoo!?
Yahoo! Mail � Free email you can access from anywhere!
http://mail.yahoo.com.sg/
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
