An interesting development

------------------------- SNIP -----------------------

mysql> select count() from Attachments;
| count(
) |
| 560833 |
1 row in set (0.00 sec)

mysql> insert into Attachments values (0, 1159371, NULL,
‘TESTMESSAGEBLAH’, ‘— TEST TICKET —’, NULL, ‘text/plain’, NULL,
‘Testing’, ‘Testing HEADERS’, NULL, NULL);
ERROR 1114: The table ‘Attachments’ is full

bash-2.05$ tail -3 rt.log
error: couldn’t parse head; error near:

------------------------- SNIP -----------------------

Just a warning for those sites with growing RT2 databases, you might
want to watch for this problem. I’m now going to look into why MySQL
might be limiting the table; perhaps there’s a soft limit that can be
expanded, or perhaps a different table type has a higher capacity.

Byron Ellacott bje@apnic.net
APNIC

ERROR 1114: The table ‘Attachments’ is full
Just a warning for those sites with growing RT2 databases, you might
want to watch for this problem. I’m now going to look into why MySQL
might be limiting the table; perhaps there’s a soft limit that can be
expanded, or perhaps a different table type has a higher capacity.

The problem is the underlying OS, which limits files to 4G; using the
MySQL RAID table create option will solve this, as soon as we manage to
dump/restore the current data :slight_smile:

Byron Ellacott bje@apnic.net
APNIC

Do you know if this applies to InnoDB databases as well? I’m working on a
migration plan from rt2 to rt3 and to InnoDB.----- Original Message -----
From: “Byron Ellacott” bje@apnic.net
To: rt-users@lists.fsck.com
Sent: Sunday, February 23, 2003 6:21 PM
Subject: Re: [rt-users] An interesting development

On Mon, 2003-02-24 at 11:52, Byron Ellacott wrote:

ERROR 1114: The table ‘Attachments’ is full
Just a warning for those sites with growing RT2 databases, you might
want to watch for this problem. I’m now going to look into why MySQL
might be limiting the table; perhaps there’s a soft limit that can be
expanded, or perhaps a different table type has a higher capacity.

The problem is the underlying OS, which limits files to 4G; using the
MySQL RAID table create option will solve this, as soon as we manage to
dump/restore the current data :slight_smile:


Byron Ellacott bje@apnic.net
APNIC


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm