Bug 1656826
Summary: | mv does not work on sshfs volumes (Numerical result out of range) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jean-Luc Richier <jean-luc.richier> |
Component: | fuse-sshfs | Assignee: | Peter Lemenkov <lemenkov> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | csaba, ddepaula, evan, igeorgex, joshua, lemenkov, scott, spam |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | fuse-sshfs-3.5.1-1.fc29 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-12 02:55:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jean-Luc Richier
2018-12-06 12:11:36 UTC
Same problem here 3 different F29 machines, await the update, thanks! +1 with this problem. Reason: Recently mv(1) got to the habit of attempting renameat2() syscall with flags. It's not expected to be supported by all fs backends; if some fs backend does not support flags, a fallback to standard renameat() is available. sshfs does not support flags, and thus it fails the rename if flags are passed. Intent is to fail with EINVAL which indicates to mv to go for the fallback. However, the signature of the errno is mistaken, and libfuse can't interpret the value it receives from sshfs_rename; hence it fails with ERANGE instead of EINVAL, which is bogus for mv, thus it gives up, reporting the ERANGE. (The bug was introduced in sshfs 3.0.0, but it got triggered only by the new mv behavior.) Fix: Upstream fixed the bug in sshfs 3.5.0: https://github.com/libfuse/sshfs/commit/6480b66 Can we get a fix for this? This is a rather crippling bug. Any change to get in the near future a new mv package to fix this bug? fuse-sshfs-3.5.1-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-200e6036d3 Came here to report this as a bug. Downloaded fuse-sshfs-3.5.1-1.fc29 and it does indeed fix the problem. Thank you! fuse-sshfs-3.5.1-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-200e6036d3 fuse-sshfs-3.5.1-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |