Bug 233415 - 12.0-RC1 - sysutils/fusefs-exfat broken on 12.x
Summary: 12.0-RC1 - sysutils/fusefs-exfat broken on 12.x
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.0-STABLE
Hardware: Any Any
: --- Affects Many People
Assignee: samm
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2018-11-22 22:16 UTC by vermaden
Modified: 2019-08-08 20:55 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vermaden 2018-11-22 22:16:39 UTC
Below is the problem shown.

The sysutils/fusefs-exfat worked like a charm on 11.2-RELEASE.


# mkdir -p /media/da0

# mount.exfat -o noatime -o uid=1000 -o gid=1000 -o dmask=022 -o fmask=133 -o noatime /dev/da0 /media/da0
FUSE exfat 1.2.8

# mount
sys/ROOT/12.0-RC1 on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
linprocfs on /compat/linux/proc (linprocfs, local)
tmpfs on /compat/linux/dev/shm (tmpfs, local)
local/home on /home (zfs, local, noatime, nfsv4acls)
local/usr/obj on /usr/obj (zfs, local, noatime, nfsv4acls)
local/usr/ports on /usr/ports (zfs, local, noatime, nfsv4acls)
local/usr/src on /usr/src (zfs, local, noatime, nfsv4acls)
local/var/cache/pkg on /var/cache/pkg (zfs, local, noatime, nfsv4acls)
/dev/fuse on /media/da0 (fusefs, local, noatime, synchronous)

# ls /media 
ls: da0: No such file or directory

# ls /media/da0
ls: /media/da0: No such file or directory

# umount /media/da0 

# ls /media 
da0
Comment 1 vermaden 2018-11-23 07:15:35 UTC
Maybe its not only sysutils/fusefs-exfat problem but a 'general' FUSE problem on 12.x ...
Comment 2 Alan Somers freebsd_committer 2019-01-02 22:06:57 UTC
I doubt it's a general fuse problem.  Assigning to port maintainer.
Comment 3 Conrad Meyer freebsd_committer 2019-01-02 22:25:38 UTC
fusefs-exfat port has not changed since the 11.2 release date.  I doubt it is the port.
Comment 4 Alan Somers freebsd_committer 2019-01-02 22:37:15 UTC
But many FS-related data structures changed with 12.0.  My gut instinct is that fusefs-exfat is making some kind of assumption that was valid on 11.2 but not 12.0.  I don't know what, though.  But I know that other fuse filesystems aren't having this problem on 12.0.
Comment 5 Conrad Meyer freebsd_committer 2019-01-02 22:51:06 UTC
(In reply to Alan Somers from comment #4)
Sure, it's possible.
Comment 6 Conrad Meyer freebsd_committer 2019-01-02 22:55:01 UTC
@vermaden, maybe this is a dumb question, but did you upgrade an 11.2 system to 12.0 and not update the installed fusefs-exfat port?
Comment 7 Conrad Meyer freebsd_committer 2019-01-02 23:07:18 UTC
Also, does exfat print anything on stderr if you use 'debug'?
Comment 8 Conrad Meyer freebsd_committer 2019-01-02 23:13:31 UTC
I am not able to reproduce this myself on 13-CURRENT with a filesystem created by mkfs.exfat, but it's possible it is somewhat different from an organic exfat filesystem image.
Comment 9 Conrad Meyer freebsd_committer 2019-01-02 23:14:35 UTC
(In reply to Conrad Meyer from comment #7)
Oops, it isn't a standard mount.fuse.  Uh, if you use '-d'.
Comment 10 vermaden 2019-01-03 08:32:12 UTC
(In reply to Conrad Meyer from comment #6)
> @vermaden, maybe this is a dumb question, but did you upgrade an 11.2 system to 12.0 and not update the installed fusefs-exfat port?

Nope. I made update with freebsd-update and then the first next thing was pkg upgrade for all packages.
Comment 11 Conrad Meyer freebsd_committer 2019-01-03 20:50:41 UTC
(In reply to vermaden from comment #10)
Can you try mount.exfat -d flag?  Is the filesystem image small enough / not containing personal information that you could share it with myself or Alan to try to debug?  Thanks.
Comment 12 Alan Somers freebsd_committer 2019-08-08 20:55:23 UTC
Please retest on current using the latest build (Aug-8 or later)