yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1103158] Re: XenServer not cleaning up SM locks

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: John Garbutt <john@xxxxxxxxxxxxxxx>
Date: Wed, 06 Mar 2013 17:18:47 -0000
Reply-to: Bug 1103158 <1103158@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Moved to will not fix, since it is an issue in XenServer not OpenStack

** Changed in: nova
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1103158

Title:
  XenServer not cleaning up SM locks

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  This is a placeholder ticket to capture some issues we're seeing in
  Nova related to XenServer not cleanup the /var/lock/sm directory when
  using a FileSR.

  Since /var/lock/sm resides on a ext3 fs, when 31998 locks are
  accumulated (32K -2), then we can no longer create any more locks
  causing widespread failures on that machine.

  The solution requires to parts:

  1. Citrix needs to fix this upstream

  2. We need to run a cleanup script against the machines in the cluster
  to remove these unneeded locks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1103158/+subscriptions