Some googling gave me this which is the opposite from what Steve and I
thought
<Quote>
The issue almost certainly lies with the program, not the file-system.
The 2Gb limitation was lifted for ext2 so long ago that it's a distant
memory. Certainly, 2.4.20 has no problems with files larger than 2Gb.
The main problem is that the historical Unix API used a "long" to
represent offsets within files (including the offset to the end of the
file, i.e. its size). On a 32-bit system, a "long" is only 32 bits, so
can only hold values up to +/- 2Gb.
A later revision of the API introduced the off_t type to hold file
offsets (and sizes). Because of the amount of historical code which
uses the "long" type, the off_t type is equivalent to "long" by
default. This can be changed to a 64-bit type at compile-time, but you
need to ensure that all code which references the file (including any
libraries) support large files (which is why it isn't the default).
</Quote>
For what ever reason I should try to dd a file on the local file
system greater than 2Gb to establish if its D-Cache or the OS.
I believe the restriction is 16Gb for ext[23] and much higher for XFS.
Reiser FS max size is only 4Gb.
Steve who was thinking about this, has more to say, and as he says, the
most worrying thing is the lack of gace in the way this was handled
by D-Cache.
Regards
Owen
|