* fix(fsck): inspect references to deleted volumes
* volume.fsck: treat every match-all collection filter as global
ALL_COLLECTIONS and EACH_COLLECTION compile to the same match-all
matcher as an empty filter or "*", but the string check treated them
as a restricted scope: a selected missing volume was rejected and
references to master-absent volumes were reported without being purged.
Use the compiled matcher instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume.fsck: purge an entry whose manifest is on a missing volume
A top-level chunk on a missing volume already proves the entry is
unreadable, whether or not its manifests resolve. Skipping such entries
kept the very case where the manifest needle sat on the retired volume,
and the remaining unresolved manifest then blocked every later orphan
purge. The missing-needle check on live volumes never had this gate, so
both paths now treat these entries the same. The warning now says only
orphan purging is disabled, which is the only thing the counter gates.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume.fsck: report a failed Filer delete
A rejected purge DELETE printed nothing unless -v was set, so the run
looked successful after "deleting path" while the entry stayed. The
filer answers 204 for an entry that is already gone, so only real
failures print.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume.fsck: tighten help text, comments and missing-volume tests
The help now wraps like the rest of it and says that a purge removes
the whole entry, including its chunks on other volumes. The live test
header no longer calls the run report-only, and the reverse-scan test
checks the report line for each missing chunk.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume.fsck: drop the missing-volume design notes
The notes said no destructive change was approved while the change adds
a confirmed purge, still described the dropped manifest gate, and
mostly recorded local runs and a reverse index that is not part of
this change. The operator contract lives in help volume.fsck.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume.fsck: allow a report-only missing-volume scan with -collection
The collection check exists to stop a purge that cannot be scoped, but
it also rejected a report-only run that deletes nothing. Apply it only
with -reallyDeleteFilerEntries, and limit the -confirmMissingVolumeDeletion
description to the -volumeId case it guards.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume.fsck: count only a 2xx answer as a purged entry
A redirect the client could not follow left the entry in place but was
recorded as deleted, which also queued its parent for empty-directory
cleanup.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume.fsck: say that a filtered purge of a missing -volumeId is refused
The help and the early warning both said a purge with -collection only
reports references to unlisted volumes, but a -volumeId naming one is
rejected before the scan. The help now says so, and the warning prints
after that check, so a refused run no longer claims it will report.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: MZ01-CHOIMINSU <mz01-juwannam@MZ01-CHOIMINSU.local>
Co-authored-by: Chris Lu <chrislusf@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
