S3QL_VERIFY(1)

✨ S3QL_VERIFY(1) ✨

okay bestie, welcome to the s3ql_verify page of the S3QL manual 💖 (that's section 1 of the S3QL docs, for the girlies keeping track)

🌸 NAME 🌸

s3ql_verify — verify the data in an S3QL file system 👑

---

🦋 SYNOPSIS 🦋

s3ql_verify [options] <storage url>

---

💅 DESCRIPTION 💅

S3QL is a file system for online data storage. Before you go using S3QL, pls pls pls consult the full documentation — not just the man pages, because these man pages only briefly document the available userspace commands. iykyk 🫶

The s3ql_verify command verifies all the data in the file system. And here's the tea: unlike fsck.s3ql, s3ql_verify does not trust the object listing that the backend hands back to it. Nope. It actually goes and tries to retrieve every single object. Which means... it takes a lot longer. like, a lot longer. no cap 😭

The format of <storage url> depends on the backend you're using. Consult the S3QL User's Guide for a description of the available backends 💜

---

✨ OPTIONS ✨

The s3ql_verify command accepts the following options:

• --log <target> — where your log messages go. Say none for standard output, or syslog for the system logging daemon. Anything else gets interpreted as a file name. Log files get rotated when they hit 1 MiB, and at most 5 old log files are kept. Default: None
• --debug-modules <modules> — turn on debugging output from the modules you name (use commas to separate multiple modules, or 'all' for everything). Debug messages get written to whatever target you set with the --log option.
• --debug — turn on debugging output from all S3QL modules. Debug messages go to the target specified by the --log option.
• --quiet — be really quiet 🤫
• --version — just print the program version and exit, that's it, that's the whole job
• --cachedir <path> — store cached data in this directory (default: ~/.s3ql)
• --backend-options <options> — backend-specific options (separate them with commas). See the backend documentation for what options exist.
• --authfile <path> — read authentication credentials from this file (default: ~/.s3ql/authinfo2)
• --missing-file <name> — file to store the keys of missing objects in.
• --corrupted-file <name> — file to store the keys of corrupted objects in.
• --data — read every object completely, instead of checking just the metadata. thorough queen energy 🔥
• --parallel PARALLEL — number of connections to use in parallel.
• --start-with <n> — skip over the first <n> objects, and start verifying with object <n>+1.

---

🎀 EXIT CODES 🎀

s3ql_verify may terminate with the following exit codes:

• 0 — Everything went well. slay ✨
• 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.
• 11 — No such backend.
• 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. 😭 not the corrupted objects

---

🌈 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 🧚

---

👑 COPYRIGHT 👑

© 2008 Nikolaus Rath <Nikolaus@rath.org>

---

that's the whole page bestie, you ate 💖 this was S3QL version 5.2.3, dated Nov 02, 2024 — go verify those objects, mwah 🫶✨