File size limit

It seems to me that the maximun file size that QNX can handle is 2G bytes, I
haved tried ‘cp’ and write () from the code, I could not exceed the 2GB
limit in either case.

Is this true? What casues it if it is? Apparently Windows (at least XP) can
handle much bigger files.

Thanks,

Xuedong

Xuedong Chen <Xuedong.Chen@igt.com> wrote:

It seems to me that the maximun file size that QNX can handle is 2G bytes, I
haved tried ‘cp’ and write () from the code, I could not exceed the 2GB
limit in either case.

The QNX 4 filesystem (default for QNX Neutrino) can not handle files
over 2G-1 bytes.

Is this true?

Yes. (But… see below…)

What casues it if it is?

History – though partially it also comes from the POSIX API in 32-bit,
where the current file position for lseek() is a signed 32-bit integer.

The API hooks (e.g. lseek64() ) exist for handling larger messages,
our messaging has space for the larger integers, so a filesystem that
handled longer files could be implemented under QNX.

(Or, a resource manager that sits on top of a filesystem, and implements
longer files by combining two or more smaller files, could be done
without too great difficulty.)

Do you need large files?

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Thanks, not a must. I just need it for a test project, I will change my
approach if I can not get a large file easily.

Xuedong
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:bgs2l7$ffl$1@nntp.qnx.com

Xuedong Chen <> Xuedong.Chen@igt.com> > wrote:
It seems to me that the maximun file size that QNX can handle is 2G
bytes, I
haved tried ‘cp’ and write () from the code, I could not exceed the 2GB
limit in either case.

The QNX 4 filesystem (default for QNX Neutrino) can not handle files
over 2G-1 bytes.

Is this true?

Yes. (But… see below…)

What casues it if it is?

History – though partially it also comes from the POSIX API in 32-bit,
where the current file position for lseek() is a signed 32-bit integer.

The API hooks (e.g. lseek64() ) exist for handling larger messages,
our messaging has space for the larger integers, so a filesystem that
handled longer files could be implemented under QNX.

(Or, a resource manager that sits on top of a filesystem, and implements
longer files by combining two or more smaller files, could be done
without too great difficulty.)

Do you need large files?

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.