Hi Martin,

What machine/OS are you using?

We use GNU/Linux running on x86_64 machines.

Are the disks/partitions full? or nearly full?

Database is on a 4T file system, about a third is empty.

It looks like you have created a database with a large number of tables.

We have 10 schemas each having about 50 tables. 2 of the schemas are updated daily, when updating about 40 tables are deleted and recreated, i think it was designed that way to make the COPY INTO processes efficient. In the final steps of the update jobs table constraints are rebuild.

I think we trapped into this problem when the update process was taking unusually long, about a week ago. We killed the mclient process and have stopped the database using 'monetdb stop', thinking that the update process would never end. Is there any safer method than 'monetdb stop' to use in such situations?

--mahmut

...

We update our MonetDB databases using COPY INTO commands, we recently have started to get errors similar to the following error.

GDKerror:!ERROR: GDKload: cannot read: name=13/52/135274, ext=theap, 56932 bytes missing. !OS: No such file or directory GDKload: cannot read: name=13/56/135610, ext=theap, 906 bytes missing. !OS: No such file or directory

Deleting and recreating the tables and the schema haven't helped. If we create a new table with a table name not used in the past then we are able to use COPY INTO commands to update the new table. It is also possible to update the broken tables using 'INSERT INTO' commands. We see the problem only when we use COPY INTO commands.

We use MonetDB Jan2014-SP1 release. We have 3 database nodes that 2 of them doesn't show this error.

Any help much appreciated. We also don't know yet why we have started getting this error, any notes on how one can start getting this error would also be helpful.

Mahmut Uludag