Very Computer

by **Dances With Cro** » Sat, 23 Jun 2001 10:06:24

[Inappropriate and nonexistent NGs removed]

On Thu, 21 Jun 2001 23:33:33 GMT, Jason M. Shatto staggered into the
Black Sun and said:

>> I am running Redhat 6.2 with kernel 2.4.2 on a Dell Power Edge 6400 I
>> am using ext2 file system. Is there a way to remove the 2GB file size
>> limitation and how if so? Any help would be appreciated.
>The 2GB limitation has to do with the /boot partition. If you make
>this a 25 or 30MB Partition, then you can make the root partition "/"
>as big as you would like (some limitations I'm sure)

That's not what Justus meant by "2G filesize limitation". File size !=
partition size or partition placement.

As I keep telling anyone who has the brains to use
http://groups.google.com/ , the 2G limitation is an artifact of some
kernel design decisions made several years ago and the x86 architecture.
To get a system able to use > 2G files, you need several things:

0. A 2.4.x kernel or a 2.2.x kernel that's been patched w/largefile.
1. A glibc that's been compiled with largefile support
2. Applications that have been compiled against that glibc

Or:

3. An Alpha or Sparc64 system.

The easiest way for Justus to get all the elements in steps 0, 1, and 2
is for him to use a more recent distro, like RedHat 7.1 or SuSE 7.2.
Step 2 is the really time-consuming part. I can say that at least some
applications under RedHat 7.0 can grok > 2G files.

--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Outside of a dog, a book is a man's best
http://www.brainbench.com / friend. Inside of a dog, it's too dark
-----------------------------/ to read. --Groucho Marx

by **Betast** » Sat, 23 Jun 2001 10:39:09

Quote:>As I keep telling anyone who has the brains to use
>http://groups.google.com/ , the 2G limitation is an artifact of some
>kernel design decisions made several years ago and the x86 architecture.
>To get a system able to use > 2G files, you need several things:

>0. A 2.4.x kernel or a 2.2.x kernel that's been patched w/largefile.
>1. A glibc that's been compiled with largefile support
>2. Applications that have been compiled against that glibc

>Or:

>3. An Alpha or Sparc64 system.

>The easiest way for Justus to get all the elements in steps 0, 1, and 2
>is for him to use a more recent distro, like RedHat 7.1 or SuSE 7.2.
>Step 2 is the really time-consuming part. I can say that at least some
>applications under RedHat 7.0 can grok > 2G files.

It takes more than 7.1 to get this though - it is not fully
implemented yet. I have 7.1, run 7.1 with the enterprise kernel
(2.4.2.2) with the proper glibc, and still have yet to see a file go
above 2.0GB without a core dump and a filesize error.

Betastar

by **Dances With Cro** » Sat, 23 Jun 2001 12:17:47

On Fri, 22 Jun 2001 01:39:09 GMT, Betastar staggered into the Black Sun
and said:

>>The easiest way for Justus to get all the elements in steps 0, 1, and
>>2 is for him to use a more recent distro, like RedHat 7.1 or SuSE 7.2.
>>Step 2 is the really time-consuming part. I can say that at least
>>some applications under RedHat 7.0 can grok > 2G files.

>It takes more than 7.1 to get this though - it is not fully
>implemented yet. I have 7.1, run 7.1 with the enterprise kernel
>(2.4.2.2) with the proper glibc, and still have yet to see a file go
>above 2.0GB without a core dump and a filesize error.

Well, that's completely FUBAR since 7.0 with the "enterprise" 2.2.16
kernel and the stock glibc deals with large files on x86 just fine.
Could it be 2.4.2's fault? In my experience, the 2.4 series wasn't all
there until 2.4.5.

--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Outside of a dog, a book is a man's best
http://www.brainbench.com / friend. Inside of a dog, it's too dark
-----------------------------/ to read. --Groucho Marx

by **Rex Diete** » Sat, 23 Jun 2001 22:26:29

>>To get a system able to use > 2G files, you need several things:

>>0. A 2.4.x kernel or a 2.2.x kernel that's been patched w/largefile.
>>1. A glibc that's been compiled with largefile support
>>2. Applications that have been compiled against that glibc
> It takes more than 7.1 to get this though - it is not fully
> implemented yet. I have 7.1, run 7.1 with the enterprise kernel
> (2.4.2.2) with the proper glibc, and still have yet to see a file go
> above 2.0GB without a core dump and a filesize error.

Point 2 above needs to be amended:
2. Applications have been compiled with LFS support against that glibc

Not all apps support LFS, only those configured to do so.

--

Computer System Administrator http://www.math.unl.edu/~rdieter/
Mathematics and Statistics
University of Nebraska Lincoln

by **Betast** » Sat, 23 Jun 2001 22:11:33

Quote:>>It takes more than 7.1 to get this though - it is not fully
>>implemented yet. I have 7.1, run 7.1 with the enterprise kernel
>>(2.4.2.2) with the proper glibc, and still have yet to see a file go
>>above 2.0GB without a core dump and a filesize error.

>Well, that's completely FUBAR since 7.0 with the "enterprise" 2.2.16
>kernel and the stock glibc deals with large files on x86 just fine.
>Could it be 2.4.2's fault? In my experience, the 2.4 series wasn't all
>there until 2.4.5.

Could be, since I've heard others say they've got it running too.
My other thought is that while I upgraded the kernel, I didn't do
anything with the glibc.

Do I need to recompile it against the new kernel?
And since I'm a Linux newbie (lots of Unix experience, first time
administering at this level, though) ... How do I recompile glibc
against the new kernel??

Betastar

Very Computer

2GB File size limitation

2GB File size limitation

2GB File size limitation

2GB File size limitation

2GB File size limitation

2GB File size limitation