mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #1427] 1.87 - symlinks not working after remount #752
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#752
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cris-b on GitHub (Sep 29, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1427
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD
Version of s3fs being used (s3fs --version)
1.87
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.2
Kernel information (uname -r)
3.10.0-1127.18.2.el7.x86_64
GNU/Linux Distribution, if applicable (cat /etc/os-release)
NAME="Red Hat Enterprise Linux Server"
VERSION="7.8 (Maipo)"
When using 1.87:
create symlink
ls -l
lrwxrwxrwx. 1 crisb crisb 6 Sep 29 10:13 cristest -> data
unmount s3fs
mount s3fs
ls -l
lrwxrwxrwx. 1 crisb crisb 6 Sep 29 10:13 cristest ->
Rolling back to 1.86 solves the issue.
I'm only using _netdev, passwd_file and url parameters to mount.
@gaul commented on GitHub (Oct 10, 2020):
@ggtakec I bisected this to
1f796d432dbut this does not make sense to me. Any ideas?@ggtakec commented on GitHub (Oct 10, 2020):
@gaul This is a bug, I probably found its reason in code, please wait PR.
@gaul commented on GitHub (Oct 11, 2020):
Please test with the latest master.