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

Ca 390937: fix conflicts between GC and SR detach #688

Merged
merged 2 commits into from
May 23, 2024

Conversation

MarkSymsCtx
Copy link
Contributor

No description provided.

To avoind inheriting locks and open files through a fork start the GC
cleanup script as a standalone process.

Signed-off-by: Mark Syms <mark.syms@cloud.com>
Doing the cleanupCache before acquiring the locks can result in a
failure, in particular as part of XenCert where an sr_detach operation
attempts to abort GC but the GC is not registered as running and then
the umount of NFS fails as the cache cleanup still has the directory
open.

Also check for the SR still being attached after the active lock has
been acquired.

Signed-off-by: Mark Syms <mark.syms@cloud.com>
@MarkSymsCtx MarkSymsCtx merged commit 8462c37 into xapi-project:master May 23, 2024
2 checks passed
@MarkSymsCtx MarkSymsCtx deleted the CA-390937 branch May 23, 2024 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants