[Openstack-operators] /var/lib/nova/instances fs filled up corrupting my Linux instances

Vivek Singh Raghuwanshi vivekraghuwanshi at gmail.com
Wed Mar 13 16:28:50 UTC 2013


make a entry in the nova.conf to delete _base directory unused data
automatically

On Wed, Mar 13, 2013 at 9:08 PM, Conor Glynn <cglynn at sportingindex.com>wrote:

> by the way, yes both compute nodes were using that shared NFS storage...
> ________________________________________
> From: Conor Glynn
> Sent: 13 March 2013 15:07
> To: Michael Still
> Cc: openstack-operators at lists.openstack.org
> Subject: RE: [Openstack-operators] /var/lib/nova/instances fs filled up
> corrupting my Linux instances
>
>
> thanks Michael,
> conor
> ________________________________________
> From: mikalstill at gmail.com [mikalstill at gmail.com] On Behalf Of Michael
> Still [mikal at stillhq.com]
> Sent: 13 March 2013 14:53
> To: Conor Glynn
> Cc: openstack-operators at lists.openstack.org
> Subject: Re: [Openstack-operators] /var/lib/nova/instances fs filled up
> corrupting my Linux instances
>
> On Wed, Mar 13, 2013 at 9:42 AM, Conor Glynn <cglynn at sportingindex.com>
> wrote:
> > I ran:
> > cd /var/lib/nova/instances; find -name "disk*" | xargs -n1 qemu-img info
> |
> > grep backing | sed -e's/.*file: //' -e 's/ .*//' | sort | uniq >
> /tmp/inuse
> > then I removed some of the old _base files that did not exist in
> /tmp/inuse
>
> That should be ok, although you should probably note that you can also
> just turn on the image cache manager in folsom and it will magically
> keep the base directory clean for you. That manual cleanup command
> line is only really needed for essex these days.
>
> Note, if you have multiple compute nodes all storing instances to a
> shared NFS directory this is not true, and the image cache manager is
> dangerous in folsom. This is true for your cleanup script as well.
> Were both compute nodes using the same NFS directory?
>
> I went and had a look at my blog about this stuff and realised its not
> as clear as I thought it was. I'll work on fixing that ASAP.
>
> Michael
>
>
> Please consider the environment before printing this email
>
> Inbound Email has been scanned for viruses and SPAM
>
>
>
>
> *****************************************************************************
> P *Please consider the environment before printing this email or
> attachments*
>
>
> This email and any attachments are confidential, protected by copyright
> and may be legally privileged. If you are not the intended recipient, then
> the dissemination or copying of this email is prohibited. If you have
> received this in error, please notify the sender by replying by email and
> then delete the email completely from your system. Neither Sporting Index
> nor the sender accepts responsibility for any virus, or any other defect
> which might affect any computer or IT system into which the email is
> received and/or opened. It is the responsibility of the recipient to scan
> the email and no responsibility is accepted for any loss or damage arising
> in any way from receipt or use of this email. Sporting Index Ltd is a
> company registered in England and Wales with company number 2636842, whose
> registered office is at Gateway House, Milverton Street, London, SE11 4AP.
> Sporting Index Ltd is authorised and regulated by the UK Financial Services
> Authority (reg. no. 150404) and Gambling Commission (reg. no.
> 000-027343-R-308898-001). Any financial promotion contained herein has been
> issued and approved by Sporting Index Ltd.
>
> Outbound email has been scanned for viruses and SPAM
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
ViVek Raghuwanshi
Mobile -+91-09595950504
Skype - vivek_raghuwanshi
IRC vivekraghuwanshi
http://vivekraghuwanshi.wordpress.com/
http://in.linkedin.com/in/vivekraghuwanshi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130313/509f73eb/attachment.html>


More information about the OpenStack-operators mailing list