Details
Description
If "lfs mirror delete" is called on a file to delete a specific mirror (eg. with "-p <pool>" or "--comp-id <id>", but that is the only non-stale mirror of the file, it makes sense from a usability point of view to automatically resync the stale mirror(s) and then remove the mirror as requested by the user, rather than returning an error to the user.
Otherwise, the user will first have to understand that the stale mirrors are preventing their request from completing, then manually resync the mirror with "lfs mirror resync" before calling "lfs mirror delete" again. Since "lfs mirror delete" could do the resync directly, why bother the user to have to understand this problem and do the resync manually?
Attachments
Issue Links
- is related to
-
LU-5170 lfs usability
- Open
-
LU-14512 prohibit extend file with stale mirror
- Closed
-
LU-14554 Improve usability of "lfs mirror" commands
- Open
- is related to
-
LU-18468 Md5 chksum fails on the mirror file created by dd with bs=4k after doing mirror resync and delete
- Open
-
LU-11485 MDS allows "lfs setstripe" to mark last mirror as stale
- Resolved
-
LU-11022 FLR1.5: "lfs mirror" usability for Burst Buffer
- Resolved