#843 Database Corruption on Delete

open
V3 (197)
5
2012-09-17
2010-02-15
Mark G.
No

File/Properties reports that database contains 246 entries over 24 groups (DB format v3.06). Four main groups are at the root.

After deleting a whole group from the root (three remaining), File/Properties reports that database contains 232 entries over 23 groups.

Upon File/Save, the fourth group that was deleted reappears in the tree, with its associated entries. Properties still report 234/23.

A further Delete/Save cycle makes the group reappear from deletion still, and Properties reporting 163/22.

Following cycles: 153/21, 149/20. Then the deleted root group did not reappear.

For obvious reasons I am not using this version of my database, I am only guessing this phenomenon is related to database corruption based on the visible symptoms.

Discussion

  • Rony Shapiro

    Rony Shapiro - 2010-02-15

    Hi Mark,

    Interesting. A couple of questions:
    1. With what version of PasswordSafe are you seeing this issue?
    2. Can you run the latest version (3.21) of PasswordSafe from the command line with the '-v' flag and the name of the database, e.g., "pwsafe.exe -v pwsafe.psafe3" and report what it found? (-v attempts to verify and repair the database)

    Cheers,

    Rony

     
  • Mark G.

    Mark G. - 2010-02-15

    Hi Rony, thanks again for your support.

    1. Version is 3.21.
    2. The report states 3 UUIDS repaired out of 246 processed entries. 0 in the other departments. Even after saving a clean version of this database (which passes the -v check), I can repeat the problem. FYI i repeated the problem on both Win7 (1) and XP (2) computers.

    Funny thing is I was trying to trim down my DB to send you a sanitized version to investigate merging issues (minidump produced). I was actually happy to see 3.21 had its merging functions improved and was eager to test them! It just occured to me the merging problems could be related to this possible DB corruption issue.

    I would have no problem attaching the aforementioned minidump (from the merging problem), but I'd like further reassurance that it contains no personal data. Let me know if you'd like to have it.

     
  • Mark G.

    Mark G. - 2010-02-16

    Password is "a", no quotes. Delete a root group, then save. Group is back.

     
  • Mark G.

    Mark G. - 2010-02-16

    Added a problematic database. The possible corruption issue repeats, however the database appears to merge with a copy with itself which could indicate this issue is unrelated to my merging issues.

    If I make a copy of this database, change one entry, then try to merge with the original I get the minidump failure.

     
  • Rony Shapiro

    Rony Shapiro - 2010-02-16

    Hi Mark,

    Thanks very much for the sanitized database. We're checking up a couple of ideas. No need for the minidump right now.

    Rony

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks