Dirstate breaks when updating disk with no free space
Bug #131111 reported by
Martin Albisetti
This bug report is a duplicate of:
Bug #98836: [MASTER] "OS locks must die" - dirstate file write locks exclude readers and limit portability.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
In Progress
|
High
|
Robert Collins |
Bug Description
Changes to dirstate when a drive is full can corrupt the dirstate, because the file is written to in-place rather than a new file being written; as such the updates can partially complete rather than only being enabled once successfully updated. A new way of storing/updating the dirstate is needed, and this is demonstrated in the attached branch.
Related branches
Changed in bzr: | |
status: | Triaged → Confirmed |
tags: | added: dirstate2 |
Changed in bzr: | |
status: | Confirmed → In Progress |
assignee: | nobody → Robert Collins (lifeless) |
description: | updated |
To post a comment you must log in.
It turns out I have the servers' hard drive full, and seem to provoke this.
I'm leaving it open because I'm not sure bzr should explode when running out of disk space :D