I caught wind of fscheck and fsrecover via a discussion on this list. A test run on a backup of the data.fs file gave some interesting results. The interesting parts of the output are included below. So, can someone tell me what this all means, and what I should do with it? Would swapping in the "recovered" data.fs result in data loss? I'm not really sure what fsrecover does, although I've seen it implied that its a good thing. Any advice or resources on the subject of proper data.fs handling and care would be wonderful. Edward ----- #> python ./fsrecover.py ../../../var/Data.fs ../../../var/Data.fs.rec Recovering ../../../var/Data.fs into ../../../var/Data.fs.rec exceptions.TypeError: len() of unsized object __main__.ErrorFound: invalid status, ^@ , at 58474904 ZODB.POSException.ConflictError: database conflict error (oid 0000000000001243, serial was 034a40dcb7aa3199, now 034a45d17cf00377) ZODB.POSException.ConflictError: database conflict error (oid 0000000000001243, serial was 034a40dcb7aa3199, now 034a45d17cf00377) ZODB.POSException.ConflictError: database conflict error (oid 0000000000001243, serial was 034a40dcb7aa3199, now 034a45d17cf00377) ZODB.POSException.ConflictError: database conflict error (oid 0000000000001243, serial was 034a40dcb7aa3199, now 034a45d17cf00377) ZODB.POSException.ConflictError: database conflict error (oid 0000000000001243, serial was 034a40dcb7aa3199, now 034a45d17cf00377) ZODB.POSException.ConflictError: database conflict error (oid 0000000000001243, serial was 034a40dcb7aa3199, now 034a45d17cf00377) __main__.ErrorFound: bad transaction length at 58815206 ZODB.POSException.ConflictError: database conflict error (oid 0000000000001243, serial was 034a40dcb7aa3199, now 034a45d17cf00377) __main__.ErrorFound: invalid status, ^@ , at 58822552 ZODB.POSException.ConflictError: database conflict error (oid 0000000000000e7f, serial was 034a4034f6f2c899, now 034a403593bb9522) ZODB.POSException.ConflictError: database conflict error (oid 0000000000000e7f, serial was 034a4034f6f2c899, now 034a403593bb9522) __main__.ErrorFound: invalid status, ^@ , at 58862947 ZODB.POSException.ConflictError: database conflict error (oid 0000000000000e8a, serial was 034a46e12a0b7fd5, now 034a46e3fa383855) ZODB.POSException.ConflictError: database conflict error (oid 0000000000000e7f, serial was 034a4034f6f2c899, now 034a403593bb9522) ZODB.POSException.ConflictError: database conflict error (oid 0000000000000e8a, serial was 034a46e12a0b7fd5, now 034a46e3fa383855) __main__.ErrorFound: bad transaction length at 62828071 ZODB.POSException.ConflictError: database conflict error (oid 0000000000001243, serial was 034a40dcb7aa3199, now 034a45d17cf00377) ZODB.POSException.ConflictError: database conflict error (oid 0000000000000002, serial was 034ab736a74f7619, now 034ab73a2152dbb3) ZODB.POSException.ConflictError: database conflict error (oid 0000000000000002, serial was 034ab736a74f7619, now 034ab73a2152dbb3) ZODB.POSException.ConflictError: database conflict error (oid 0000000000000002, serial was 034ab736a74f7619, now 034ab73a2152dbb3) 1948686 bytes removed during recovery