The s3ql_verify command¶
Synopsis¶
s3ql_verify [options] <storage url>
Description¶
The s3ql_verify command verifies all data in the file system. In contrast to fsck.s3ql, s3ql_verify does not trust the object listing returned by the backend, but actually attempts to retrieve every object. It therefore takes a lot longer.
The format of <storage url> depends on the backend that is
used. The S3QL User’s Guide should be consulted for a description of
the available backends.
Options¶
The s3ql_verify command accepts the following options.
- --authfile <path>
Read authentication credentials from this file (default: /home/nikratio/.s3ql/authinfo2).
- --cachedir <path>
Store cached data in this directory (default: /home/nikratio/.s3ql).
- --backend-options <options>
Backend specific options (separate by commas). See backend documentation for available options.
- --missing-file <name>
File to store keys of missing objects. [default: missing_objects.txt]
- --corrupted-file <name>
File to store keys of corrupted objects. [default: corrupted_objects.txt]
- --data
Read every object completely, instead of checking just the metadata.
- --start-with <n>
Skip over first <n> objects and start verifying object <n>+1. [default: 0]
- --max-connections <no>
Maximum number of concurrent backend I/O operations (default: 32). This is independent of –max-threads, which governs compression.
- --max-threads <no>
Number of parallel compression/encryption threads to use (default: auto). This bounds CPU parallelism only and is independent of –max- connections.
- --log <target>
Destination for log messages. Specify ‘none’ for standard output or ‘syslog’ for the system logging daemon. Anything else is interpreted as a file name. Log files are rotated when they reach 1 MiB, keeping at most 5 old files.
- --debug
Activate debugging output from all S3QL modules. Debug messages are written to the destination given by –log.
- --debug-modules <module>
Activate debugging output from the named module. May be given multiple times; use ‘all’ for everything. Debug messages are written to the destination given by –log.
- --quiet
be really quiet
- --install-completion
Install completion for the current shell.
- --show-completion
Show completion for the current shell, to copy it or customize the installation.
- --help
Show this message and exit.
Exit Codes¶
s3ql_verify may terminate with the following exit codes:
- 0:
Everything went well.
- 1:
An unexpected error occurred. This may indicate a bug in the program.
- 2:
Invalid command line argument or configuration file key.
- 3:
Invalid backend option.
- 10:
Could not open log file for writing.
- 12:
Authentication file has insecure permissions.
- 13:
Unable to parse proxy settings.
- 14:
Invalid credentials (Authentication failed).
- 15:
No permission to access backend (Authorization denied).
- 16:
Invalid storage URL, specified location does not exist in backend.
- 17:
Wrong file system passphrase.
- 18:
No S3QL file system found at given storage URL.
- 19:
Unable to connect to backend, can’t resolve hostname.
- 32:
Unsupported file system revision (too old).
- 33:
Unsupported file system revision (too new).
- 45:
Unable to access cache directory.
- 46:
The file system data was verified, and some objects were found to be missing or corrupted.
See Also¶
The S3QL homepage is at https://github.com/s3ql/s3ql/.
The full S3QL documentation should also be installed somewhere on your
system, common locations are /usr/share/doc/s3ql or
/usr/local/doc/s3ql.