>>>> Attributes force write, no reserve

>>> Having "no reserve" isn't a good option for a regular read/write production database, because this basically prevents having back record versions on the same page as the primary record version, thus additional page reads are necessary.
>
>> Thanks Thomas!
>

OK, I figured out what happened.

If you restore just once using 'use all space', then the next time you backup/restore, it remembers that setting!

(I'm using FIBPlus's components, but I presume GBAK will do the same thing)

So now, I'm going to have to make sure I run GFIX after every restore, where 'use all space' has not been specified, to make sure it doesn't stay in that mode.