Hello, On Thu, 2005-06-09 at 03:48, Pat Thoyts wrote: <snip> > > The metakit file was created using Windows XP on a local hard drive but has > almost > certainly been modified over an SMB mount. I believe the server was > Windows 2003 server (but it may have been NT 4 -- they upgraded fairly > recently). <snip> > I would like to know if anyone has seen something similar or has any > idea how this might be reproduced. If this is a metakit over SMB issue > it would be good to confirm this. If it's a more general metakit on > windows issue then I need to work out a fix.
Using the python interface, corruption happens 90% of the time with network file access. Doesn't matter if it's a Linux based Samba server, Window's NT, 2000, or 2003 server. Given that the Microsoft recommended small business configuration is to keep all important files on the main file server for backup purposes we had to abandon using Metakit. Local file access worked just fine. Someone recently reported that turning off memory mapped access seemed to correct the problem for them, IIRC Windows doesn't guarantee a consistent view of a memory mapped files also accessed via file handle operations (even if you unmap and remap), YMMV. HTH, William. -- William K. Volkman <[EMAIL PROTECTED]> _____________________________________________ Metakit mailing list - [email protected] http://www.equi4.com/mailman/listinfo/metakit
