Here is what you suggested:
I don't know what is going on, since I do have files greater than 2 GB, and
no problem with them...
At the beginning I thought it was a problem in which MySQL couldn't handle
large input files, so I spited my original file into two parts. One a little
bit less than 2 GB and the other with the rest of the data. Here you can see
that I do have files greater than 2GB:
% ls -al | grep supfam
-rw-r--r-- 1 supfam supfam 2161802937 Apr 13 22:17 supfam01.sql
-rw-r--r-- 1 supfam supfam 887476820 Apr 13 21:58 supfam02.sql
-rw-r--r-- 1 supfam supfam 3049279757 Apr 13 19:46 supfamORIGINAL.sql
So I don't think this is a limit imposed by the filesystem... unless you can
guess something different.
I could try using the 'raid' support, and see what happens, but still the
problem would persist since I will have to have some indexes and as you say
that could bring me to the same problem again.
Thank you for your help... I am looking forward to get another
answer/direction from your side.
Anyway, could you please tell me where can I find a "quick guide to raid
support in MySQL"? =)
From: Sean Quinlan [mailto:sean@stripped]
Sent: Miércoles, 14 de Abril de 2004 01:35 p.m.
To: Dan Nelson
Cc: Cesar Bonavides Martinez; mysql@stripped
Subject: Re: Problem with 2GB limit.
On Wed, 2004-04-14 at 15:20, Dan Nelson wrote:
> Now that's interesting. Max_data_length is set to 4gb, but you're
> getting an error at 2gb. Could it be a process resource limit? What
> does the "ulimit" command return? You can reset that limit with the
> "ulimit unlimited" command.
IIRC, some filesystems have a 2gb limit for file size. This could be the
wall your hitting?
I've used mysql's 'raid' support in a couple instances in the past as a
simple way get beyond this data limit (wont help with indexes > your
filesize limit however). However I'm having trouble getting that working
Sean Quinlan <sean@stripped>