Hi,

A database with a shadow "crashed" due to insufficient disk space
for shadow. Here is the log excerpt:

/*******************/
adm (Server) Tue Nov 6 04:00:04 2001
INET/inet_error: select in packet_receive errno = 4

adm (Server) Tue Nov 6 04:00:04 2001
Database:
I/O error for file "/interbase/bak/abc.shd"
Error while trying to write to file
No space left on device

adm (Server) Tue Nov 6 04:00:04 2001
Database:
I/O error for file "/interbase/bak/abc.shd"
Error while trying to write to file
No space left on device

adm (Server) Tue Nov 6 04:59:23 2001
Database: /interbase/abc.gdb
internal gds software consistency check (root file name not
listed
for shadow (163))

adm (Server) Tue Nov 6 04:59:23 2001
shadow /interbase/bak/abc.shd deleted from database
/interbase/abc.gdb due to unavailabilit

adm (Server) Tue Nov 6 05:00:04 2001
Database: /interbase/bak/123.shd
I/O error for file "/interbase/bak/123.shd"
Error while trying to write to file
No space left on device
internal gds software consistency check (error during
savepoint
backout (290))
/*******************/

GFIX -v -n -f reports (only) orphan pages in database. The
questions is: Is it safe to remove these orphans, i.e. are these
pages benign or can contain data ? How to check that and what's
the best strategy for recovery in this situation ?

Best regards
Pavel Cisar