dexpand problem

[Richard Kreiss]

Apparently there is a limit to the file size that dexpand.exe can handle.

One of my client's reached that limit.  It is a file size over 4GB.

This issue was corrected by fpTech.

Note that this is on filePro 5.8.  My client has upgraded to 5.8(64 bit) but the problem was with their production system which is 5.6 and this fix is not backward compatible.   They should be moving to their new server and 5.8 in the next week after a bit more testing.  The server came through with some issues which required a motherboard change and reinstallation of the operating system.

I don't think in past years that anyone thought companies would be having data files this size.  My client already has a history file that is approaching  6GB  in size as well as some automatic indexes reaching 5 to 6 GB.

Consider that when most of us started with filePro, a 15Mb hard drive was considered huge.  Now storage is talked about in 1,2,3 and 4 TB drives.  Some arrays are much larger than that.

By the way, this issue kept occurring with rebuilding free chain messages.  Over the past few years, once in a while, then this year more and more often.  Rebuilding the free chain over the network, on files this size takes well over 3 or 4 hours.  It's a matter of minutes on the server.

If you know that there are files nearing the 4GB mark, be aware that you will have issues.  This is a good time to consider upgrading to 5.8.


Richard Kreiss
GCC Consulting


-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 13824 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20160826/9f2a0933/attachment.bin>