Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross-storage move doesn't properly update oc_mounts #25805

Closed
PVince81 opened this issue Aug 15, 2016 · 4 comments
Closed

Cross-storage move doesn't properly update oc_mounts #25805

PVince81 opened this issue Aug 15, 2016 · 4 comments

Comments

@PVince81
Copy link
Contributor

PVince81 commented Aug 15, 2016

Steps

  1. Create two users "user1" and "user2"
  2. Login as "user1"
  3. Create a folder "test"
  4. Share "test" with "user2"
  5. Login as "user2"
  6. Check oc_mounts and note the values of "storage_id" and "root_id" for the "test" folder for "user2"
  7. Login as admin
  8. Setup a SFTP external storage "/sftp", applicable for "user1" only
  9. Login as "user1"
  10. Move "test" to "/sftp", it becomes "/sftp/test"
  11. Login as "user2"
  12. Check oc_mounts

Expected result

The value of "storage_id" must change to match the new storage in which the "root_id" is on.

Actual result

"storage_id" still points at the home storage of "user1".
I didn't find any negative side-effects in regular OC use. However if some apps are using APIs to reverse-resolve storages based on oc_mounts, they will get wrong results.

Versions

v9.1.0

@PVince81 PVince81 added this to the 9.1.1 milestone Aug 15, 2016
@PVince81 PVince81 modified the milestones: 9.1.2, 9.1.1 Sep 21, 2016
@PVince81 PVince81 modified the milestones: 9.1.3, 9.1.2 Oct 20, 2016
@PVince81 PVince81 self-assigned this Nov 21, 2016
@PVince81 PVince81 modified the milestones: 9.1.4, 9.1.3 Nov 30, 2016
@PVince81 PVince81 modified the milestones: 9.1.5, 9.1.4 Feb 6, 2017
@PVince81 PVince81 modified the milestones: 9.1.6, 9.1.5 Apr 13, 2017
@PVince81 PVince81 modified the milestones: triage, 9.1.6 May 29, 2017
@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.

@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@stale
Copy link

stale bot commented Sep 21, 2021

This issue has been automatically closed.

@stale stale bot closed this as completed Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants