mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 19:01:57 -04:00
Updates some sync comments.
This commit is contained in:
parent
edb97c21d7
commit
d8689465a5
1 changed files with 4 additions and 1 deletions
5
sync.c
5
sync.c
|
|
@ -185,6 +185,9 @@ static int state_sync_process(struct snapraid_state* state, struct snapraid_pari
|
|||
|
||||
/* it could happens that all the blocks are EMPTY/BLK and CHG but with the hash */
|
||||
/* still matching because the specific CHG block was not modified. */
|
||||
/* Note that CHG/DELETED blocks already present in the content file loaded */
|
||||
/* have the hash cleared, and then they won't never match the hash. */
|
||||
/* We are treating only CHG blocks created at runtime. */
|
||||
/* In such case, we can avoid to update parity, because it would be the same as before */
|
||||
parity_needs_to_be_updated = 0;
|
||||
|
||||
|
|
@ -212,7 +215,7 @@ static int state_sync_process(struct snapraid_state* state, struct snapraid_pari
|
|||
/* get the block */
|
||||
block = disk_block_get(handle[j].disk, i);
|
||||
|
||||
/* if the block is new or removed, we have to update the parity */
|
||||
/* if the block is NEW or DELETED, we have to update the parity */
|
||||
/* to include this block change */
|
||||
if (!block_has_same_presence(block)) {
|
||||
parity_needs_to_be_updated = 1;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue