tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Subdirectories remain in magic-folder upload queue indefinitely #2924

New issue
Closed
opened 2018-05-14 01:18:24 +00:00 by cypher · 3 comments
cypher commented 2018-05-14 01:18:24 +00:00
Owner
Copy link

Subdirectories created inside of a magic-folder appear to remain in the magic-folder status upload queue indefinitely. Example:

dev ~ % tahoe magic-folder status -n TestFolder
Magic-folder status for 'TestFolder':
Local files:
  file.txt (5.21 MB): good, version=0, created 6 minutes ago
  subdir@_ (0 B): good, version=0, created 5 minutes ago
  subdir@_other_file.txt (965.85 kB): good, version=0, created 2 minutes ago

Remote files:
  admin's remote:
    file.txt (5.21 MB): good, version=0, created 6 minutes ago
    subdir@_ (0 B): good, version=0, created 5 minutes ago
    subdir@_other_file.txt (965.85 kB): good, version=0, created 2 minutes ago

Uploads:
  subdir/: 0.0% done

In this case, the subdir/: 0.0% done upload operation will persist in between client restarts (i.e., be re-added to the queue on startup but remain at "0.0% done" forever), regardless of the contents of that subdirectory and/or the ongoing upload/download progress of any of the files contained inside it.

As meejah has suggested, this may have something to do with the "flattening" behavior of magic-folder (which does not use standard/nested tahoe directories but instead lists all files within a magic-folder at the top-level of a mutable object using "@_" as a path separator). In any case, the correct behavior should probably either clear/remove this upload operation once "subdir" has been successfully created in the remote magic-folder, or keep the upload operation in the list for some amount of time but display it as being 100% done.

Subdirectories created inside of a magic-folder appear to remain in the `magic-folder status` upload queue indefinitely. Example: ``` dev ~ % tahoe magic-folder status -n TestFolder Magic-folder status for 'TestFolder': Local files: file.txt (5.21 MB): good, version=0, created 6 minutes ago subdir@_ (0 B): good, version=0, created 5 minutes ago subdir@_other_file.txt (965.85 kB): good, version=0, created 2 minutes ago Remote files: admin's remote: file.txt (5.21 MB): good, version=0, created 6 minutes ago subdir@_ (0 B): good, version=0, created 5 minutes ago subdir@_other_file.txt (965.85 kB): good, version=0, created 2 minutes ago Uploads: subdir/: 0.0% done ``` In this case, the `subdir/: 0.0% done` upload operation will persist in between client restarts (i.e., be re-added to the queue on startup but remain at "0.0% done" forever), regardless of the contents of that subdirectory and/or the ongoing upload/download progress of any of the files contained inside it. As meejah has suggested, this may have something to do with the "flattening" behavior of magic-folder (which does not use standard/nested tahoe directories but instead lists all files within a magic-folder at the top-level of a mutable object using "@_" as a path separator). In any case, the correct behavior should probably either clear/remove this upload operation once "subdir" has been successfully created in the remote magic-folder, or keep the upload operation in the list for some amount of time but display it as being 100% done.
tahoe-lafs added the
unknown
normal
defect
1.12.1
 labels 2018-05-14 01:18:24 +00:00
tahoe-lafs added this to the undecided milestone 2018-05-14 01:18:24 +00:00
meejah commented 2018-05-15 04:40:29 +00:00
Author
Owner
Copy link

Does this always happen if you add a subdir? I tried a couple quick things but didn't ever see any of my subdirs in the uploads list.

Does this *always* happen if you add a subdir? I tried a couple quick things but didn't ever see any of my subdirs in the uploads list.
meejah commented 2018-05-15 04:41:57 +00:00
Author
Owner
Copy link

Oh, there we go: this only happens if you:

  • add a subdirectory
  • restart the client
Oh, there we go: this only happens if you: - add a subdirectory - restart the client
meejah commented 2018-05-15 15:12:54 +00:00
Author
Owner
Copy link

Hmm, I also see that at least my subdir "uploads" entries go away after a while (possibly when magic-folder decides to do a "full scan" which is every 10 minutes).

Hmm, I also see that at least my subdir "uploads" entries go away after a while (possibly when magic-folder decides to do a "full scan" which is every 10 minutes).
tahoe-lafs added
code-frontend-magic-folder
 and removed
unknown
 labels 2019-01-29 15:57:12 +00:00
tahoe-lafs added the
somebody else's problem
 label 2020-06-30 13:48:54 +00:00
exarkun closed this issue 2020-06-30 13:48:54 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No labels
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No milestone
undecided
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2924
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?