Subject Re: [firebird-support] gfix questions
Author Markus Ostenried
On 12/21/06, Ann W. Harrison <aharrison@...> wrote:
> Markus Ostenried wrote:
> > On 12/20/06, heineferreira <heineferreira@...> wrote:
> >> I haven't had a corrupt firebird database....
> >
> > Other reasons include faulty RAM, defunct disk drives, and running out
> > of disk space.
> Bad RAM possibly, dead disk drives certainly, but running out
> of disk space will not be a problem if you have forced writes
> on. Forced writes causes pages to be written in careful order
> so each write leaves the database in a consistent state.

That makes sense to me, didn't think of it though.

> > One of the most nasty ways would be to hit the file
> > size limit - most likely the 2gb/4gb limit on a 32bit file system
> That isn't a problem on any Firebird version. We use 64bit file
> I/O. InterBase 5.6 would happily write over the front of the file,
> but it's eight years old and should be retired.

I've started with using IB 5.x, I guess I'm still sensitive to old
problems from that times :)
So the old problem was with something like a page number overflowing
and restarting from the beginning, but only on 32bit file systems?

Thanks for the clarifications, Ann.