From owner-freebsd-xen@freebsd.org Fri Jan 29 16:03:48 2021 Return-Path: Delivered-To: freebsd-xen@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 286F94F06E9 for ; Fri, 29 Jan 2021 16:03:48 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (ns.NFBCAL.ORG [157.22.230.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nfbcal.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DS2Fb1gdXz3Kv8 for ; Fri, 29 Jan 2021 16:03:46 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (localhost [127.0.0.1]) by nfbcal.org (8.15.2/8.14.1-NFBNETBSD) with ESMTPS id 10TG3guF005336 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Jan 2021 08:03:43 -0800 (PST) Received: (from buhrow@localhost) by nfbcal.org (8.15.2/8.12.11) id 10TG3fq9013084; Fri, 29 Jan 2021 08:03:42 -0800 (PST) Message-Id: <202101291603.10TG3fq9013084@nfbcal.org> From: Brian Buhrow Date: Fri, 29 Jan 2021 08:03:41 -0800 In-Reply-To: X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: Roger Pau =?utf-8?B?TW9ubsOp?= Subject: Re: Corruption in xenstored tdb file? Cc: , buhrow@nfbcal.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nfbcal.org [127.0.0.1]); Fri, 29 Jan 2021 08:03:43 -0800 (PST) X-Rspamd-Queue-Id: 4DS2Fb1gdXz3Kv8 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of buhrow@nfbcal.org designates 157.22.230.125 as permitted sender) smtp.mailfrom=buhrow@nfbcal.org X-Spamd-Result: default: False [-0.23 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:ns.nfbcal.org]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nfbcal.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[157.22.230.125:from]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[157.22.230.125:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.933]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7091, ipnet:157.22.0.0/16, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MAILMAN_DEST(0.00)[freebsd-xen]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 16:03:48 -0000 Hello. Yes, I think /var/run/xen or /var/run/xenstored is highly appropriate. -thanks -Brian On Jan 29, 1:40pm, Roger Pau =?utf-8?B?TW9ubsOp?= wrote: } Subject: Re: Corruption in xenstored tdb file? } On Thu, Jan 28, 2021 at 05:11:04PM -0800, Brian Buhrow wrote: } > hello. Recently One of my FreeBSD-xen servers went down hard due to a power failure. } > When it came back up, one of the domus' came up, but with no network interface. Dmesg } > messages show the following errors. To fix the issue, I removed the /var/lib/xenstored/tdb } > file and rebooted. Before that, I couldn't get this domu to boot with a network interface. My } > question is, is it reasonable to take this action when such an error occurs and, further, might } > it be better to remove that file before attempting to start xen on reboots, just in case } > something didn't go down cleanly? } } Yes, I think it should be placed in a directory that's cleaned on } reboot, it's not expected that people have to go clean this } themselves. } } Do you have any recommendation where this should be placed? } } /var/run/xen would seem like a suitable place. } } Thanks, Roger >-- End of excerpt from Roger Pau =?utf-8?B?TW9ubsOp?=