Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion The C-Prize
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Matt Mahoney  
View profile  
 More options Jun 19 2005, 7:31 pm
Newsgroups: comp.compression
From: "Matt Mahoney" <matmaho...@yahoo.com>
Date: 19 Jun 2005 16:31:59 -0700
Local: Sun, Jun 19 2005 7:31 pm
Subject: Re: The C-Prize

jim_bow...@hotmail.com wrote:
> Erratum:

> I had written:
> >  such as ext3 which have a 2GiB file size limit.

> This is wrong.  I got this erroneous information from the first hit
> that google returned on the subject:

> http://www.linuxgeek.net/beginners/node101.html

> The truth is that the maximum file size varies with the blocksize of
> the ext3 file system and that maximum file size is given by the
> following table available from:
> http://www.novell.com/documentation/suse91/suselinux-adminguide/html/...

> Ext2 or Ext3 (1 kB block size)     234 (16 GB)     241 (2 TB)
> Ext2 or Ext3 (2 kB block size)     238 (256 GB)    243 (8 TB)
> Ext2 or Ext3 (4 kB block size)     241 (2 TB)      244 (16 TB)
> Ext2 or Ext3 (8 kB block size) (systems with 8 kB pages (like
> Alpha))    246 (64 TB)     245 (32 TB)

> My Ubuntu system came with 4kB blocksize (according to dumpe2fs) for
> max file size of 2TB.

> The problem was with the wget command.  Apparently the Linux distro
> guys aren't as religious as they should be about updating their basic
> utilities to handle larger file sizes given the new world of cheap
> massively large disks.

Lots of programs probably assume files are never larger than 2 GB.
fseek() and ftell() use 32 bit signed ints.  Maybe your program doesn't
call these directly, but maybe the library does.  Maybe some other part
of the program does this implicitly, like counting bytes with an int or
long, or using 32 bit pointers or array indexes.  Probably this stuff
doesn't get tested a lot.

It wouldn't hurt to split up the big files into pieces for the contest.

-- Matt Mahoney


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.