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

storage: NFS unmounting of a busy share lacks critical information #8563

Closed
andreasn opened this issue Feb 6, 2018 · 2 comments
Closed

storage: NFS unmounting of a busy share lacks critical information #8563

andreasn opened this issue Feb 6, 2018 · 2 comments
Labels
UXresearch-finding Issues that we found while conducting user research

Comments

@andreasn
Copy link
Contributor

andreasn commented Feb 6, 2018

In the usability testing of NFS, we identified that all four participants lacked the information to know if a busy share was safe to unmount.
While the session information was great, they wanted more information about how long ago the session was active.

@andreasn
Copy link
Contributor Author

andreasn commented Feb 7, 2018

If we put in a timestamp for when the session was last active, that should help.
mockup

@andreasn
Copy link
Contributor Author

andreasn commented Feb 7, 2018

Some quotes from the test:

  • "It's nice to have it ask you for confirmation. It need some prompt to say ""Are you sure you want to do that?"" We're trusting our sysadmins in the extreme.
  • Ideally I would like to see what other services are being run under that session. It doesn't give me enough information.
  • Want to know what other services are being run by that user. If it's safe to stop and unmount.
  • I want more information in the popup.
  • I understand that I'll lose the session. I would try to find out who has this login session, before I yank out this login session.
  • I want to see ""terminate session"" under Account.
  • It would be useful in Accounts that something here says that I'm in Session4, because nothing is linking it now.
  • I would go and talk to them before stopping and unmounting. I would look at the CPU, Memory etc by user and I don't see anything here about that. I would go and look in system, and try and find the resource user for that user, and if that person is idle, I would kick them off. "

@schizari schizari added the UXresearch-finding Issues that we found while conducting user research label Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UXresearch-finding Issues that we found while conducting user research
Projects
None yet
Development

No branches or pull requests

2 participants