SFTP: put an approximation of grid capacity and available space in the 'df' output #1285
Labels
No Label
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
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1285
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Ticket #648 is about collecting server capacities and putting them on the welcome page. This might also allow a better approximation of available space than what SFTP currently outputs for 'df'.
Because the SFTP protocol did not originally have a way of implementing 'df', clients use either an extension (implemented at [sftpd.py SftpUserHandler.extendedRequest]source:src/allmydata/frontends/sftpd.py@4545#L1757) or try to log in to the server and issue a 'df' command (implemented in [sftpd.py ShellSession.execCommand]source:src/allmydata/frontends/sftpd.py@4545#L1879). sshfs does the latter, and will not mount the filesystem if it cannot do so. Currently we always report 314159265 KiB free, and double that capacity, to keep sshfs happy.
However, even given the space available on each server, it is not entirely obvious what to report as the total space available on the filesystem. Brian wrote in ticket #648:
Proposed method of calculating the grid capacity and available space:
The rationale here is that the
H
servers with most available space are likely to fill up last, and when theH
'th of those servers fills up, any extra space on the remainingH-1
that have more space will be unusable. (Implementing #872 would improve this situation.)Hmm, do we have any way of implementing
get_used_space_on_each_server()
? I don't think we do (but that would be part of #648).Attachment delegate-grid-stats-calculation-to-client.darcs.patch (11898 bytes) added
Move responsibility for calculating the estimated total/used/available space on a grid as used by SFTP to client.py.
Replying to davidsarah:
Figuring out how much space your local storage server is using is #671.