From owner-svn-src-head@freebsd.org Tue Jan 19 18:36:45 2016 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14B61A88C23; Tue, 19 Jan 2016 18:36:45 +0000 (UTC) (envelope-from cschuber@gmail.com) Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9CDA148A; Tue, 19 Jan 2016 18:36:44 +0000 (UTC) (envelope-from cschuber@gmail.com) Received: by mail-pf0-x231.google.com with SMTP id e65so180072968pfe.0; Tue, 19 Jan 2016 10:36:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:mime-version:from:subject:date:to:cc:content-type; bh=z5FvMqRdxhZxNs1NmG3rw7Z5JUSwlyCBSlXOiCLQF9Q=; b=dyIVGfyV1QOJIUdqw+yR+ZUZGdU9WGeVUqR0zDELl8MOVH8dODWuWdUP5Sx9+rSchj RLAGB5kVWPb84lU3U6YOI4NRkc+v0hMYfDTuiF+F423upLYWRtS7F3XjV12JZLR5RVR/ Q7vBOgQ7tyZexp7USmC5vYEPWyPIKdQs8c0t72w3kCRemV0/affGfX/07sgTIdtCTa1N +gbLogkLJrT3D3mwIUKy5Q4hieRrVRYGQi9sq7ghXKsAYlwM8vDZU4y6Y4jvp6psuLgN 1Si4O97L6j60fzE2yb285AO8XbCFVKYkZkCslvltGs2oT5CLCLHWbqvdKc/VnkTRv7tA 82JQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:mime-version:from:subject:date:to:cc :content-type; bh=z5FvMqRdxhZxNs1NmG3rw7Z5JUSwlyCBSlXOiCLQF9Q=; b=HYcq6H7D5xJCisKC/WI9hUNA9ppij/8CehP0QFH4vMEv5oHUnBZ+amz37kaObOAAxT jyZeZvcs6pLmAWei/GjAZo7qAfIcJDdG5dmFsJFz8+7npYE1crntlBwgpNuLjEevrj1j NzQlnshu2zelM4fbiBLbYkMrZC0sZpudS2Zgv2EwDGjtz9QVUxkLo8xWivdpioLcZgbS scBjmuwdvyqL9k07DCj2oDuSn5Ew6xlIu/wKlKk47ZtijF6flpd05JDkZHjRvIBcrztg 5D2tZ36RUEHghjX5yj4I0YonAFAIeLIvUEgAIM/FW9AeC16ifDUZ9w2q79VppUCcuF6c t2UQ== X-Gm-Message-State: ALoCoQnhQl/lRP9FgMIxRu/2kQ+M+yYka2i3B8S/6ehzBY4vn51s7rsjw/wanwUuvZvKs/TDJpCFjx7oZFGwQmqxWiMU45Y5ZA== X-Received: by 10.98.86.67 with SMTP id k64mr47107549pfb.50.1453228604396; Tue, 19 Jan 2016 10:36:44 -0800 (PST) Received: from [10.168.3.75] (S0106d4ca6d8943b0.gv.shawcable.net. [24.68.134.59]) by smtp.gmail.com with ESMTPSA id 73sm43189370pfm.10.2016.01.19.10.36.42 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Jan 2016 10:36:43 -0800 (PST) Message-ID: <569e823b.cc0c620a.88044.ffffd719@mx.google.com> MIME-Version: 1.0 From: Cy Schubert Subject: RE: svn commit: r294329 - inhead/sys/cddl/contrib/opensolaris/uts/common/fs/zfs: . sys Date: Tue, 19 Jan 2016 10:36:45 -0800 To: Shawn Webb , Alan Somers CC: Kurt Lidl , "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" , "cy@freebsd.org" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2016 18:36:45 -0000 Just another thought. If we must do this, why not a sysctl to restore funct= ionality to those of us who need it. If indeed there are panics and hangs d= ue to zpools on vdevs, a sysctl to bypass the restriction, in effect saying= "I understand the risk," would be a reasonable compromise. I'm willing to = put together a patch to do this. Sent from my cellphone, ~Cy -----Original Message----- From: Cy Schubert Sent: 19/01/2016 10:27 To: Shawn Webb; Alan Somers Cc: Kurt Lidl; svn-src-head@freebsd.org; svn-src-all@freebsd.org; src-commi= tters@freebsd.org; cy@freebsd.org Subject: RE: svn commit: r294329 - inhead/sys/cddl/contrib/opensolaris/uts/= common/fs/zfs: . sys Agreed, I do a fair bit of testing (nothing permanent) by putting zpools on= zvols. I have never experienced a hang or panic due to zpools on zvols. Th= is is a POLA violation. Regarding zfs hangs, I only experience them with zpool vdevs on USB devices= on my laptop when I forget to zpool export tpool prior to laptop shutdown/= reboot. This is acceptable as I'm in front of it. Sent from my cellphone, ~Cy -----Original Message----- From: Shawn Webb Sent: 19/01/2016 10:07 To: Alan Somers Cc: Kurt Lidl; svn-src-head@freebsd.org; svn-src-all@freebsd.org; src-commi= tters@freebsd.org Subject: Re: svn commit: r294329 - inhead/sys/cddl/contrib/opensolaris/uts/= common/fs/zfs: . sys On Tue, Jan 19, 2016 at 10:20:38AM -0700, Alan Somers wrote: > On Tue, Jan 19, 2016 at 10:08 AM, Kurt Lidl wrote: > > Removing the ability to run different zpools on top of a zvol is > > a significant reduction in functionality of the entire system, and a hu= ge > > violation of the POLA. >=20 > The thing is, it never really worked in the first place. Panics and > deadlocks are so frequent that I don't think the feature was usable > for anybody. I actively use this every day and will be making even more use of it in the very near future. I haven't had a single kernel panic. I have had deadlocks at shutdown, but since it's a laptop and I'm sitting right in front of it, it's not a big deal. I'd say fix the underlying problem, don't prevent people from getting work done. >=20 > > > > At the very least, can you not add a sysctl that allows the > > dangerous behavior (even if it defaults to off)? Myself > > and certainly others rely on having being able to use a zpool > > installed into a zvol for hosting bhyve virtual machines. >=20 > Your use case should be unaffected. The guest has a different ZFS > instance than the host, so it should work just fine. Please let me > know if you have problems. --=20 Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE