HashDB import tool (database full) #1232
Unanswered
thiagocaparelli
asked this question in
Q&A
Replies: 1 comment
-
Hi, The optimization step needs up to 2x the database size of free space (32GB free space in your case), if you don't have it, the optimization will fail and temp files deleted. But the database should be in a consistent and usable state. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
I'm trying to create a database containing NSRL, NSRL-CAID, Project VIC and LED.
First I've added the NSRL using this command:
java -jar .\iped-hashdb.jar -d T:\Pericia\Ferramentas\Base-de-Hashes\rds_modernm\ -o C:\temp-iped\iped-hashes.db
Before that I've tried to insert the Project VIC using this:
java -jar .\iped-hashdb.jar -d E:\Documentos\Hubstream\Inbox\ -o C:\temp-iped\iped-hashes.db
First of all, it takes a lot of time (3 to 4 days), and in the end I've got this error:
Optimizing the database...
org.sqlite.SQLiteException: [SQLITE_FULL] Insertion failed because database is full (database or disk is full)
at org.sqlite.core.DB.newSQLException(DB.java:1012)
at org.sqlite.core.DB.newSQLException(DB.java:1024)
at org.sqlite.core.DB.execute(DB.java:866)
at org.sqlite.core.CoreStatement.exec(CoreStatement.java:80)
at org.sqlite.jdbc3.JDBC3Statement.execute(JDBC3Statement.java:46)
at iped.engine.hashdb.HashDBTool.vacuum(HashDBTool.java:1601)
at iped.engine.hashdb.HashDBTool.finish(HashDBTool.java:1642)
at iped.engine.hashdb.HashDBTool.main(HashDBTool.java:121)
Optimization completed in 3026 seconds.
Now the database iped-hashes.db have more or less 16GB, and the disk is not full.
By the way the disk is SSD.
Anyone knows what is happening?
THX
Beta Was this translation helpful? Give feedback.
All reactions