Hello Yes, if your physical drive has been corrupted there is no other way as to restore the dbfarm from your backup system or rebuilt the database from your source input. regards, Martin On 10/3/12 9:59 PM, Assaf Gordon wrote:

Hello,

While loading a large file into a MonetDB database, my server crashed (the physical machine, not the MonetDB server process). After rebooting the machine and restarting MonetDB, almost every query crashes the MonetDB server:

== $ mclient -d voc Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased) Database: MonetDB v11.14.0 (unreleased), 'mapi:monetdb://chachacha.cshl.edu:50000/voc' Type \q to quit, \? for a list of available commands auto commit mode: on sql>select * from bc251 limit 10 ; Connection terminated

$ tail merovingian.log <snip> 2012-10-03 15:53:51 MSG merovingian[4001]: proxying client (local) for database 'voc' to mapi:monetdb:///localdata/gordon/monetdb/testdb4/voc/.mapi.sock?database=voc 2012-10-03 15:53:51 MSG merovingian[4001]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-10-03 15:53:58 MSG merovingian[4001]: database 'voc' (4043) was killed by signal SIGSEGV ==

The database contains several tables, and queries on all of them result in monetdb server crash.

How do I fix the database ? I tried "monetdbd stop + start", and also "monetdb lock + release", but to no avail.

Thanks, -gordon

BTW, It is likely that some of the database files are corrupted (due to the physical server crash). _______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

_______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list