Bug #26487 Bug in extent/page allocation when *using* >1gb datafiles

Submitted: 20 Feb 2007 4:51 Modified: 9 Mar 2007 1:53
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Disk Data Severity:S3 (Non-critical)
Version:5.1 OS:
Assigned to: Jonas Oreland CPU Architecture:Any

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

  • On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
  • On windows use WinZip or a similar utility to split the large file
[20 Feb 2007 4:51] Tomas Ulin 
config.ini

Attachment: config.ini (application/octet-stream, text), 773 bytes.
[20 Feb 2007 4:54] Tomas Ulin 
truncated trace log

Attachment: ndb_1_trace.log.1.gz (application/x-tar, text), 5.26 KiB.
[20 Feb 2007 5:11] Tomas Ulin 
information schema select (after restart)

Attachment: information_schema.txt (text/plain), 3.34 KiB.
[20 Feb 2007 5:20] Tomas Ulin 
ndb_1_out  lots of stuff written there....

Attachment: ndb_1_out.log.gz (application/x-tar, text), 65.38 KiB.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.047 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.