Changes between Initial Version and Version 4 of Ticket #54


Ignore:
Timestamp:
Dec 19, 2010 7:21:59 AM (4 years ago)
Author:
tboeckel
Comment:

I think the most important point is to check here is why YAM is trying to recreate the index at all. Is it just because the dates of the folder and the .findex file were altered and thus YAM thinks the index is outdated/corrupted or is there a another reason? Or is it because the backed up index on the CD has an older version than YAM currently uses?

Second, how should YAM react in case a mail's state has to be changed (i.e. from "new/unread" to "read"? This requires write access to the disk or you will get tons of further "disk is write protected" requesters and the next time you start YAM the mails will have their old state. Although this must be acceptable.

One solution would be to either accept index files from read-only media as they are and never perform a rescan, but this would mean old mail backups cannot be used with future versions of YAM and a changed index file layout.

Doing the rescan once is no 100% solution either, as YAM will automatically flush unused indices from memory and reload them when necessary, but this would result in yet another rescan. In this case the index must be marked as "not flushable" to avoid the constant rescan. But this all only holds true as long as YAM is not restarted. After a restart the scan will be due again.

From my point of view it all comes down to one question: why is the index rebuilding necessary at all and can any logic inside YAM make this necessity more tolerable? The way YAM handles its mails simply requires a disk that can be written to.

Opinions?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #54

    • Property Status changed from new to pending
    • Property Severity changed from major to minor
    • Property Cc yamos-svn@… removed
    • Property Component changed from stable build to mail indexing
    • Property Priority changed from undecided to low
    • Property Milestone changed from to YAM 2.7

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • ojciec_swiety@…(Reporter)