[MDEV-13666] Wheezy runs out of disk space / shm Created: 2017-08-29  Updated: 2017-10-04  Resolved: 2017-10-04

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: N/A
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Daniel Bartholomew
Resolution: Fixed Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-wheezy-amd64/builds/10095/steps/mtr/logs/stdio

innodb.innodb-enlarge-blob '32k,innodb'  w1 [ fail ]
        Test ended at 2017-08-28 19:09:25
 
CURRENT_TEST: innodb.innodb-enlarge-blob
mysqltest: At line 23: query 'UPDATE t1 SET a=CONCAT(a, RAND(), a)' failed: 1114: The table 't1' is full
 
The result from queries just before the failure was:
CREATE TABLE t1 (a LONGTEXT) ENGINE=INNODB DEFAULT CHARSET=UTF8 ROW_FORMAT=DYNAMIC;
SHOW WARNINGS;
Level	Code	Message
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B');
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
INSERT INTO t1 SELECT CONCAT('A', SPACE(4087), 'B') FROM t1;
UPDATE t1 SET a=CONCAT(a, RAND(), a);
UPDATE t1 SET a=CONCAT(a, RAND(), a);
UPDATE t1 SET a=CONCAT(a, RAND(), a);

As discussed earlier, wheezy has been running out of space quite often recently. Probably other VMs will follow. The outcome of that discussion was that we should try to increase the memory for our kvm runs.



 Comments   
Comment by Daniel Bartholomew [ 2017-08-31 ]

Current plan is to add a new memory size variable to maria-master.cfg and update the various builder definitions to use that variable when launching VMs. This way if we want to change the default memory again we can just update one variable and have it apply everywhere.

Comment by Daniel Bartholomew [ 2017-08-31 ]

This is now in place. Not sure if it's related or not, but I also noticed that the most recent wheezy 10.2 builds succeeded, before I upped the memory.

Marko made the commit that seemed to fix things: https://github.com/MariaDB/server/commit/a9e71c77e429e5cf35bb5373a4bda41983d21002

In any case, we can still easily adjust the memory now, up or down.

Comment by Daniel Bartholomew [ 2017-10-04 ]

I think this issue is fixed. Please reopen if it is not (with details and links of what remains to be done). Thanks.

Generated at Thu Feb 08 08:07:23 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.