Subject | AW: [firebird-support] Re: FB 2.1.4 (vlad) crached (frozen fb_inet_server.exe and index corrupted) |
---|---|
Author | Steffen Heil |
Post date | 2010-04-05T13:46:26Z |
Hi
How can you be sure?
index could be corrupt ?
Though it could be a bug in firebird, I would rule out a lot of different
things first.
You already noted that you are using classic on windows 2008 R2. Can you
give more information of your environment?
- 32 or 64 bit server?
- some special memory settings?
And some details about your storage:
- is there antirvirus software?
- is there backup software?
- is there any type of raid?
- have you tested your hard drives for failures? read s.m.a.r.t. values?
Basically is firebird really the only process accessing that database file?
- What is your file extension?
- Are there active volume shadow copies?
- Is the database file on a local folder that is shared? (even if not used?)
- Have you tried to disabled the administrative share of the drive
containing the database?
Regards,
Steffen
[Non-text portions of this message have been removed]
> it's not our compoment (UIB) that can cause the probleme or it's a bug inthe fbclient.dll !
How can you be sure?
> this problem is very (very) serious ! the stability of all the firebird iscompromise.... how can we use a 24*24 database engine when every xx days the
index could be corrupt ?
Though it could be a bug in firebird, I would rule out a lot of different
things first.
You already noted that you are using classic on windows 2008 R2. Can you
give more information of your environment?
- 32 or 64 bit server?
- some special memory settings?
And some details about your storage:
- is there antirvirus software?
- is there backup software?
- is there any type of raid?
- have you tested your hard drives for failures? read s.m.a.r.t. values?
Basically is firebird really the only process accessing that database file?
- What is your file extension?
- Are there active volume shadow copies?
- Is the database file on a local folder that is shared? (even if not used?)
- Have you tried to disabled the administrative share of the drive
containing the database?
Regards,
Steffen
[Non-text portions of this message have been removed]