Claude
ade03ac6f3
Fix how chunk servers handle state updates from the metadata server based on the design in DESIGN.txt. The implementation now: 1. Checks if chunks in the add_list exist in the chunk store and collects any missing chunks 2. Unmarks chunks in the add_list that were previously marked for removal 3. Marks chunks in the rem_list for removal with timestamps 4. Responds with SUCCESS if all chunks are present, or ERROR with the list of missing chunks Added: - RemovalList data structure to track chunks marked for deletion with timestamps - chunk_store_exists() to check if a chunk file exists - Helper functions for removal list management (init, free, add, remove, find) This implements the garbage collection mechanism described in DESIGN.txt where chunks are marked for removal and can be unmarked if they appear in the add_list again.