[GH-ISSUE #1321] Stop recommending `s3fs#bucketname` in fstab #707

New issue

Closed

opened 2026-03-04 01:48:05 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:48:05 +03:00

Owner

Originally created by @pxeger on GitHub (Jul 2, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1321

Details about issue

In the README and other bits of documentation, you recommend to use this format of fstab listing:

s3fs#bucketname /path/to/mountpoint fuse option1,option2 0 0

However, according to man 5 fstab, this is deprecated:

mount(8) and umount(8) support filesystem subtypes. The subtype is defined by '.subtype' suffix. For example 'fuse.sshfs'. It's recommended to use subtype notation rather than add any pre‐fix to the first fstab field (for example 'sshfs#example.com' is deprecated).

Instead you should use

bucketname /path/to/mountpoint fuse.s3fs option1,option2 0 0

Originally created by @pxeger on GitHub (Jul 2, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1321 ### Details about issue In the README and other bits of documentation, you recommend to use this format of `fstab` listing: ```none s3fs#bucketname /path/to/mountpoint fuse option1,option2 0 0 ``` However, according to [`man 5 fstab`](https://helpmanual.io/man5/fstab), this is deprecated: > mount(8) and umount(8) support filesystem subtypes. The subtype is defined by '.subtype' suffix. For example 'fuse.sshfs'. It's recommended to use subtype notation rather than add any pre‐fix to the first fstab field (for example 'sshfs#example.com' is deprecated). Instead you should use ```none bucketname /path/to/mountpoint fuse.s3fs option1,option2 0 0 ```