> The problems I had with FS were very user-visible - whole folders went missing at the same
> time that we had massive POSKeyErrors, and they had to be laboriously restored from old
> backups. One of these occasions was likely caused by a long-since-fixed packing bug.
> The others, I have no idea whether the problems were ultimately caused by software issues,
> hardware issues (if so, there have never been any other visible problems on the same
> hardware, which has been up continuously for the past 40 months), or what.
Given the "changelog on the homepage",http://dirstorage.sourceforge.net , it seems safe to
say that DS has had some problems through its life, as well. FWIW, the only similar problems
*I* have seen have been due to application-level bugs (swallowed ConflictErrors), rather than
storage-level bugs. Tim's conclusion (all reported data-loss is due\ to hardware issues) goes
back at least to before ZODB 3.2.
> The problems I had with FS were very user-visible - whole folders went missing at the same
> time that we had massive POSKeyErrors, and they had to be laboriously restored from old
> backups. One of these occasions was likely caused by a long-since-fixed packing bug.
> The others, I have no idea whether the problems were ultimately caused by software issues,
> hardware issues (if so, there have never been any other visible problems on the same
> hardware, which has been up continuously for the past 40 months), or what.
Given the "changelog on the homepage",http://dirstorage.sourceforge.net , it seems safe to
say that DS has had some problems through its life, as well. FWIW, the only similar problems
*I* have seen have been due to application-level bugs (swallowed ConflictErrors), rather than
storage-level bugs. Tim's conclusion (all reported data-loss is due\ to hardware issues) goes
back at least to before ZODB 3.2.