HI all –

A week or so ago we ran an upgrade to the lastest monetdb June-2020 patch.  Our db was 2 patches old.

While the log showed no specific problems, the upgrade effected our databases in that 2 of them would crash when they were accessed, and the third one (the largest one) I could access but could not see any tables.

I ended up “destroying” all the dbs and recreating them fomr the saved binary files.

Now, we are getting disk full messages (the db is only read – no one is adding to it).  I look at the file sizes and there is a huge mervingian.log file:

Is it a problem if I delete this file?  What will it hurt?  Should I “tail” it and save the end of it?  Please advise.

root@cbsudc01 dbfarmBL]# du -h --max-depth=1
1.3M    ./testDB_lynn
52G     ./maizeChrom10DB
955G    ./maizeFullGenomeDB
1.3M    ./testDB
6.9T    .

[lcj34@cbsudc01 dbfarmBL]$ l -ltr

total 6320304952

-rw-rw---- 1 root buckler 339559112 Oct 9 2018 merovingian.log.old

drwx------ 4 root root 121 Jun 26 13:54 testDB_lynn/

drwx------ 4 root root 121 Jul 1 17:23 maizeChrom10DB/

drwx------ 4 root root 121 Jul 1 17:23 testDB/

-rw-r--r-- 1 root root 6 Jul 1 17:23 merovingian.pid

drwx------ 4 root root 4096 Jul 1 17:24 maizeFullGenomeDB/

-rw-r--r-- 1 root buckler 6471651893248 Jul 6 14:43 merovingian.log

[lcj34@cbsudc01 dbfarmBL]$

Thanks - Lynn