[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] domU file system corruption

  • To: Florian Heigl <florian.heigl@xxxxxxxxx>
  • From: Thomas Knauth <thomas.knauth@xxxxxxxxxxxxxx>
  • Date: Tue, 8 Feb 2011 16:03:08 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 08 Feb 2011 07:19:58 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=U7vP+4TmKAjx6zxz5fsxbpIUxR1zRs+BGNeOOoJjKCqE7xjN1DJ5cwstyXS6fi4i6N vg0Qx3eMx7VFjgor+scR8rSdAIBf8eOypJ7sFw2BKNUktKP80hG1z7AAnI1U2scLw4Mc I1J9Rs9fiEKmaWAj5cHnzkhDaaI+oGyIE+y1c=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> Can you try to "drop caches" via /proc after the vm shutdown? Then try
> hard and see if you can reproduce the issue.
> I think I remember loop devices are being buffered by the kernel, it
> will not care that they reside on a "sync" filesystem like nfs.

I resorted to calling /bin/sync after shutting down the VM. This seems to help.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.