mount fails with file system subtypes set

[mapi]

This is work

mount -t gcsfuse -o rw,user my-bucket /mnt/mybucket

These are not work.

mount -t fuse -o rw,user gcsfuse#my-bucket /mnt/mybucket
mount -t fuse.gcsfuse -o rw,user my-bucket /mnt/mybucket

mount can use another way. but these command return gcsfuse error.

Error: gcsfuse takes exactly two arguments.

NAME:
   gcsfuse - Mount a GCS bucket locally

USAGE:
   gcsfuse [global options] bucket mountpoint

[snip]

I met this problem while using chef.
Chef's mount function support fuse, but use mount -t fuse -o rw,user gcsfuse#my-bucket /mnt/mybucket idiom.

[jacobsa]

Thanks for the report. I'm not familiar with Chef; can you provide a link?

[jacobsa]

After some Googling, I assume you're referring to this Chef. In particular, here are the docs on mounting.

Can you share your Chef configuration that is causing this problem? It seems like you must have provided the string fuse or fuse.gcsfuse somewhere. If you set fstype to gcsfuse it seems like this would just work?

[mapi]

My small config is here.

mount "/mnt/my-bucket" do
  device "gcsfuse#my-bucket"
  fstype "fuse"
  options "rw,user"
  action [:mount, :enable]
end

without fstype "fuse", Chef check device "my-bucket" is exist.
This makes "Device my-bucket does not exist" error. (Chef's issue)

mount "/mnt/my-bucket" do
  device "my-bucket"
  fstype "fuse.gcsfuse"  # also fstype "gcsfuse"
  options "rw,user"
  action [:mount, :enable]
end

Of course, Chef should skip the device check if fstype is gcsfuse. but there is already generic way to skip check.

And I found man mount(8) after this issue created.

The programs mount and umount support filesystem subtypes. The subtype is defined by a '.subtype' suffix.
For example 'fuse.sshfs'. It's recommended to use subtype notation rather than add any prefix to the mount source (for example 'sshfs#example.com' is deprecated).

support mount with subtypes improve compatibility.

[jacobsa]

To confirm, I believe you're saying that the following doesn't work because Chef gets in the way:

mount "/mnt/my-bucket" do
  device "my-bucket"
  fstype "gcsfuse"
  options "rw,user"
  action [:mount, :enable]
end

This should work; mount -t gcsfuse my-bucket /mnt/my-bucket is totally valid. Have you reported the bug to Chef?

That said, it does make sense to ensure subtypes work, for the reasons described in torvalds/linux@79c0b2d. I'll look into it.

[jacobsa]

For the record, I can reproduce this on Ubuntu 15.04 with the following line in /etc/fstab:

jacobsa-standard-asia /home/jacobsa/mp fuse.gcsfuse rw,noauto,user

[jacobsa]

@mapi: Could you confirm that the following causes this to work for you?

sudo ln -s /sbin/mount.gcsfuse /sbin/mount.fuse.gcsfuse

[mapi]

On Debian 8.1(jessie)

after create symlink.

mount -t fuse.gcsfuse -o rw,user my-bucket /mnt/mybucket
This works fine.

mount -t fuse -o rw,user gcsfuse#my-bucket /mnt/mybucket
This return error.

Error: gcsfuse takes exactly two arguments.

NAME:
   gcsfuse - Mount a GCS bucket locally

USAGE:
   gcsfuse [global options] bucket mountpoint

VERSION:
   0.10.0 (commit 2cda84d)
[snip]

[jacobsa]

Thanks. Right, I haven't added support for the deprecated version. Will make a release that adds support for the modern version soon.

[jacobsa]

Thanks again for the report. This should be fixed as of v0.11.0. @mapi: Could you update and confirm?

[mapi]

👏 great work. thank you.

[rshade]

@mapi how did you get this to work via chef?