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

Re: oxenstored restart after system crash

  • To: Roger Pau Monne <roger.pau@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Edwin Torok <edvin.torok@xxxxxxxxxx>
  • Date: Thu, 18 Feb 2021 10:13:38 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mvD//k+mnJawP31ZUy/eUC99eCmCfx6eayuNUTQap3o=; b=EYpXHWbMIp9y1iyH7eamexK7Y2hPqpanLQL55XJQw3hSrxkMHv7mq/MiE1leE93c0W7fBGoUWaDkwObrXyVWdGPTC/rlT4ycdT5WNspRxJBa/Lo6Z7rm7TLM4LfK48vEIQskuo0coDZB/sJKY/t6znlkinAkwdOujMu2E7qqrNWVt5kYFvTCliwEAaoVWXPXjApar0DX8vfpwIkfS4wTOJxCL6kG91LHtNsSP2RKuKVKBjxszORVU4iEf0M8/UKJF7Fb1jzE9nHHivr1gQOxqLRPx6FYfKngnei886qvYLVPu09hBuNNoiGItWwhSOhY+w27lk+briWJL73J2mjlHg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CpnHaZMjYenfg//z7z6U4RmFm5K3om05+cWaHgsd8kBWsexP3Z8E5sqOj1czMj5Y6Xixw3Yz2Necz8RlHJdUXV+L9HyChAOwNYJQlB1vOGV/vOuA16E5GXsbXWZhcDkDhiAsDOfyb6brii8z4rMe3sxjOWa6+eV/w4aQBFTl/Rq+GpOhD8WANjMeHnclu8wVjbct0kYJCbuT5PqjD3A6gkpgbxF3hR67nuWU1UUcJry3E42aNnmZSZJOCx7kUf8iaUIEqAl1luS5FXEBtP73Za0XVsFvd5lRuwyTI5g8NCxsea6Lz4Us7e4TR9roj23KVdpAoLh2F1ZdcCrdGXK5rQ==
  • Authentication-results: esa2.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
  • Cc: Christian Lindig <christian.lindig@xxxxxxxxxx>, Jürgen Groß <jgross@xxxxxxxx>, Ian Jackson <iwj@xxxxxxxxxxxxxx>
  • Delivery-date: Thu, 18 Feb 2021 10:13:53 +0000
  • Ironport-sdr: ElurHBGuJ8z1ELb231YywTqaXFsLfMZllvXRjPZehCw6/ZXkQ/Il6V45a1qb63ihU0r5LOlzcK Urolrpaj8E5lInWV4pDK2qNLH2tHb+HwLC32z7u6K8GQJZqxnSJ6EUnL8EBh9VbvoTEsE4rzlY nHP6usVTbfEXldkjqw5g4r2qnXfJ/GMhhKmUrQ7U6aQJKesEf2L8QzpJRqotQ1BkpvuQ4YA3jB PubDTTdG65fReSFJf+DCvsYYULTRUPU6jsOOQV43whXjmb4pgJktfWoR6mHIKJbOWp1/gJ9wiH smg=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHXBdrqiMKXv9cDnkSLt+pdzqCGoKpdrxcg
  • Thread-topic: oxenstored restart after system crash


oxenstored doesn't have a tdb file, by default it stores the entire tree in memory only.

There is a way to persistently store the tree (--persistent), but that is not enabled by default and I don't know whether it even works.
Master (or the hotfixed releases) have a live-update functionality now that dump and restore state properly (and reuses some of the persistent disk code, but also dumps some additional state).

The default location of the "persistent" database is /var/run/xenstored, which is a tmpfs and thus cleared on every boot. So if you'd ensure that oxenstored uses the equivalent of that on FreeBSD (or have a script on boot that clears it) that would solve any issues like this.

I don't know about C xenstored's behaviour, I'll let someone else answer that.

Best regards,

From: Roger Pau Monne <roger.pau@xxxxxxxxxx>
Sent: 18 February 2021 09:46
To: xen-devel@xxxxxxxxxxxxxxxxxxxx <xen-devel@xxxxxxxxxxxxxxxxxxxx>
Cc: Christian Lindig <christian.lindig@xxxxxxxxxx>; Edwin Torok <edvin.torok@xxxxxxxxxx>; Jürgen Groß <jgross@xxxxxxxx>; Ian Jackson <iwj@xxxxxxxxxxxxxx>
Subject: oxenstored restart after system crash

Last month I got a query from a FreeBSD Xen user having issues with
xenstored after a power failure:


I'm not sure what's the right approach here. I've been told cxenstored
will attempt to unlink the tdb file when starting, does oxenstored
attempt to do the same?

Should the tdb file be placed in a path that's cleaned up on boot?

Should xencommons remove the stale tdb before starting xenstored?

Mostly wanted to know what's the approach on Linux so that I can do
the same on FreeBSD.

Thanks, Roger.



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