Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database often became corrupted after an out of disk space condition [CORE1228] #1652

Closed
firebird-automations opened this issue Apr 25, 2007 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

Relate to CORE1469

Firebird allocated new pages in buffer cache only. They go to disk some time later - usually at commit. If disk is full many newly allocated pages can't be written. This is often leads to corruption.
Proposed solution is to write page to disk immediately after it is allocated. This guarantees that only one page can't be written in case of disk full condition and allow to gracefully handle this error

Commits: 44c11df 31af74f

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue relate to CORE1469 [ CORE1469 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11940 ] => Firebird [ 15382 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment