Bugs item #911326, was opened at 2004-03-07 02:50 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=911326&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: Core Group: (zombie: MonetDB 4.3 CVS Head) >Status: Closed Resolution: None Priority: 6 Private: No Submitted By: Martin Kersten (mlkersten) Assigned to: Peter Boncz (boncz) Summary: Bus error on full disk Initial Comment: A full disk caused a bus error in Mserver while running an experiment to create a 'huge' table of 40M elements using the DBtapestry program. the latest portion of the BBP dir might indicate where action was missing, i.e. the first: -rw-r--r-- 1 mk ins 0 Mar 7 11:40 568.buns.priv -rw-r--r-- 1 mk ins 335609857 Mar 7 11:39 549.buns -rw-r--r-- 1 mk ins 335609857 Mar 7 11:39 568.buns -rw-r--r-- 1 mk ins 335609857 Mar 7 11:35 548.buns -rw-r--r-- 1 mk ins 180 Mar 7 11:31 540.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 540.desc -rw-r--r-- 1 mk ins 180 Mar 7 11:31 541.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 541.desc -rw-r--r-- 1 mk ins 180 Mar 7 11:31 542.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 542.desc -rw-r--r-- 1 mk ins 180 Mar 7 11:31 543.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 543.desc -rw-r--r-- 1 mk ins 180 Mar 7 11:31 544.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 544.desc -rw-r--r-- 1 mk ins 756 Mar 7 11:31 560.desc -rw-r--r-- 1 mk ins 335609857 Mar 7 11:29 560.buns.priv -rw-r--r-- 1 mk ins 125829124 Mar 7 11:27 557.buns -rw-r--r-- 1 mk ins 125829124 Mar 7 11:26 553.buns -rw-r--r-- 1 mk ins 251723777 Mar 7 11:25 555.buns -rw-r--r-- 1 mk ins 251723777 Mar 7 11:24 547.bun ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2007-11-29 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2006-11-29 01:05 Message: Logged In: YES user_id=572415 Originator: NO over-ruling "sf-robot": re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet. User (submitter) & developer (assignee), please check, again. ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2006-11-21 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2005-11-20 19:20 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2005-11-06 01:48 Message: Logged In: YES user_id=572415 BugDay_2005-10-06: "left-overs" are now marked as "pending" ---------------------------------------------------------------------- Comment By: Sjoerd Mullender (sjoerd) Date: 2005-10-06 04:01 Message: Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / POSTPONED - testing what happens in case of a fulll disk is hard to do automatically in Mtest - general check for left-over BATs should be added to Mtest itself - set priority to 9 to keep us reminded ---------------------------------------------------------------------- Comment By: Peter Boncz (boncz) Date: 2004-03-14 12:36 Message: Logged In: YES user_id=591107 what simply happened is that you ran out of disk space. memorymapped areas on files with holes, intantiate memory pages on the fly as they are written into. if that is not possible, you get a BUSERR signal. so the crash is normal and justified (you have consumed simply too much resources to be able to continue). the fix is to catch the signal and give an error message and quit. ---------------------------------------------------------------------- Comment By: Martin Kersten (mlkersten) Date: 2004-03-08 22:19 Message: Logged In: YES user_id=490798 running the tests on db1 did not cause problems. A second trial on Orion of runMILTapestry caused the system to 'hang' while processing 30M tuples. ---------------------------------------------------------------------- Comment By: Martin Kersten (mlkersten) Date: 2004-03-07 05:24 Message: Logged In: YES user_id=490798 running the tests on db1 did not cause problems. A second trial on Orion of runMILTapestry caused the system to 'hang' while processing 30M tuples. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=911326&group_id=56967 ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
