[ 
https://issues.apache.org/jira/browse/HDDS-15927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siyao Meng updated HDDS-15927:
------------------------------
    Description: 
Formal verification for Ozone snapshot lifecycle
h3. Coverage (Specula campaign ozone-9fbf9ee)
Run environment: Ozone 9fbf9ee0cb1bd2f5f5d437b6719ebbe5309351fb, Specula v1.1.0 
(c6aa3dfa), claude-code Claude Opus 4.8.
||Target||Effort||Guidance||Result||
|om-snapshot-gc|high|{{campaigns/ozone-9fbf9ee/targets/008-om-snapshot-gc/.prompt-extra.md}}|1
 reproduced High, 1 masked Critical|
|om-snapshot-defrag|high|{{campaigns/ozone-9fbf9ee/targets/011-om-snapshot-defrag/.prompt-extra.md}}|No
 findings|

h3. Bugs (link via "Testing discovered")
* (REPRODUCED, High) HDDS-16464: an unfenced deep clean flag write clobbers the 
purge driven reset, so a snapshot is skipped by the deep clean and its 
reclaimable deleted keys are stranded for its retention. [om-snapshot-gc MC-1]
* (MASKED, Critical) HDDS-16465: a non atomic dual chain update or restart 
rebuild could give a surviving snapshot a different effective previous and 
misdirect the adjacency reclaim filter, currently masked. [om-snapshot-gc CR-4]

  was:Formal verification for Ozone snapshot lifecycle


> Formal verification for Ozone snapshot lifecycle
> ------------------------------------------------
>
>                 Key: HDDS-15927
>                 URL: https://issues.apache.org/jira/browse/HDDS-15927
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Siyao Meng
>            Assignee: Siyao Meng
>            Priority: Major
>
> Formal verification for Ozone snapshot lifecycle
> h3. Coverage (Specula campaign ozone-9fbf9ee)
> Run environment: Ozone 9fbf9ee0cb1bd2f5f5d437b6719ebbe5309351fb, Specula 
> v1.1.0 (c6aa3dfa), claude-code Claude Opus 4.8.
> ||Target||Effort||Guidance||Result||
> |om-snapshot-gc|high|{{campaigns/ozone-9fbf9ee/targets/008-om-snapshot-gc/.prompt-extra.md}}|1
>  reproduced High, 1 masked Critical|
> |om-snapshot-defrag|high|{{campaigns/ozone-9fbf9ee/targets/011-om-snapshot-defrag/.prompt-extra.md}}|No
>  findings|
> h3. Bugs (link via "Testing discovered")
> * (REPRODUCED, High) HDDS-16464: an unfenced deep clean flag write clobbers 
> the purge driven reset, so a snapshot is skipped by the deep clean and its 
> reclaimable deleted keys are stranded for its retention. [om-snapshot-gc MC-1]
> * (MASKED, Critical) HDDS-16465: a non atomic dual chain update or restart 
> rebuild could give a surviving snapshot a different effective previous and 
> misdirect the adjacency reclaim filter, currently masked. [om-snapshot-gc 
> CR-4]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to