Hi;
I'm having a problem using DBM files with my Alpha running DU 3.2G. The
DBM files themselves work fine, however, what really are small files show
up like this:
-rw-rw-r-- 1 erik users 14367697424384 Aug 30 17:30 mydbm.pag
-rw-rw-r-- 1 erik users 1753870336 Aug 24 18:59 mydbm.dir
Now, as you can imagine, my drive isn't quite (even close to) that big, so
the file definitly isn't. :)
I heard a rumor that there is a documented DU bug concerning this, but
could not find any information about it anywhere. Has anyone else
experienced this as well? Is there a patch available for this? If not,
anyone have a good way to manipulate these files? They can not be copied,
tarred, gzip'ed, etc. because the utilities all think the file is really
this large, and just keep writing out until the disk is full. The only
successful method I have found so far it to write a perl script to do a
dbmopen, read everything into a hash, and write it all back out to a plain
text file. Then once moved, I have another script to read it all back
in to a dbm. (to give you an idea of how big the example file really is,
once converted to plaintext, it was only ~500K.)
Note: I don't know if this makes a difference, but this is an ADVfs
filesystem.
Thanks very much in advance,
Erik
--
Erik M. Beebe Infinet
Publishing Systems Administration Phone: (757) 664-2227
Email: ebeebe_at_infi.net http://www.infi.net
Received on Mon Aug 31 1998 - 15:41:00 NZST