cli version: 1.3.0

fsck <metaurl>

fsck <metaurl> --path <path> -r

I found that fsck with path or without path works differently. When without --path fsck check entire my storage and checking missing slices, but if I know which file is problematic and use --path to check it directly, it does not really do the job.

Is there any reason that --path cannot checking the missing slices? I certainly don't want to fsck entire storage every time when I just want to check a few directories.