From owner-freebsd-stable@FreeBSD.ORG Tue Feb 18 10:32:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E8852BB2; Tue, 18 Feb 2014 10:32:50 +0000 (UTC) Received: from mail-ee0-x22a.google.com (mail-ee0-x22a.google.com [IPv6:2a00:1450:4013:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 54B83155A; Tue, 18 Feb 2014 10:32:50 +0000 (UTC) Received: by mail-ee0-f42.google.com with SMTP id b15so7612708eek.15 for ; Tue, 18 Feb 2014 02:32:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DSD0jCllxWHFPzh24QBGnmvE9bPsLE+mElQ89snR01w=; b=0MjI7SJV7fxlvlcbv5kMAWUz9U4u9GqQSbvi0bKyjOk710PFa2JlAEWgEQLulzxUIn BfE1kVv2m/BaGR9tRupHDk0xr2YeNeobY00Utf779ZCsmoQXR9kBu1X3Q68ySjNKJkYI smgQsxqjgLTUykeZTKaGg1JV2HSX2gxqoZPnCtVaJYpdnZcbeFdBhdbo8TgOiDQP0ppM FjgxPcMPnDDvdvBglxSNdE2FytVIbsB2/3dF2nKK1yvN2pRb9vD/RwEx8ehKTXvVBFMl EvBou0LLHygyZJwUGBUSFqJqeJil7iEUNpqUESzFHGl+CzzjY+FEoLKuYdFndkFxYxiU ez7A== X-Received: by 10.14.109.71 with SMTP id r47mr32730876eeg.28.1392719568285; Tue, 18 Feb 2014 02:32:48 -0800 (PST) Received: from strashydlo.home (adgg180.neoplus.adsl.tpnet.pl. [79.184.136.180]) by mx.google.com with ESMTPSA id o43sm68508185eef.12.2014.02.18.02.32.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 02:32:43 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: recovering from or increasing timeouts on virtio block device Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: <920CC320-1A95-46E2-BB18-B6987805885E@jnielsen.net> Date: Tue, 18 Feb 2014 11:32:38 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <18D133C0-E71B-4E66-A13F-6DC3B1BF620C@FreeBSD.org> References: <920CC320-1A95-46E2-BB18-B6987805885E@jnielsen.net> To: John Nielsen X-Mailer: Apple Mail (2.1283) Cc: Bryan Venteicher , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2014 10:32:51 -0000 Wiadomo=B6=E6 napisana przez John Nielsen w dniu 17 lut 2014, o godz. = 21:21: > I run several FreeBSD virtual machines in a Linux KVM environment with = a SAN. The VMs use virtio block storage, and the KVM hosts map the = virtual volumes to targets on the SAN. Occasionally, failover or other = maintenance events on the SAN cause it to be unavailable for 30+ = seconds. When this happens, the FreeBSD VMs have hard failures on the = vtbd* devices, and thereafter any attempted reads or writes return = immediately with an error (even after the SAN is responsive again). The = only way to recover a VM once that happens is to hard boot it. >=20 > Is there any way to adjust the timeouts or enable some kind of retry = for the virtio block devices? It would be nice to be able to recover = gracefully after a SAN event without needing to reboot the VMs. Use gmountver(8) perhaps? --=20 If you cut off my head, what would I say? Me and my head, or me and my = body?