Skip to content

Transfer ownership only analyze home storage - #26533

Merged
DeepDiver1975 merged 1 commit into
masterfrom
transferownership-extstoragefix
Nov 7, 2016
Merged

Transfer ownership only analyze home storage#26533
DeepDiver1975 merged 1 commit into
masterfrom
transferownership-extstoragefix

Conversation

@PVince81

@PVince81 PVince81 commented Nov 2, 2016

Copy link
Copy Markdown
Contributor

Description

Don't recurse into any mount points when analyzing, only stay on home storage.

Related Issue

Fixes #26530

Motivation and Context

When transferring ownership, only the local files will be transferred
during the rename operation. This means that the analyzing code doesn't
need to recurse into any mount points.

Furthermore this fixes issues where FailedStorage might appear as mount
points as a result of inaccessible external storages or shares. So this
makes it more robust.

This can also make the transfer faster by not exploring external storages which won't be transferred anyway.

How Has This Been Tested?

See steps in original ticket.
Also tested with WND storages in "user provided" mode which used to fail with similar messages.

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Backports

  • stable9.1
  • stable9

When transferring ownership, only the local files will be transferred
during the rename operation. This means that the analyzing code doesn't
need to recurse into any mount points.

Furthermore this fixes issues where FailedStorage might appear as mount
points as a result of inaccessible external storages or shares. So this
makes it more robust.
@PVince81 PVince81 added this to the 9.2 milestone Nov 2, 2016
@mention-bot

Copy link
Copy Markdown

@PVince81, thanks for your PR! By analyzing the history of the files in this pull request, we identified @DeepDiver1975, @nickvergessen and @LukasReschke to be potential reviewers.

@davitol

davitol commented Nov 3, 2016

Copy link
Copy Markdown
Contributor

👍 WFM

@DeepDiver1975

Copy link
Copy Markdown
Member

👍

@DeepDiver1975
DeepDiver1975 merged commit 01feb74 into master Nov 7, 2016
@DeepDiver1975
DeepDiver1975 deleted the transferownership-extstoragefix branch November 7, 2016 12:14
@DeepDiver1975

Copy link
Copy Markdown
Member

@PVince81 backport as well?

@PVince81

PVince81 commented Nov 7, 2016

Copy link
Copy Markdown
Contributor Author

stable9.1: #26566
stable9: #26565

elie195 pushed a commit to elie195/core that referenced this pull request Mar 23, 2017
When transferring ownership, only the local files will be transferred
during the rename operation. This means that the analyzing code doesn't
need to recurse into any mount points.

Furthermore this fixes issues where FailedStorage might appear as mount
points as a result of inaccessible external storages or shares. So this
makes it more robust.
@lock

lock Bot commented Aug 4, 2019

Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock Bot locked as resolved and limited conversation to collaborators Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Transfer ownership fails if storage exists with user password

4 participants