Opened 14 years ago
Last modified 11 years ago
#2132 closed defect
Datastore index corruption — at Initial Version
Reported by: | bernie | Owned by: | tomeu |
---|---|---|---|
Priority: | Urgent | Milestone: | Unspecified |
Component: | Sugar | Version: | Git as of bugdate |
Severity: | Blocker | Keywords: | dextrose, r+ |
Cc: | tch, alsroot | Distribution/OS: | Unspecified |
Bug Status: | Unconfirmed |
Description
Today we figured out one of the possibly many ways in which the index of the datastore can get corrupted in Sugar.
Here's an almost infallible recipe to reproduce it:
- open Write
- type something
- close Write
- wait a few seconds
- kill -9 the datastore process
- restart sugar (ctrl-alt-del)
Your saved entry is gone. It still takes up space on disk, but it's no longer visible until you rebuild the index.
Step 5 is just an artificial way to reproduce the problem. Other equally effective ways to trigger this data loss issue in the real-world include running out of battery, holding the power button for 4 seconds, and triggering the kernel out-of-memory killer.
Note: See
TracTickets for help on using
tickets.