files:scan --path does not propagate the size #24271

Closed
nickvergessen opened this Issue Apr 26, 2016 · 3 comments

Projects

None yet

3 participants

@nickvergessen
Contributor
nickvergessen commented Apr 26, 2016 edited

Steps

  1. Create empty folder in the UI: test/test1/test2/
  2. Enter test/test1/test2/ in the UI
  3. cp a file into data/admin/files/test/test1/test2
  4. Run ./occ files:scan --path="/admin/files/test/test1/test2"

Expected

Size of all folders should not be 0:

  • test/
  • test/test1/
  • test/test1/test2/

Actually

  • test/ = 0
  • test/test1/ = 0
  • test/test1/test2/ > 0

Confirmed on 8.2.3 and master

@PVince81 PVince81 added this to the 9.1-current milestone Apr 26, 2016
@PVince81
Collaborator

@nickvergessen did the etag propagate at least or did it also stop at the requested path ?

Because I can imagine some people using --path for the files:scan workaround for external storages, and use the path option to avoid rescanning everything fully and limit it to their external storages.

@PVince81
Collaborator
@nickvergessen
Contributor

on my 8.2.3 installation at least the mtime got propagated to test and test/test1, I didn't note down the etag, so not sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment