Related topics

RelCache (aka ELF prebinding) news
I should run "make test" against the default configuration, without 64-bit file support, and see if it's there, too. It's almost 2AM, though and I'm tired. ... lib/safe.......ok lib/sdbm.......sdbm store returned -1, errno 22, key "101" at ./lib/sdbm.t line 104. FAILED on test 8 lib/socket.....ok lib/soundex....ok

Problems taring up files larger than 2GB on Solaris 8
Smalltalk80 from Parcplace doesn't run on my small Mac Powerbook (needs the 68020 I think) and I guess it would be too big and too slow anyway. Any ideas? Floating point numbers are stored in 80 bit format (64 bit mantissa) rather than 64 bit format (53 bit mantissa). Whether this matters to you depends on your

innd does not find cycbufs
And even using zcat -f, it comes back with a "file too big" error. I thought it might be running out of disk space - but it is only 71% used when it dies. The real problem lies in the Intel CPU's 32-bit architecture, since ext2 is 64-bit by design and can handle files up to 2T in size on 64-bit processors

An article in BYTE, ignorance amazes me.
And what if your admittedly huge file is larger than 2**32 bytes? (A very real possibility! You said it was too big to fit in memory!) Are you going to suggest that all STRING* consumers on 32-bit platforms emulate 64-bit arithmetic whenever manipulating STRING* lengths? Blech. Yeah, that *would* be annoying.

gunzip "File too large"`
The error messages vary a bit between the two programs, the former complaining "write error onfilex: No such file or directory", the latter saying "gunzip: filex: File too large". I've tried various things with input/output redirection, and the error messages vary a bit, but the problem remains.

'file too large' error in log.smb
message, --------------------------------------------------- I'm running 64-bit enabled perl 5.6.1 on Irix 6.2 (SGI Origin 4000). I need to change it to: 12 6 0 13 7 1 14 8 2 15 9 3 16 10 4 17 11 5 (I also need to write it out as single-precision) Problem is, the file is too large (14Gb) to read in all at once.

max page file on 64 bit server exhange 2007?
Yes, and this is a cause of portability issues for programs written in those languages. ...interesting portability problem: "...hey, these 128-bit integers are too big! We're having problems storing the value 763 in it....." :-) ....which will enable you to use the underlying hardware more efficiently.

unpredictable behaviour
I have heard people talk "Is your file system flagged largefile", how do you check this and how do you change it if, it isn't set for large files. You are running into a well known problem with SOLARIS. While SUN continues to hype it as a 64-bit OE, the reality of the situation is that SOLARIS is only a 32-bit OE.

R14 fopen large files
[2000/05/15 09:03:12, 0] lib/util.c:(2760) fcntl_lock: WARNING: lock request at offset 0, length 4611686018427387904 retu rned a 'file too large' error. This can happen when using 64 bit lock offsets on 32 bit NFS mounted file systems. Retrying with 32 bit truncated length. what is the significance of this message?

Advice for Smalltalk/V on Mac
+x440-fixes.patch Various simplifications +ppc-64-bit-stat.patch +64-bit-dev_t-init_rd-fixes.patch 64-bit dev_t fixes +o14int.patch back to ksoftirqd rcu-grace-period.patch Monitor RCU grace period intel8x0-cleanup.patch intel8x0 cleanups bio-too-big-fix.patch Fix raid "bio too big" failures ppa-fix.patch ppc

large file support - odd upper limit
Even just running the zcat or gzcat command without piping it to cpio blows up with a "File too large for data type" error. Darnell Your system does seem to be a 32-bit variant without support for large files. As a workaround : Can you extract the data on a large (64 bit) or BSD machine ?

Please Break This
You get striped, so it gives you a speed improvement ... but also twice as big a drive. You might be better off not using RAID at all and just staging stuff Once people upgrade to 64 bit computers ... and then later to 64-bit Operating-Systems, then file sizes will probably be large enough to last for a while.

Ext2/3 32-bit stat() wrap for ~2TB files
In any case, I just checked a mix of big-endian and little-endian boxes: 32-bit BE SPARC 64-bit BE SPARC 32-bit BE PowerPC 32-bit LE i386 64-bit LE x86-64 64-bit LE Alpha In every case, 1-byte padding came after ac_flag. I'm pretty sure ac_comm is too big as well. It has room for 17 bytes. It needs room for 15,

2.5.74-mm3
M$ is still M$$$, they did not change the file formats on you to force you to upgrade your office applications, but they make XP so well that many of your older I think the video data is too much even with the 64-bit PCI. I upgraded my PCi card's memory to 320 Mbyte also. Don't forget to defragment your PCi's

generating files > 2 GB
... buf, len) FILE *fd; char *buf; ! int len; { while (len-- > 0) { --- 575581 ---- fputbytes(fd, buf, len) FILE *fd; char *buf; ! ssize_t len; val) FILE *fd; ! size_t val; { char c; if (val >= KRADIX*KRADIX) { + #if (_MIPS_SZLONG == 64) + fprintf(stderr, "error: integer too big (%ld > %d)\n", + val,

EXE file too big for memory
Just to name one example: the ext2 filesystem supports up to 4 TB, so according to your definition ext2 is a 64-bit file system. Have you ever seen a 4 TB disk? So we can safely say that no disk is too big for the ext2 filesystem. True. However, never say too big. As Linux advocates are so found of pointing out.

Ghostscript FAQ 0.4
What's the diff between my 16-bit sbox example and your 64-bit sbox (DES) example? Let me say that my main proposal is for blocks of at least two words and a This protocal is only good if the entire file/msg is available at once to load and provided it's not too big. The scheme intentionally does a whole-file

Bug#395164: Monit fails if log file is too large
The xrange() object implementation has been improved so that xrange(sys.maxint) can be used on 64-bit platforms. There's still a limitation that in this case In 1.6 and earlier, a negative long formatted via %u raised an error if it was too big to fit in an int. - Dictionary objects have an odd new method,

Contemplation of redesign of the traditional "file system" in ...
The files I'm moving in are about 15-20 Gbytes in size, so whatever solution I decide upon will have to support files that big. (The files are databases from a VMS machine.) The employer has dictated that the files *must* be moved to Linux. You might consider freebsd as an alternative, or Linux on a 64 bit

Suggestions for own file system structure / algorithm ?
Block #536346624 (980630818) causes file to be too big. IGNORED. ... Whoops. e2fsck sees that st_blocks is too large at this point, and decides that it Even if we fix up all the stat() stuff to pass back 64-bit st_blocks, we still have every e2fsck in existence which will not be able to deal with those files.