On Mon, Jun 26, 2006 at 01:44:52PM -0500, khym@azeotrope.org wrote:
> On Mon, Jun 26, 2006 at 01:37:03PM -0500, khym@azeotrope.org wrote:
> >      permits files over 4GB, and its 18-bit limit for most other fields makes
> >      it unsuitable for modern systems.
> 
> BTW, 18 bits gives a max of 262143... and apparently, the inode number is
> something that gets stored in the header. So does ls -li of the problem
> file show an inode number of 262144 or greater?

Whatever is happening, I don't think it is due to large inode numbers.

For example:

sanctum $ touch foo
sanctum $ ls -li foo
4972109 -rw-rw-r--  1 ben  users  0 Jun 26 12:00 foo
sanctum $ pax -w -x cpio -f foo.cpio foo
sanctum $ pax -f foo.cpio
foo

Cheers,

Ben