pelican server cache chaos corrupt

pelican-server cache chaos corrupt

Flip bytes in a cached object’s block

Synopsis

Flip bytes in the on-disk (encrypted) representation of a block so that its authentication tag no longer validates. The cache detects this on the next cold read of the block or during the periodic data scan, which invalidates and re-fetches the object.

By default the latest cached version is targeted; use —etag or —instance to select a specific version.

Examples: pelican cache chaos corrupt pelican://my-federation/data/file.dat pelican cache chaos corrupt /data/file.dat —block 3 —bytes 32 pelican cache chaos corrupt —instance <hash> —block 0


pelican-server cache chaos corrupt <object-url> [flags]

Options


      --block uint32   Zero-based block number to corrupt
      --bytes int      Number of bytes to flip (default: the authentication-tag size)
  -h, --help           help for corrupt

Options inherited from parent commands


      --config string       config file (default is $HOME/.config/pelican/pelican.yaml)
  -d, --debug               Enable debug log messages
      --etag string         Select the object version by ETag (default: latest)
  -f, --federation string   Pelican federation to utilize
      --instance string     Select the object version by instance hash
      --json                Output in JSON format
  -L, --log string          Specified log output file
  -t, --token string        Path to admin token file (auto-generated if not provided)
      --version             Print the version and exit