Re: ext2fs or ramdisk problems......

[greyham@research.canon.com.au (Graham Stoney)]

Whitney, John writes:
> I have had odd results using ext2 on the ramdisk (in my case, a 16MB
> ramdisk).  Using the 2.2.13, ramdisks I created using ext2 would boot
> up just fine on the system, but after use the filesystem would declare
> that it was out of space, even though "df" showed several megabytes
> free on that filesystem.

Scott's suggestion re: inodes sounds like the explanation here.
Unfortunately the error message you get for being out of inodes is the same
as what you get for running out of available blocks.

> Someday I'll go into the Minix source code on my PC and modify it to be
> big-endian, so I don't have to worry about it anymore.

This would be a really worthwhile enhancement.  I'm a little suprised noone's
bothered to fix this, given that ext2 gets it right.  It should be possible
to auto-detect the byte order it was constructed with and have it "just work"
on either architecture, even if mkfs.minix continues to write the fields in
the native byte order.

Regards,
Graham
--
Graham Stoney
Principal Hardware/Software Engineer
Canon Information Systems Research Australia
Ph: +61 2 9805 2909  Fax: +61 2 9805 2929

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/