 | | | mysqldump: Got errno 27 on write. file too large | mysqldump: Got errno 27 on write. file too large 2006-07-05 - By Michael Stassen
Back
Dominik Klein wrote:
> This might be a filesystem problem. Some filesystems (in certain
> configurations) cannot hold files larger than a particular size.
>
> Do you have any files larger than that cut dumpfile on that partition?
>
Duhaime Johanne wrote:
> Thank you for your answer.
>
> Yes I have file larger than what mysqldump could manage. Here is an
> example of this. Both files are on the same partition.
>
> mercure{root}54: du -k mercure.log.jui2006
> 11948544 mercure.log.jui2006
Umm, that's only about 1Gb, which makes it smaller than the problem file. Did
you mean to show us a different file?
> mercure{root}68: du -k myregendump
> 2098184 myregendump
> Which stop at that size.
>
> Which make me think that mysql is concerned. Or a tmp file but as I
> mention the tmp file has plenty of space.
>
> Best regards
>
> Johanne
My first thought is that Dominik is on the right track. I get
~: perror 27
OS error code 27: File too large
which suggests there is some OS limitation. Perhaps the user running mysqldump
is limited? Do you have any larger files owned by the same user? Can that
user
currently create a file larger than that using another means?
The other possibility would be a bug. You are using version 4.1.7, which is
nearly 2 years old now (released October 2004). The current version is 4.1.20.
If you have indeed hit a bug, your best bet would be to upgrade and try
again. You should probably at least read the *long* list of bug fixes from
4.1.7 to 4.1.20 in the MySQL change history in the manual
<http://dev.mysql.com/doc/refman/4.1/en/news-4 (See http://ews-4.ora-code.com)-1-x.html>.
Michael
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=mysql@(protected)
|
|
|