It is more a limitation of the 32 bit chipset rather than a limitation of the filesystem. 64 bit systems don't have this problem and a journaling filesystem won't fix the problem. It was a design choice when the filesystem was designed, disks were small and 64 bit systems were on the horizon. I think thatIntel has done some fancy design work on the Xeons so that that have 36 bit registers that are used for addressing but it is basically a kludge( needs a nonstandard approach for just that platform ). The software kludge is to create an extra layer in the filesystem ( read slower ) design. There are patches round that do fix this problem but the reason why it has not been incorporated into the mainstream kernel is that it is bad (read nonstandard ) design. If you are addressing files of this size I would look very seriously at a 64 bit system simply for performance reasons. Ethan Fremen wrote:

Pavlos Christoforou wrote:

...

On Sat, 13 Nov 1999, Alexander Limi wrote:

...

Does anybody know if this is a limitation of the kernel or the FS? And is it going to be fixed in the foreseeable future?

It is a limitation of the FS, and it will be fixed but I do not know when.

The next edition of Red Hat Linux will include a journaling filesystem- i believe this is the one from SGI- which allows files in the petabytes...

-- Ethan "mindlace" Fremen you cannot abdicate responsibility for your ideology.

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )