> Using file systems with more than 2^16-1 (65535) inodes. For a
> default ext2 file system this means that tomsrtbt will not build on
> partitions of greater than 268,435,456 bytes.
My guess is that it also requires some happenstance with the high 16 bits
of the inode. I've certainly always built it on a 1-gig ext2fs partition.
I am only seeing failures on a 4-gig partition. I can confirm the
problems on an ext2fs loop filesystem. What really suprised me, is that I
get 4 sectors free when I build under a minix loop filesystem. I had 2
free under the 1-gig ext2fs filesystem, when I built there, which means
that some calculation is filesystem-affected, probably in 'du' in
buildit.s or something. I will have to review the whole thing, maybe
there are 2 problems: (1) inode handling in pax (for >16 bit inodes, it
shouldn't be able to _store_ the inode, as the cpio format only supports
16, but it _should_ be able to correctly truncate it so that it works...),
and, (2) free space calculations on ext2fs filesystems. ?? maybe they are
the same problem?? I'll start by looking at pax, after all, it is more
critical to get pax working completely than anything else as that also
affects backup and restoring... -Tom
