Subject | Database Corrupted Due to Zero Disk Space |
---|---|
Author | Christian Gütter |
Post date | 2009-04-01T16:17:49Z |
Hi everyone,
I have got a problem with a corrupted Firebird 1.5 database
which is about 2 GB in size.
The database server ran out of disk space and due to that,
the database became corrupted.
The error in the server log file was the following:
DB (Server) Thu Mar 26 11:11:03 2009
Database: D:\DATABASES\DB.FDB
I/O error for file "D:\DATABASES\DB.FDB"
Error while trying to read from file
Reached the end of the file.
internal gds software consistency check (error during savepoint backout (290))
When I tried to validate or mend the database, I got the following errors first:
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279368 (sequence 74339) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279369 (sequence 74340) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279372 (sequence 74341) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279373 (sequence 74342) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279374 (sequence 74343) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279377 (sequence 74344) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279378 (sequence 74345) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279379 (sequence 74346) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279382 (sequence 74347) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279383 (sequence 74348) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279385 (sequence 74349) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:46 2009
Database: D:\DATABASES\DB.FDB
Index 1 is corrupt on page 133462 in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:46 2009
Database: D:\DATABASES\DB.FDB
Index 1 is corrupt on page 133462 in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:46 2009
Database: D:\DATABASES\DB.FDB
Index 1 is corrupt on page 133462 in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:48 2009
Database: D:\DATABASES\DB.FDB
Index 1 is corrupt on page 279381 in table T$_LOG_COLUMNS (135)
After that, the following error is repeated endlessly with different
page numbers:
DB (Server) Thu Mar 26 12:04:48 2009
Database: D:\DATABASES\DB.FDB
Page 256759 doubly allocated
After six hours, I stopped GFix, after the server log file had grown
to more than 7 GB.
Has anyone of you made some experience with this problem? Would it
make sense to let GFix run longer, or is it caught up in an endless
loop (on the IBSurgeon site, I read that the GFix process never
finishes in this case).
Any information would be very appreciated.
Regards,
Christian
I have got a problem with a corrupted Firebird 1.5 database
which is about 2 GB in size.
The database server ran out of disk space and due to that,
the database became corrupted.
The error in the server log file was the following:
DB (Server) Thu Mar 26 11:11:03 2009
Database: D:\DATABASES\DB.FDB
I/O error for file "D:\DATABASES\DB.FDB"
Error while trying to read from file
Reached the end of the file.
internal gds software consistency check (error during savepoint backout (290))
When I tried to validate or mend the database, I got the following errors first:
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279368 (sequence 74339) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279369 (sequence 74340) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279372 (sequence 74341) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279373 (sequence 74342) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279374 (sequence 74343) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279377 (sequence 74344) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279378 (sequence 74345) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279379 (sequence 74346) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279382 (sequence 74347) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279383 (sequence 74348) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:23 2009
Database: D:\DATABASES\DB.FDB
Data page 279385 (sequence 74349) is confused in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:46 2009
Database: D:\DATABASES\DB.FDB
Index 1 is corrupt on page 133462 in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:46 2009
Database: D:\DATABASES\DB.FDB
Index 1 is corrupt on page 133462 in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:46 2009
Database: D:\DATABASES\DB.FDB
Index 1 is corrupt on page 133462 in table T$_LOG_COLUMNS (135)
DB (Server) Thu Mar 26 12:04:48 2009
Database: D:\DATABASES\DB.FDB
Index 1 is corrupt on page 279381 in table T$_LOG_COLUMNS (135)
After that, the following error is repeated endlessly with different
page numbers:
DB (Server) Thu Mar 26 12:04:48 2009
Database: D:\DATABASES\DB.FDB
Page 256759 doubly allocated
After six hours, I stopped GFix, after the server log file had grown
to more than 7 GB.
Has anyone of you made some experience with this problem? Would it
make sense to let GFix run longer, or is it caught up in an endless
loop (on the IBSurgeon site, I read that the GFix process never
finishes in this case).
Any information would be very appreciated.
Regards,
Christian