workaround=all no more recognize using fuse in fstab

Bug #1898466 reported by Dash
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sshfs-fuse (Ubuntu)
New
Undecided
Unassigned

Bug Description

In Ubuntu 18.04 we had this line in fstab which was working well

sshfs#dh@keewin:Mes_documents/ /home/dh/Mes_documents/ fuse compression=yes,port=36022,user,,noatime,reconnect,workaround=all 0 0

After upgrade to 20.04 we get

dh@feijoa:~$ mount /home/dh/Mes_documents/
unknown workaround: 'all'

If we replace all by eg. none it's OK

dh@feijoa:~$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04

dh@feijoa:~$ sudo apt-cache policy sshfs
sshfs:
  Installé : 3.6.0+repack+really2.10-0ubuntu1
  Candidat : 3.6.0+repack+really2.10-0ubuntu1
 Table de version :
 *** 3.6.0+repack+really2.10-0ubuntu1 500
        500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: sshfs 3.6.0+repack+really2.10-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 4 17:38:13 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
InstallationDate: Installed on 2019-12-07 (301 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: sshfs-fuse
UpgradeStatus: Upgraded to focal on 2020-10-04 (0 days ago)

Revision history for this message
Dash (devel-tootai) wrote :
Revision history for this message
Stefano Panarese (nefast0) wrote :

Ubuntu 20.04 is shipped with sshfs version 3.6

If you check the changelog, they dropped support for `workaround=all` so you have to explicitly specify the workarounds you need.

See: https://github.com/libfuse/sshfs/blob/master/ChangeLog.rst#release-360-2019-11-03

Revision history for this message
Dash (devel-tootai) wrote :

This bug can be closed

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.