### Navigation

- next
- previous |
- S3QL 1.14 documentation »

# Checking for Errors

If, for some reason, the filesystem has not been correctly unmounted, or if you suspect that there might be errors, you should run the `fsck.s3ql` utility. It has the following syntax:

    fsck.s3ql [options] <storage url>

This command accepts the following options:

> `--log <target>` | Write logging info into this file. File will be rotated when it reaches 1 MiB, and at most 5 old log files will be kept. Specify `none` to disable logging. Default: `~/.s3ql/fsck.log`
> `--cachedir <path>`
> | Store cached data in this directory (default: `~/.s3ql)` (default: /home/nikratio/.s3ql)
> `--authfile <path>`
> | Read authentication credentials from this file (default: `~/.s3ql/authinfo2)` (default: /home/nikratio/.s3ql/authinfo2)
> `--debug <module>`
> | activate debugging output from <module>. Use `all` to get debug messages from all modules. This option can be specified multiple times. (default: None)
> `--quiet` | be really quiet (default: False)
> `--ssl` | Always use SSL connections when connecting to remote servers. For backends that allow only encrypted connections, S3QL uses SSL automatically, even if this option is not set. (default: False)
> `--version` | just print program version and exit
> `--batch` | If user input is required, exit without prompting. (default: False)
> `--force` | Force checking even if file system is marked clean. (default: False)

### Navigation

- next
- previous |
- S3QL 1.14 documentation »