-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-02-15 17:10, Anthony Damico wrote:
> I am running MonetDB5 Oct 2012 SP3 on my work Windows 7 desktop
> computer.  My office has what I imagine is a pretty typical mix of
> networked machines, with a few more powerful servers and larger
> shared drives that everyone can connect to.  (1) When I attempt to
> import a large CSV file into a MonetDB server on the _local_ disk
> (C:\My Directory\MonetDB\dbfarm), the importation command runs as
> expected. (2) When I attempt to import the same CSV file to a
> MonetDB server stored on a networked drive, the import command
> fails.  (3) Finally, when I *remote desktop* into the server that
> the networked drive is actually attached to, the importation
> succeeds again!  Here's the error seen in scenario (2) --
>
>
> GDKerror:!ERROR: GDKunlink(bat\13\1327.tail) !OS: The process
> cannot access the file because it is being used by another
> process. GDKunlink(bat\13\1327.theap) !OS: The process cannot
> access the file because it is being used by another process.
>
>
> So it seems pretty clear that something about windows networked
> drives is the culprit.  This error does not occur on every file
> (larger files seem more prone to the error), but if an import
> command does not work on a file, it _consistently_ does not work on
> that file.  As an example, importing this large file works with
> methods (1) and (3) but not (2) --
>
> http://downloads.cms.gov/BSAPUF/2008_BSA_Carrier_Line_Items_PUF_1.zip
>
>
>
> I tried disabling the windows firewall and using different server
> ports, but I still hit the above error.
>
> I spoke with Hannes about it briefly, he said: "The issue is
> probably related to the Windows mmap() implementation when talking
> to a SMB filesystem. It is far from certain that there is something
> we can do about this, but in either case, we'd like to know about
> it."
>
>
> Should I submit an official bug report to http://bugs.monetdb.org/
> ? Perhaps we are overlooking something obvious about our windows
> network's configuration..

By all means, please submit a bug report.  I agree with Hannes, your
description of what goes wrong and what works points towards memory
mapped files.
We haven't tried the scenario.  When we do run the server on Windows,
we always use local drives (local to mserver5, that is).

- --
Sjoerd Mullender
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQCVAwUBUR5kOT7g04AjvIQpAQIdPQP/fiEYG3TW3CvQigLSXm87bCvpbm5/DPYJ
jvQVfG0MKl++o60gA1TckhMLBrT0F6Uqozw0XImqdwMY757c6Ss0taZy3GmWvooG
qo/+WkcjZJWRK2bdsLn7Rp0zG0xc4fPP6S1QbpnEKlENSVcazGYqPvVbKzM61WGM
CjxakeYl68A=
=SJvx
-----END PGP SIGNATURE-----
_______________________________________________
users-list mailing list
users-list@monetdb.org
http://mail.monetdb.org/mailman/listinfo/users-list