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

add expected 'df' output to README #25

Closed
trel opened this issue Aug 21, 2019 · 6 comments
Closed

add expected 'df' output to README #25

trel opened this issue Aug 21, 2019 · 6 comments
Assignees

Comments

@trel
Copy link
Member

trel commented Aug 21, 2019

NFSRODS populates the available and used space fields as 0. This signals to a default df request to ignore the mountpoint information for NFSRODS.

Live NFSRODS mountpoint information can be viewed via df -a.

@michael-conway
Copy link
Member

michael-conway commented Aug 21, 2019 via email

@trel
Copy link
Member Author

trel commented Aug 21, 2019

We've settled on reporting zeroes for now since anything else would be misleading.

  • There is no 'actual' number (iRODS has multiple resources, possibly including AWS S3...).
  • Arbitrary 'ReallyBigNumber' is misleading and could cause certain problems to other programs using that information to make decisions.
  • Zero is a known pattern for other 'silent' mountpoints.

If there are good ideas, please share - otherwise, we're going with 0 for now.

@trel trel added the enhancement New feature or request label Aug 28, 2019
@trel trel self-assigned this Aug 28, 2019
@anderbubble
Copy link
Contributor

We're working on deploying quota support as seen here:

https://github.com/irods/irods_policy_examples/blob/master/irods_policy_logical_quotas.re

I'd love to have these quotas reflected in the df output. Maybe there should just be a standard set of irods metadata that should get reported out via NFSRODS? Or maybe it should read df data out of a PEP? (Sorry if these are the wrong terms; let me know if this isn't clear.)

@michael-conway
Copy link
Member

michael-conway commented Sep 17, 2019 via email

@anderbubble
Copy link
Contributor

To be fair, I think the current state is "nonexistent" except that we asked for it and that policy is what came out. :) We haven't deployed or tested it yet; but that's basically my next step for our environment (in competition with "get NFSRODS to work").

@trel
Copy link
Member Author

trel commented Sep 18, 2019

The linked logical quotas policy is for 'all users' under a particular logical path. It handles keeping track of totals in the system via pre- and post- PEPs when data is added/removed from the system.
They possibly could be represented to df in the way you're describing - however...

iRODS also has the concept of both total and per-resource quotas as defined per-user and per-group. I can't figure out how to represent those to df at this time - or whether they get in the way at all.

Also, NFSRODS is only a single iRODS client - so we'd need to think through what representing 'capacity' means for other clients and how they can be fairly informed of the same type of information.

trel added a commit to trel/irods_client_nfsrods that referenced this issue Mar 24, 2020
trel added a commit that referenced this issue Mar 24, 2020
@trel trel added documentation and removed enhancement New feature or request labels Mar 24, 2020
@trel trel closed this as completed Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants