From owner-freebsd-fs@freebsd.org Sun Apr 2 21:00:34 2017 Return-Path: Delivered-To: freebsd-fs@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 43F9AD2B97A for ; Sun, 2 Apr 2017 21:00:34 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A5BD2F9 for ; Sun, 2 Apr 2017 21:00:34 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v32L01GO054323 for ; Sun, 2 Apr 2017 21:00:34 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201704022100.v32L01GO054323@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 02 Apr 2017 21:00:34 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2017 21:00:34 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic New | 217062 | for file systems mounted with -o noexec, exec=off Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS 7 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Apr 3 13:13:31 2017 Return-Path: Delivered-To: freebsd-fs@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 3A6A6D2CD77 for ; Mon, 3 Apr 2017 13:13:31 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (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 C5FDA6D2 for ; Mon, 3 Apr 2017 13:13:30 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wr0-x235.google.com with SMTP id w11so168013640wrc.3 for ; Mon, 03 Apr 2017 06:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=upbhKFyI7HLVDjCM1ME+vayhIhgCTTx9C0GDn+QmoIY=; b=MaDFBGSuIwHnDzDcNauJRQhgLCHAeAPBue1KJtpUp16tkfw1oSpBxViCjjsuQ0I2AC Wk/JDaw4ILomZAHMxqy3c4Q868RBE4o3ZxTeRiHPezhbRdHJEtUKxhknQqw9U5i9XNFe c53TbRPSBI4Oce6mf2kcP7TrnqPp5NlDOfFgCjV1Gvo1pVRJLjzysOjS/NO/yX7MmbZX b/tI2tPDavhgZPdP0v/GGdgIrf2KLSNX0NdOc7HzrwhX5IAtcNKQl79wAybQ1vSiJuC+ 5LENVHepQJg1zh81hKFKJ4NqHZcTmvQaPzIa/wmEyriE9sgzRRiEysrxtUQr5wg8TwPc VoFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=upbhKFyI7HLVDjCM1ME+vayhIhgCTTx9C0GDn+QmoIY=; b=pJ5sTsY+L97Sek0WdG6jOVXRL4S0dDWqKMfTgAM1aM3+s2lVuYRkV9NcljVERUi0gg 4+/yncNvfh+zXNHGjGfr35o1l6xXdURfvTfaMgVymVwcfvrXZAIZtiaeBsVRRVna4QwG u7HLTi/dHGBi5Yj1slD1MIf/E0qMxfvbeG9OnUB8SXLXjTCIJKixnmY/I31XGgC8/9LN xCeoqGKGnmoLZ1dKdp2SXhUPePKlnW79+4EcqDJWt4v9qtrm3AtKr1jmkRYAGSSiLjaV LgP07XUq8WF7Kil/gwpQWWWHI/mPCc9Q0t5ZyBUmgTP7zilPI8+BDWhgbguHddcerDYc W6aw== X-Gm-Message-State: AFeK/H1x/uAFGmDzMUROrC/Ei4Z+hnb10mRIQGB5MHAUW51bLNI/8IPkwJ8lbiKGeCePUh1x X-Received: by 10.223.176.204 with SMTP id j12mr16669816wra.10.1491225208651; Mon, 03 Apr 2017 06:13:28 -0700 (PDT) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id y190sm14271642wmy.15.2017.04.03.06.13.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Apr 2017 06:13:27 -0700 (PDT) Subject: Re: 16.0E ExpandSize? -- New Server To: Larry Rosenman , Freebsd fs References: <22e1bfc5840d972cf93643733682cda1@FreeBSD.org> <8a710dc75c129f58b0372eeaeca575b5@FreeBSD.org> <96534515-4fcb-774e-a599-8d48aec930cd@multiplay.co.uk> <8387d38f-3185-8c07-396b-602c708002a6@multiplay.co.uk> <20170205035438.6gc2ybg6otidzpaz@borg.lerctr.org> From: Steven Hartland Message-ID: <51a3fd35-87f4-f02a-7576-c7edd214b010@multiplay.co.uk> Date: Mon, 3 Apr 2017 14:13:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170205035438.6gc2ybg6otidzpaz@borg.lerctr.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2017 13:13:31 -0000 On 05/02/2017 03:54, Larry Rosenman wrote: > I saw it was accepted upstream. Can it be committed to FreeBSD? FYI the PR has been accepted, but not yet committed upstream, so I've merged this fix as r316460. https://svnweb.freebsd.org/changeset/base/316460 Regards Steve From owner-freebsd-fs@freebsd.org Mon Apr 3 13:21:00 2017 Return-Path: Delivered-To: freebsd-fs@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 6A8A9D2C060 for ; Mon, 3 Apr 2017 13:21:00 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 43FB0C0F; Mon, 3 Apr 2017 13:21:00 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-type:Mime-version:In-Reply-To:References:Message-ID:To: From:Subject:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Gy1/sJScUH4hjlFh68F/HxPrGKmeBSARkAVhY00fanA=; b=UkUlhw5HhOKI3nnIVfCJYUUFWA 6uQ58uw4FAAPdKpMl3h2RHzQnrO7EcnYUe9vKJPGLfs3szK0O1e4jA9MO7Mogdkx9lGwIJz0+T4oO 16yZQqWwgaP2Pe/Cpmp6Gssx9FUKuPnsFicCnpekobnRSETfQBREFTU34qWvUQH7RzoI=; Received: from [47.220.164.50] (port=9094 helo=[192.168.200.198]) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1cv1ul-000L4D-EL; Mon, 03 Apr 2017 08:20:59 -0500 User-Agent: Microsoft-MacOutlook/f.20.0.170309 Date: Mon, 03 Apr 2017 08:20:58 -0500 Subject: Re: 16.0E ExpandSize? -- New Server From: Larry Rosenman To: Steven Hartland , Larry Rosenman , Freebsd fs Message-ID: <4D0A1F5F-0663-45DE-9E4E-A593E029CA18@lerctr.org> Thread-Topic: 16.0E ExpandSize? -- New Server References: <22e1bfc5840d972cf93643733682cda1@FreeBSD.org> <8a710dc75c129f58b0372eeaeca575b5@FreeBSD.org> <96534515-4fcb-774e-a599-8d48aec930cd@multiplay.co.uk> <8387d38f-3185-8c07-396b-602c708002a6@multiplay.co.uk> <20170205035438.6gc2ybg6otidzpaz@borg.lerctr.org> <51a3fd35-87f4-f02a-7576-c7edd214b010@multiplay.co.uk> In-Reply-To: <51a3fd35-87f4-f02a-7576-c7edd214b010@multiplay.co.uk> Mime-version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2017 13:21:00 -0000 Cool =E2=80=93 Thanks, Steve! =20 =20 --=20 Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 =20 =20 =20 From: Steven Hartland Date: Monday, April 3, 2017 at 8:13 AM To: Larry Rosenman , "freebsd-fs@freebsd.org" Subject: Re: 16.0E ExpandSize? -- New Server =20 On 05/02/2017 03:54, Larry Rosenman wrote: I saw it was accepted upstream. Can it be committed to FreeBSD? FYI the PR has been accepted, but not yet committed upstream, so I've merge= d this fix as r316460. https://svnweb.freebsd.org/changeset/base/316460 Regards Steve From owner-freebsd-fs@freebsd.org Fri Apr 7 15:04:53 2017 Return-Path: Delivered-To: freebsd-fs@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 02CBBD32795 for ; Fri, 7 Apr 2017 15:04:53 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9154838D for ; Fri, 7 Apr 2017 15:04:51 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id v37F4nlp025222 for ; Fri, 7 Apr 2017 17:04:49 +0200 (CEST) Received: from [217.29.46.2] ([217.29.46.2]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id v37F4nT4068498 for ; Fri, 7 Apr 2017 17:04:49 +0200 (CEST) (envelope-from hausen@punkt.de) From: "Patrick M. Hausen" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: iSCSI/ZVOL: ZFS or UFS on the initiator side? Message-Id: <35CF60B2-097A-4381-9B4A-ABF2B9BBC0B9@punkt.de> Date: Fri, 7 Apr 2017 17:04:43 +0200 To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2017 15:04:53 -0000 Hi, all, a general question: If I export a ZVOL via iSCSI to be used be another FreeBSD machine as a block device, is it advisable to use ZFS or should I stick to UFS? I don't have any reason to believe that ZFS might be harmful. I just know from experience, that e.g. tunneling TCP through TCP can lead to strange effects if you happen to really have packet-loss. Anything similar for ZFS in ZFS? What if iSCSI target (ZVOL) and initiator are on the same machine? They'll share ZIL and ARC. What if memory gets low? I'm investigatiing the feasibility of creating a HA setup by running a mirror (ZFS or gmirror/UFS) on top of 2 iSCSI ZVOLs, one on the local machine but still via ISCSI, one on a remote machine ... TIA for your opinion and advice, Patrick --=20 punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: J=C3=BCrgen Egeling AG Mannheim 108285 From owner-freebsd-fs@freebsd.org Sat Apr 8 11:20:10 2017 Return-Path: Delivered-To: freebsd-fs@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 0E4EED34439 for ; Sat, 8 Apr 2017 11:20:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F17753D8 for ; Sat, 8 Apr 2017 11:20:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v38BK9TB066379 for ; Sat, 8 Apr 2017 11:20:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 208882] zfs root filesystem mount failure on startup in FreeBSD 10.3-RELEASE if USB hdd with zpool is attached to another port Date: Sat, 08 Apr 2017 11:20:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: trasz@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2017 11:20:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882 --- Comment #12 from Edward Tomasz Napierala --- Julian, I don't think that's the problem. The code in 10 doesn't wait for devices, it just waits for all the root mount holds to be released. The co= de in 11 waits for devices, but for filesystems that don't have a specific dev= ice - like ZFS or NFS - it falls back to 10 behaviour, ie waiting for the root mount holds. To be honest I don't think this is a problem with root mount mechanism at a= ll.=20 It looks more like something internal to ZFS. Perhaps we should just put t= he loop inside zfs_mountroot()? --=20 You are receiving this mail because: You are the assignee for the bug.=