UMOUNT.S3QL(1)

πŸ’« UMOUNT.S3QL(1) πŸ’«

okay bestie, welcome to the umount.s3ql manual page, part of the S3QL manual set πŸ¦‹ this is the little command that says "bye babe" to your mounted S3QL file system, and she does it properly, which is more than some other tools can say πŸ‘‘


✨ NAME ✨

umount.s3ql β€” unmount an S3QL file system πŸ’…


🌸 SYNOPSIS 🌸

umount.s3ql [options] <mount point>

πŸŽ€ DESCRIPTION πŸŽ€

so, S3QL is a file system for online data storage ⭐ and like, before you go using S3QL at all, please please please consult the full documentation, not just the man pages β€” the man pages are giving "brief summary of the userspace commands" energy and nothing more, ok? πŸ’–

the umount.s3ql command unmounts the S3QL file system that's mounted in the directory mount point, and then it blocks until every last bit of data has been uploaded to the storage backend. no rushing her. she waits. patiently. periodt 🌈

also, important: only the user who mounted the file system with mount.s3ql is able to unmount it with umount.s3ql πŸ”’ that's the vibe. if you're root and you wanna unmount an S3QL file system that an ordinary user mounted, you have to use the fusermount -u or umount command instead.

🚨 but bestie listen β€” those commands do not block until all data has been uploaded. so if you use them instead of umount.s3ql, you should manually wait for the mount.s3ql process to terminate before shutting down the system. like, actually wait. don't just yank the power. πŸ’€

πŸ‘‘ OPTIONS πŸ‘‘

the umount.s3ql command accepts the following options 🫢

  • --log <target> β€” where your log messages go πŸ’Œ specify 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 will be kept. Default: None
  • --debug-modules <modules> β€” activate 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 gave --log.
  • --debug β€” activate debugging output from all S3QL modules πŸ”₯ debug messages get written to whatever target you gave --log.
  • --quiet β€” be really quiet 🀫
  • --version β€” just print program version and exit ✌️
  • --lazy, -z β€” 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.

πŸ’€ EXIT CODES πŸ’€

umount.s3ql may terminate with the following exit codes:

  1. 0 β€” everything went well 🌟 slay.
  2. 1 β€” an unexpected error occurred. this may indicate a bug in the program 😭
  3. 2 β€” invalid command line argument or configuration file key πŸ™ˆ

🌈 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 πŸŽ€


Β© 2008 Nikolaus Rath <Nikolaus@rath.org>


and that's the whole page, bestie!! this was S3QL version 5.2.3, dated Nov 02, 2024, from the UMOUNT.S3QL(1) manual β€” go forth and unmount responsibly πŸ’…βœ¨πŸ«Ά

πŸ“¦ where this page comes from