Bugs item #1312130, was opened at 2005-10-03 20:02 Message generated for change (Comment added) made by romulog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1312130&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: SQL/Core Group: SQL CVS Head Status: Open Resolution: None Priority: 5 Private: No Submitted By: Martin Kersten (mlkersten) Assigned to: Niels Nes (nielsnes) Summary: SQL:segfault upon recovery/restart Initial Comment: Problem reported below indicates we need better protection against overflowing log directories and at least ensure that database directory and log directory are in sink. The recovery process should be safe against removal of any accidental removal of directories. The long awaited for Mguardian should include a scheme to deal with overflow in this area, e.g. sent email to the dba when the space for logs become tight. --------------------------- It seems MonetDB has problem with handling of huge tables (larger than amount of memory available). I tried to load large amount of data into a table using COPY command. I loaded same data (6 millions records, 700+MBytes) few times. Loading was successful two times, on third time server crushed. After crush I could not start the server again, it output messages !WARNING: GDKlockHome: ignoring empty or invalid .gdk_lock. !FATAL: BBPinit: cannot properly process bat/BACKUP/. and exited. Removing of the database data directory did not help much - server output messages !ERROR:mvc_init: unable to create system tables !WARNING: BBPincref: range error 410 Couple minutes later it output !ERROR: BATSIGcrash: Mserver internal error (Segmentation fault), please restart . !ERROR: (One potential cause could be that your disk might be full...) Well, insufficient disk space could be a cause, before server crashed I had approximately 2GB free. But I have cleaned up 10 GB and problem persists. How can I troubleshoot and fix the server ? What are memory / disk space requirements when bulk loading data ? I tested with 32-bit system, 512 MB RAM + 1GB swap, Ubuntu Linux, MonetDB-4.9.3, nightly build dated September 30. -- Best regards, Andrei Martsinchyk ---------------------------------------------------------------------- Comment By: Romulo Goncalves (romulog) Date: 2007-01-17 19:44 Message: Logged In: YES user_id=1498628 Originator: NO Why this bug is not closed? Regards, Romulo ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2006-06-06 21:03 Message: Logged In: YES user_id=963970 how about adding support for some "informative" error messages to start with? ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2005-12-21 11:28 Message: Logged In: YES user_id=572415 BugDay: stmane: NO TEST / POSTPONED: I'm not sure, whether it is feasible to provide a proper test script ... ---------------------------------------------------------------------- Comment By: Niels Nes (nielsnes) Date: 2005-10-05 22:08 Message: Logged In: YES user_id=43556 Protecting against users removing important data is impossible. The bugs we should fix are 1) don't crash on loading (to much) data, but report the problem and gracefully drop the inserts. When we startup without enough diskspace we should give more informative error messages. ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2005-10-04 13:31 Message: Logged In: YES user_id=963970 from Andrei: It was due to insufficient disk space. After freeing up 10 GB I successfully loaded more than 2GB of data. Server crush if there is lack of disk space is an issue, but not critical one. I guess we need some better/more indicative error messaging. ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2005-10-03 20:29 Message: Logged In: YES user_id=963970 the same problem was reported today by a few students who more or less did the same: loading a lot of data into MonetDB. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1312130&group_id=56967 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
