From owner-freebsd-geom@FreeBSD.ORG Wed Jul 31 14:31:28 2013 Return-Path: Delivered-To: freebsd-geom@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 ESMTP id 3A1C6374; Wed, 31 Jul 2013 14:31:28 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id EFEFC2565; Wed, 31 Jul 2013 14:31:27 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 250B3125AC; Thu, 1 Aug 2013 00:31:20 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BNS43095 (AUTH peterg@ptree32.com.au); Thu, 1 Aug 2013 00:31:19 +1000 Message-ID: <51F91FAC.60905@freebsd.org> Date: Wed, 31 Jul 2013 07:31:08 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: lev@FreeBSD.org Subject: Re: [PROPOSAL] GEOM probing/tasting firewall References: <447183917.20130731130956@serebryakov.spb.ru> In-Reply-To: <447183917.20130731130956@serebryakov.spb.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@FreeBSD.org, freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 14:31:28 -0000 > For first time this idea was formulated in Jabber talk with friend of > mine, who uses FreeBSD for massive iSCSI hosting on ZVOLs. He has problems > with tasting these ZVOLs, which contain different types of data (Windows > disks, Linux disks, FreeBSD disks, etc). Here are label conflicts, strange > messages about corrupted GPTs, etc. So, it looks like to have configurable > way to prevent some GEOM tasting is good idea. I'm all for this. bhyve has the exact same problem with unnecessary tasting of zvols and raw volumes being used by guest o/s's. later, Peter.