Hi Mark,
Can you please provide:
1. A copy of your virtuoso.ini and virtuoso.log files
2. A directory listing from your database directory
3. Details of the operating system being used (uname -a) and any other
commands detailing machine resources ie number of cores, memory size, disk
space etc
Do you know what is the file size of the operating system being used which
would be the limiting factor as to the size of a single database file. In
theory Virtuoso can support database sizes up to 32TB on a 64bit operating
system, but typically would requiring striping/segmenting of the database
across multiple file to get around OS limits and also performance improvement
as detailed in the following documents on striping:
http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#ini_Striping
http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#IOQS
14 billion triples hosted in a single virtuoso instance and way past the
1billion triple recommended for a single server instance beyond which a
clustered server, available in the commercial Virtuoso product is recommended:
http://docs.openlinksw.com/virtuoso/virtuosofaq.html#virtuosofaq11
Having said that we do have users running successfully with 5 billion plus
triples in a single open source instance, but 14 billion is really pushing the
barrier I would say ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com
Support: http://support.openlinksw.com
Forums: http://boards.openlinksw.com/support
Twitter: http://twitter.com/OpenLink
On 26 Mar 2010, at 18:25, Marc-Alexandre Nolin wrote:
> Hello,
>
> I've load a complete version of PDB in N3 with an approximate size of
> 14 billions triples. It completed successfully, but it crash at the
> end of a checkpoint and don't want to restart. I'm getting the
> following error:
>
> GPF: disk.c:2046 looking for a dp allocation bit that is out of range
> Segmentation fault
>
> Also, the first message I've receive, but it is not giving it to me anymore
> was
>
> GPF: disk.c:1867 cannot write buffer to 0 page.
>
> What does this mean? Is it because of the size of the virtuoso.db
> which is 1.1 TB?
>
> Thanks for the help,
>
> Marc-Alexandre Nolin
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Virtuoso-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
