RE: increase file limit 2gb for IDS 7.31 ontape -s -L 0 with

Hi, yes. You can do that. On systems that do not support large files (> 2GB) by default, you have to do that in order to get the possibility at all. However, this in general does not automatically enable large files for all applications running on such a system. And this is especially true for applications that have not been compiled and linked on that same machine (after enabling large files). [ The problem is the implementation and use of file related system calls, especially the system calls "seek()" and/or "lseek()". They return the position of the file pointer, kind of as an offset in bytes into the file. This is an integer number. In older implementations of the system calls, this return value was an "int" (i.e. 32-bits), in newer implementations it is a "long long" (64-bits). [ In fact the type is "size_t", but the actual size in bytes of this corresponds to one of the above two types. ] Therefore if the application is built (compiled and linked) on a system with the old implementation, then it's file offset capabilities are limited to 32-bit, which means in effect 2 GB file size. For such an application it does not matter whether the runtime system is capable of large files or not. The compile/link system is relevant. As well it does not matter whether the runtime system is 64-bit or 32-bit architecture. If an application does casting of a "size_t" return value from a system call to an "int" (indisputably not a good programming style), then it will not even help to merely compile and link the application on a large-file capable system. It is necessary to first go and fix all these wrong casts. ] So there are several reasons, why 7.31 is not really capable of handling files larger than 2 GB. [ Phew! Nested soap-boxes ... that's a first for me. ;-) ] Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management owner-informix-list@iiug.org wrote on 09.12.2005 11:14:38: > I do not know Linux this well, but can you enable large filesystems ? > On Solaris you can set this in your /etc/vfstab file, which allows you > to create files larger than 2Gb. > > > -----Original Message----- > From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] > On Behalf Of Cesar Cruz > Sent: 08 December 2005 03:17 AM > To: informix-list@iiug.org > Subject: increase file limit 2gb for IDS 7.31 ontape -s -L 0 with linux > redhat 3 enterprise edition update 4 > > Hi, > > We have Linux RedHat 3 Update 4 whith IDS 7.31 when ontape -s -L 0 is > send it. > > The file in /backups2/backup allways end with 2GB file size but all the > instance have 40 GB. > > This is the ulimit -a > > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > file size (blocks, -f) unlimited > max locked memory (kbytes, -l) 4 > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > stack size (kbytes, -s) 10240 > cpu time (seconds, -t) unlimited > max user processes (-u) 7168 > virtual memory (kbytes, -v) unlimited > > > This is the fstab > LABEL=/ / ext3 defaults > 1 1 > LABEL=/boot /boot ext3 defaults > 1 2 > none /dev/pts devpts gid=5,mode=620 > 0 0 > none /proc proc defaults > 0 0 > none /dev/shm tmpfs defaults > 0 0 > /dev/cciss/c0d0p2 swap swap defaults > 0 0 > /dev/cdrom /mnt/cdrom udf,iso9660 > noauto,owner,kudzu,ro 0 0 > /dev/fd0 /mnt/floppy auto > noauto,owner,kudzu 0 0 > > the file /etc/security/limits.conf > > has nothing configurated. > > Some one can help me? > > Regards, > > > > > > > ___________________________________________________________ > Do You Yahoo!? > La mejor conexisn a Internet y <b >2GB</b> extra a tu correo por $100 al > mes. http://net.yahoo.com.mx > sending to informix-list > > > > The information on this e-mail including any attachments relates to the official business of DigiCare (Pty) Ltd. The information is confidential and legally privileged and is intended solely for the addressee. Access to this e-mail by anyone else is > unauthorised and as such any disclosure, copying, distribution or any action taken or omitted in reliance on it is unlawful. Please notify the sender immediately if it has inadvertently reached you and do not read, disclose or use the content in any way. > > > No responsibility whatsoever is accepted by DigiCare (Pty) Ltd if the information is, for whatever reason, corrupted or does not reach its intended destination. The views expressed in this e-mail are the views of the individual sender and should in no > way be construed as the views of DigiCare (Pty) Ltd, except where the sender has specifically stated them to be the views of DigiCare (Pty) Ltd. > sending to informix-list sending to informix-list