Unmounting

To unmount an S3QL file system, use the command:

umount.s3ql [options] <mountpoint>

This will block until all data has been written to the backend.

Only the user who mounted the file system with mount.s3ql is able to unmount it again. If you are root and want to unmount an S3QL file system mounted by an ordinary user, you have to use the fusermount -u or umount command instead. Note that these commands do not block until all data has been uploaded, so if you use them instead of umount.s3ql then you should manually wait for the mount.s3ql process to terminate before shutting down the system.

The umount.s3ql command accepts the following options:

-z, --lazy

Lazy umount. Detaches the file system immediately, even if there are still open files. The data will be uploaded in the background once all open files have been closed.

--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.

If, for some reason, the umount.s3ql command does not work, the file system can also be unmounted with fusermount -u -z. Note that this command will return immediately and the file system may continue to upload data in the background for a while longer.