-
Notifications
You must be signed in to change notification settings - Fork 14
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
ws_restore: Restore WS between filesystems #73
Comments
You guessed right, it is a mv, and it should be fast. |
Ok, to prevent user interruption is of course a crucial part during the restore process. And additionally ... the admin can configure the "restorable" and "allocatable" parameter seperately. But if allocation is not allowed, a user has no way to restore a workspace successfully (unless an previous ws is still existing on the filesystem). So maybe some additional checks are useful for the ws_restore command, e.g:
I think these additonal checks are very helpfull if you have more than one or two filesystems in your cluster. |
Hi,
we are migrating users from one filesystem (work) to another (gpfs) and set the old system to
and make the new filesystem the default one..
But some users have expired workspaces, which they want to restore and migrate to the new filesystem.
It looks like "ws_restore" is not able to do this because in every combination the workspace could be found:
The restoration to the existing workspaces "perftest-beegfs", which is on the same filesystem works as expected.
I' not sure if this is a bug or a feature, because restoring between filesystems will be more than only a fast "mv".
But in both cases it is a real problem for users.
The only way to solve this was to enable the allocation of "work" temporarily.
The text was updated successfully, but these errors were encountered: