Scanning a 100 Gb of data?

Is 300 Mb of memory sufficient to run a gallery2 scan of this size..?? I've tried the netpbm toolkit and imagemagick and gd (or whatever it's two letter name is) all 3 have crashed when I ran the scan..

I have data directory's as small as 10 Gb and 30 Gb and they seem to make it through the Gallery2 scan as far as I can tell but when I tackle 60 Gb+ gallery2 script crash's.. some expert admin's think it's a memory problem.. but I don't know.. When the crash happens I end up with incomplete data.. (some photo's done) other's never finished..

I have tried the debugging mode.. but I was unable to see any relevant errors messages as my scan crashed usually in the first 30 minutes..

Gallery URL = http://kilbournefamily.com/gallery23/main.php
Gallery version = 2.3 core 1.3.0
API = Core 7.54, Module 3.9, Theme 2.6, Embed 1.5
PHP version = 5.2.9 cgi-fcgi
Webserver = Apache
Database = mysqli 5.0.67-log, lock.system=flock
Toolkits = Exif, Thumbnail, NetPBM
Acceleration = none, none
Operating system = Linux 2.6.32.9-vs2.3.0.36.29.1 #2 SMP Tue Mar 2 11:07:49 PST 2010 x86_64
Default theme = matrix
gettext = enabled
Locale = en_US
Browser = Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)
Rows in GalleryAccessMap table = 7
Rows in GalleryAccessSubscriberMap table = 92107
Rows in GalleryUser table = 2
Rows in GalleryItem table = 92106
Rows in GalleryAlbumItem table = 1750
Rows in GalleryCacheMap table = 0