From owner-freebsd-fs@freebsd.org Sun Apr 8 21:01:21 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2853FA2E3D for ; Sun, 8 Apr 2018 21:01:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 69B4D82B85 for ; Sun, 8 Apr 2018 21:01:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1EBE8FA2E3A; Sun, 8 Apr 2018 21:01:20 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D63C3FA2E39 for ; Sun, 8 Apr 2018 21:01:19 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70FC682B50 for ; Sun, 8 Apr 2018 21:01:19 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B0B481C9DA for ; Sun, 8 Apr 2018 21:01:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w38L1IWf075563 for ; Sun, 8 Apr 2018 21:01:18 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w38L1ICE075554 for fs@FreeBSD.org; Sun, 8 Apr 2018 21:01:18 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201804082101.w38L1ICE075554@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 8 Apr 2018 21:01:18 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2018 21:01:21 -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 New | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data 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 8 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Tue Apr 10 05:45:40 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18644FA2F43 for ; Tue, 10 Apr 2018 05:45:40 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) (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 6A82B83341 for ; Tue, 10 Apr 2018 05:45:39 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f52.google.com with SMTP id o102-v6so9841265lfg.8 for ; Mon, 09 Apr 2018 22:45:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=kTKS6aTJv2EQiPhLGPkDDNj6KdX+NFPtXuYsfi6x4Ss=; b=jI6Rlk2FAqhxsLo5GrI8aCiCpttctQc4oTyneQR4Pdp4k+4wH7fMh2njKyrS4s6yok 9aiW3dHyTXbP7BMZDLVFiigW2E+fQwFhqQJQ/CladiXkinaKRzFN86uVK87+KR+vVRGi kkbrmpz4F1AQnxZ7ikaCY7YlFh+YLK9Jsy8tou3d7BKFf0OO6xyCKjloh2R2JZ8bndjH +KSE2f/hxTW1wibrrZhdiUDI20qDCvEt2sAx8KMW1gdz4DMsBvi6SITku/ig4QUMWX6y rbsw6EruRhNviI4fKOyLxmMxkwtUwbBAsrN7DcYnihm1Ku7VmXkfJPQ+gU1gC4bCO+TF fyvA== X-Gm-Message-State: ALQs6tCKFHE3cV/KzJXlYyPua2ho7e+8Qqgp51nHbLmzbbhyanVG2nEl xXiJUL6r9xm5zXnERVhboLHJA1H1 X-Google-Smtp-Source: AIpwx49Et19e99xjBw97yEO+0lnyZs4wGyPdHi189c4XrLpyTyWjX49+3xhXkKKuce69hCF//zCsdw== X-Received: by 10.46.29.140 with SMTP id w12mr23988569lje.108.1523339132034; Mon, 09 Apr 2018 22:45:32 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id z205-v6sm158403lff.38.2018.04.09.22.45.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Apr 2018 22:45:31 -0700 (PDT) Subject: Re: Does setuid=on work on ZFS datasets, or is the man page for zfs misleading? To: Stilez Cc: freebsd-fs References: <7eba73db-3097-5c8a-eb2c-e3880fb5b501@FreeBSD.org> <672e2c84-b906-4073-0206-7eb1720adc7e@FreeBSD.org> <1629c0d63d0.2756.49a377fccbf53440a4b582c142a1ed88@gmail.com> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <26e3c3b5-9baf-5499-0e12-81486cc8c839@FreeBSD.org> Date: Tue, 10 Apr 2018 08:45:30 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1629c0d63d0.2756.49a377fccbf53440a4b582c142a1ed88@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 05:45:40 -0000 On 06/04/2018 20:42, Stilez wrote: > I had looked at ACLs before asking. They don't work for this, your info looks > wrong AFAIK. They only allow inheritance of permissions, not ownership. None of > the ACL flags and nothing in setfacl man page, says anything about ownership > inheritance. That's correct. > I'm using NFSv4 of it matters, but I'm guessing that's the default > for ZFS based file hierarchies? Yes. > So the question stands - is there any working method to ensure files in a ZFS > dataset or contained dir have a predetermined owner? Including within ACLs if I > missed the right page? My assumption was that the ownership change was not an end goal and there was a wider context related to access management. In other words, why do you want to change file ownership unless you want to change the file's access rights... In my opinion, Unix file ownership is a part of Unix file access model. -- Andriy Gapon From owner-freebsd-fs@freebsd.org Tue Apr 10 19:06:05 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6B6BF90B54 for ; Tue, 10 Apr 2018 19:06:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5A6088050D for ; Tue, 10 Apr 2018 19:06:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1988CF90B53; Tue, 10 Apr 2018 19:06:05 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08443F90B52 for ; Tue, 10 Apr 2018 19:06:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B2D4804F7 for ; Tue, 10 Apr 2018 19:06:04 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id BAB4414601 for ; Tue, 10 Apr 2018 19:06:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3AJ63Yi009403 for ; Tue, 10 Apr 2018 19:06:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3AJ63PH009402 for fs@FreeBSD.org; Tue, 10 Apr 2018 19:06:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 205154] newfs_msdos issue Date: Tue, 10 Apr 2018 19:06:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: gonzo@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: version product cc component 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 19:06:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205154 Oleksandr Tymoshenko changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Latest |CURRENT Product|Documentation |Base System CC| |gonzo@FreeBSD.org Component|Documentation |bin --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Apr 11 10:22:47 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DB28F86F88 for ; Wed, 11 Apr 2018 10:22:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 061166A857 for ; Wed, 11 Apr 2018 10:22:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id BB4D6F86F87; Wed, 11 Apr 2018 10:22:46 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A898CF86F83 for ; Wed, 11 Apr 2018 10:22:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 42F3E6A851 for ; Wed, 11 Apr 2018 10:22:46 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5D2A51C270 for ; Wed, 11 Apr 2018 10:22:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3BAMjwM037314 for ; Wed, 11 Apr 2018 10:22:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3BAMjbB037313 for fs@FreeBSD.org; Wed, 11 Apr 2018 10:22:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 205154] newfs_msdos issue Date: Wed, 11 Apr 2018 10:22:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: k5867568@hotmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Rejected X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 10:22:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205154 RueiChang changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Rejected Status|New |Closed --- Comment #3 from RueiChang --- Sorry, it been a long time. This issue I forgot how to fix. Thanks for your reply. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Apr 11 11:32:58 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13B35F8C5D4 for ; Wed, 11 Apr 2018 11:32:58 +0000 (UTC) (envelope-from stilezy@gmail.com) Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (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 9EFB07C413; Wed, 11 Apr 2018 11:32:57 +0000 (UTC) (envelope-from stilezy@gmail.com) Received: by mail-vk0-x22d.google.com with SMTP id n64so842359vkf.12; Wed, 11 Apr 2018 04:32:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Aylmx3Jmw1KQP71hYQLfZkhgLjYCLc8rCuANdSXqP1A=; b=kF2/pZZfoWmLH7CGlIFnI0hNnYL2977zUyHp1b9qBHQN/8KD1glktLMp/mXsE8YUfG PgiJNStnMEHpz2/G6HALreFAvH9W7WBAd5fFzG9GcPh91B6Z10EVVT7e+XpT4de7oEhM M+6b6ISJI9VjgUBp/gGvkszZFRnfHswmtNtBACL5KSi7Jt/UCBYDlA7mY9oxNopjO5ok FGF1n6fntVHSa/gzY1IMl2vb7q6JMzctKghRVkbMEmH1rEhE4DKpa7KY9p5IDtBNsHYi LRWHv+/o6+L4v6ivVl7dZEMskQiGgs288oT58SOyrSXlT9kNceeCf4JdjVT1FDWHtYEc yNkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Aylmx3Jmw1KQP71hYQLfZkhgLjYCLc8rCuANdSXqP1A=; b=tSOAu6g+119ODfQVf3X/26Z4XDr3w5PF4op3itLj4N2v0XWCXHocl71J/ePtd1eiil 3cFNw+Ij98v8wsPpJsun4dkApCqOhXauJldvXmqttktyv0rVLgQzft8L8Amc6KpcSXT2 0Cf1yap4bhGJLMhq3ezFKpuVMSpFTJGidoR3wDvxmBDMf/yjpRggggNrgVTN9uF353LH zZmslZspiDrjKZVBX1J4bep8RFtKdE5iBTKwRXveissmm4lvcwwrtWWB0iR53Dv1fVvs s+b/pi979THndyLQo0Hm7FA2xfMq/fO4cUNsbENDNx3cpgY5Tl5CZH4Qrx513A0Nuh8h PYSg== X-Gm-Message-State: ALQs6tAkKFJ48sz03ovtnWeDRmrWik0VrSythjRb0OpDdtyklclJ5/4X XLbyTWuqXlx68HWVXav3HFG9dbfXbsog/FCJhRA= X-Google-Smtp-Source: AIpwx49XY5/m8tRWLdfOIusEncic9+x4YfVOhdkmJSt8aILjFz5IuWHhTHF0IYctGUZalwY9zl/fR2bRoZY43USJRmk= X-Received: by 10.31.197.197 with SMTP id v188mr3072075vkf.18.1523446376955; Wed, 11 Apr 2018 04:32:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.219.148 with HTTP; Wed, 11 Apr 2018 04:32:26 -0700 (PDT) In-Reply-To: <26e3c3b5-9baf-5499-0e12-81486cc8c839@FreeBSD.org> References: <7eba73db-3097-5c8a-eb2c-e3880fb5b501@FreeBSD.org> <672e2c84-b906-4073-0206-7eb1720adc7e@FreeBSD.org> <1629c0d63d0.2756.49a377fccbf53440a4b582c142a1ed88@gmail.com> <26e3c3b5-9baf-5499-0e12-81486cc8c839@FreeBSD.org> From: Stilez Stilezy Date: Wed, 11 Apr 2018 12:32:26 +0100 Message-ID: Subject: Re: Does setuid=on work on ZFS datasets, or is the man page for zfs misleading? To: Andriy Gapon Cc: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 11:32:58 -0000 On 10 April 2018 at 06:45, Andriy Gapon wrote: > On 06/04/2018 20:42, Stilez wrote: > > So the question stands - is there any working method to ensure files in > a ZFS > > dataset or contained dir have a predetermined owner? Including within > ACLs if I > > missed the right page? > > My assumption was that the ownership change was not an end goal and there > was a > wider context related to access management. > In other words, why do you want to change file ownership unless you want to > change the file's access rights... In my opinion, Unix file ownership is > a part > of Unix file access model. > Good question. Four reasons come to mind: 1. I'm a comparative newcomer to FreeBSD security and related matters, and don't have the skill/knowledge to make assumptions that an experienced fbsd-er might make. My assumption is that whatever owner permissions/ACLs are set at, and whatever exec rights exist, files are more vulnerable to issues I leave open or mistakes I make, if they accidentally have a privileged owner, compared to a non privileged one. A lot of work I do in CLI is done with su-ing to a privileged account. The files don't need a privileged owner, so why give them one, or expose them to having one? 2. Another reason is that some branches of the file system are accessed via Samba, and if ACLs aren't correct, Windows tends to look at the owner as the account able to fix it. If files accumulate different owners, that could become a real pain to sort out as the file system is in the millions of files. This probably isn't so important because Samba allows owner inheritance on any dir, but I'd like to rely on OS controls rather than Samba controls. 3. An old principle of computing - if something isn't needed but adds complication, don't do it. I don't need the files to have varied owners, so varied owners becomes at best useless, at worst a pain at some unforeseeable future time. 4. Finally of course, ACLs and ownership committed within short and long term snapshots never can be changed or fixed. If any of these ever do give rise to a problem, I won't be able to fix it short of an insane amount of cloning/sending/rebuilding of the pool and every snapshot in it. At present I'm currently tightening my "archived files" pool's permissions, having dealt with most other basics. I'm starting from the top down - get ownership right, then groups, then ACLs/permissions on owners/users/groups. If FreeBSD can't do ownership inheritance, I have to think whether it's actually a problem and if so what to do. Perhaps the simplest option is to treat ownership as untrusted and give null ACLs (no rights at all) to the owner; instead just condition all access rights on user/group only. As far as I understand, that should be as secure/effective, and will inherit. So instead of forcing all files to be owned by (say) userX, and giving userX some rights, I could acept that the owner is arbitrary, give the owner no rights at all, create a user or group called "data_file_owner", and give that user/group the access rights over the dataset root dir that I would have given the owner. My understanding is that even on ZFS that setup *can* be configured to forcibly inherit when files+dirs are created. Would that angle work as I intend? Any issues/warnings for me, that I should be aware of? Stilez From owner-freebsd-fs@freebsd.org Wed Apr 11 11:36:38 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE041F8C963 for ; Wed, 11 Apr 2018 11:36:37 +0000 (UTC) (envelope-from stilezy@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (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 76DF37C588; Wed, 11 Apr 2018 11:36:37 +0000 (UTC) (envelope-from stilezy@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id r184so850799vke.11; Wed, 11 Apr 2018 04:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vTXo4oczS0cjm/mfhn3U/TZtY6O3y5T1TANvz8yiVwU=; b=Ja7DrBw4Z4MFCTTVKfM7oHGGBP+J/18BxTM2A5Eri422/oKSnmwkhJWtmDFY/kQ2+d EHNPhM5PpNTrFAx2B+5m2vz2Gryg1swxyyjbyhTD9J53lY0f32j0D0y3IZ57ph1VbKpJ Sbma945Ge0FHGrFUSvDa0Tuj7W7dIlztKLVbILkcrBzRoxbz3mQJsz3iPzTDMe2ez4IM Rz1ukD2tjyyrel/7kJr5wHYTTIENX7l3uw4A9sFMN/afeKRbBDGndfUUdlnst6mgbYkF ZypETtwVN0xClcng3PWugOb59sdDKKanVZDKeiisWUHRG10ubrioJRXbM3xLGQFAEy7V TQJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vTXo4oczS0cjm/mfhn3U/TZtY6O3y5T1TANvz8yiVwU=; b=LU1ZB91oFePpSaCn28hEc9e2G5HksCoT3yhhZCLxBROxLNTLnxvv1KWXfxOB3A7iea 8nuGE+Ssg0pdkEYYrFHr1sC6BeeRAcJzOszBxfkBlMX/ie0mD7j8cwfoyHOd2keyCt3+ VssgMmRrH8PPDJ4YQnqhqlZ9gIIBmjTcs2Z/8DCpAumH+v59viBbiGYd4bgkWubO8wtE UJ4Ocsumlvva1ws85Olrf5aJIThwgzWeulzzj+xqaSJzWhf09id1eT2w7BiuZmfwj8cy pCLoHjOX45uduoE0LCEcqeSE0FPZHZoKKYtw1vcMMlxDauMT+8TP7kwXLgT+cJaZa0y2 0I5g== X-Gm-Message-State: ALQs6tCciH9Ct0zXw7ER6rycFQgw4aQXrA71cS+F2DqRjOibUzkwrXFW bl0DWYHdYJX+Lk/diZuElIp6moohkaGZgA0UChr/Vw== X-Google-Smtp-Source: AIpwx48n6nY+pC9z5+4ORYwi2bb4S+2ivygnzO2qtqf6HijSb8KEKZZsx9sX1ySDxTdBmzMkg+tYaxYChaeGPzy0pGI= X-Received: by 10.31.61.216 with SMTP id k207mr2989447vka.125.1523446596877; Wed, 11 Apr 2018 04:36:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.219.148 with HTTP; Wed, 11 Apr 2018 04:36:06 -0700 (PDT) In-Reply-To: References: <7eba73db-3097-5c8a-eb2c-e3880fb5b501@FreeBSD.org> <672e2c84-b906-4073-0206-7eb1720adc7e@FreeBSD.org> <1629c0d63d0.2756.49a377fccbf53440a4b582c142a1ed88@gmail.com> <26e3c3b5-9baf-5499-0e12-81486cc8c839@FreeBSD.org> From: Stilez Stilezy Date: Wed, 11 Apr 2018 12:36:06 +0100 Message-ID: Subject: Re: Does setuid=on work on ZFS datasets, or is the man page for zfs misleading? To: Andriy Gapon Cc: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 11:36:38 -0000 (Sorry, slight reword, my mistake, underlined correction: " So instead of forcing all files to be owned by (say) userX, and giving userX some rights, I could acept that the owner is arbitrary, give the owner no rights at all, *create a group called "data_file_owner", add my desired file+dir owner to the data_file_owner group, and give the data_file_owner group the access rights* over the dataset root dir that I would have given the owner. My understanding is that even on ZFS that setup *can* be configured to forcibly inherit when files+dirs are created." ) On 11 April 2018 at 12:32, Stilez Stilezy wrote: > > > On 10 April 2018 at 06:45, Andriy Gapon wrote: > >> On 06/04/2018 20:42, Stilez wrote: >> > So the question stands - is there any working method to ensure files in >> a ZFS >> > dataset or contained dir have a predetermined owner? Including within >> ACLs if I >> > missed the right page? >> >> My assumption was that the ownership change was not an end goal and there >> was a >> wider context related to access management. >> In other words, why do you want to change file ownership unless you want >> to >> change the file's access rights... In my opinion, Unix file ownership is >> a part >> of Unix file access model. >> > > Good question. Four reasons come to mind: > > 1. I'm a comparative newcomer to FreeBSD security and related matters, and > don't have the skill/knowledge to make assumptions that an experienced > fbsd-er might make. My assumption is that whatever owner permissions/ACLs > are set at, and whatever exec rights exist, files are more vulnerable to > issues I leave open or mistakes I make, if they accidentally have a > privileged owner, compared to a non privileged one. A lot of work I do in > CLI is done with su-ing to a privileged account. The files don't need a > privileged owner, so why give them one, or expose them to having one? > > 2. Another reason is that some branches of the file system are accessed > via Samba, and if ACLs aren't correct, Windows tends to look at the owner > as the account able to fix it. If files accumulate different owners, that > could become a real pain to sort out as the file system is in the millions > of files. This probably isn't so important because Samba allows owner > inheritance on any dir, but I'd like to rely on OS controls rather than > Samba controls. > > 3. An old principle of computing - if something isn't needed but adds > complication, don't do it. I don't need the files to have varied owners, so > varied owners becomes at best useless, at worst a pain at some > unforeseeable future time. > > 4. Finally of course, ACLs and ownership committed within short and long > term snapshots never can be changed or fixed. If any of these ever do give > rise to a problem, I won't be able to fix it short of an insane amount of > cloning/sending/rebuilding of the pool and every snapshot in it. > > At present I'm currently tightening my "archived files" pool's > permissions, having dealt with most other basics. I'm starting from the top > down - get ownership right, then groups, then ACLs/permissions on > owners/users/groups. > > If FreeBSD can't do ownership inheritance, I have to think whether it's > actually a problem and if so what to do. Perhaps the simplest option is to > treat ownership as untrusted and give null ACLs (no rights at all) to the > owner; instead just condition all access rights on user/group only. As far > as I understand, that should be as secure/effective, and will inherit. > > So instead of forcing all files to be owned by (say) userX, and giving > userX some rights, I could acept that the owner is arbitrary, give the > owner no rights at all, create a user or group called "data_file_owner", > and give that user/group the access rights over the dataset root dir that I > would have given the owner. My understanding is that even on ZFS that setup > *can* be configured to forcibly inherit when files+dirs are created. > > Would that angle work as I intend? Any issues/warnings for me, that I > should be aware of? > > Stilez > From owner-freebsd-fs@freebsd.org Thu Apr 12 10:30:29 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 046FCF86ED6; Thu, 12 Apr 2018 10:30:29 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 480E178D58; Thu, 12 Apr 2018 10:30:27 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from bsdrookie.norma.com. (asterisk.enaza.ru [91.237.76.254]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id w3CAUMZZ088475 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Apr 2018 15:30:23 +0500 (YEKT) (envelope-from eugene@zhegan.in) To: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org From: "Eugene M. Zheganin" Subject: HAST, cyclic singal 6, and inability to start Message-ID: Date: Thu, 12 Apr 2018 15:30:22 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Language: en-US X-Spamd-Result: default: False [-998.10 / 25.00] WHITELISTED_IPS(-999.00)[91.237.76.254] AUTH_NA(1.00)[] RCVD_COUNT_TWO(0.00)[2] MID_RHS_MATCH_FROM(0.00)[] DMARC_NA(0.00)[zhegan.in] FROM_EQ_ENVFROM(0.00)[] ARC_NA(0.00)[] ASN(0.00)[asn:57973, ipnet:91.237.76.0/24, country:RU] FROM_HAS_DN(0.00)[] R_SPF_NA(0.00)[] TO_MATCH_ENVRCPT_ALL(0.00)[] TO_DN_NONE(0.00)[] MIME_GOOD(-0.10)[multipart/alternative, text/plain] RCVD_TLS_ALL(0.00)[] RCPT_COUNT_TWO(0.00)[2] R_DKIM_NA(0.00)[] IP_SCORE(0.00)[ip: (-9.89), ipnet: 91.237.76.0/24(-7.82), asn: 57973(-4.89), country: RU(0.12)] X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 0.58 X-Rspamd-Queue-ID: w3CAUMZZ088475 Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 10:30:29 -0000 Hi. About a month ago I was experimenting with HAST on my servers, and, though I did have a complications with signal 6 on init phase, I was able to start it and it was working in test mode for a couple of weeks. After that I had to reboo both of them and now it doesn't start al all - both node hast is crashing on signal 6, and I'm unable to launch it as primary in either one. As soon as I switch from init or secondary to primary on either node - bad things are starting to happen - cyclic signal 6 for hastd and hangups for hastctl. Both nodes are running FreeBSD 11.1-RELEASE-pX (p1 and p6). Here's an extempt from the PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227461 I just created: ===Cut=== Node A (11.1-RELEASE-p1): ======== [root@gw0:/var/log]# service hastd start Starting hastd. [root@gw0:/var/log]# hastctl status Name Status Role Components hasta - init /dev/gpt/hasta tcp4://192.168.0.247 hastb - init /dev/gpt/hastb tcp4://192.168.0.247 [root@gw0:/var/log]# hastctl role secondary hasta [root@gw0:/var/log]# hastctl role secondary hastb [root@gw0:/var/log]# hastctl status Name Status Role Components hasta - secondary /dev/gpt/hasta tcp4://192.168.0.247 hastb - secondary /dev/gpt/hastb tcp4://192.168.0.247 Node B (11.1-RELEASE-p6): ======== [root@gw1:/var/log]# service hastd start Starting hastd. [root@gw1:/var/log]# hastctl status Name Status Role Components hasta - init /dev/gpt/hasta tcp4://192.168.0.248 hastb - init /dev/gpt/hastb tcp4://192.168.0.248 [root@gw1:/var/log]# hastctl role promary hasta usage: hastctl create [-d] [-c config] [-e extentsize] [-k keepdirty] [-m mediasize] name ... hastctl role [-d] [-c config] all | name ... hastctl list [-d] [-c config] [all | name ...] hastctl status [-d] [-c config] [all | name ...] hastctl dump [-d] [-c config] [all | name ...] [root@gw1:/var/log]# hastctl role primary hasta [root@gw1:/var/log]# hastctl role primary hastb [root@gw1:/var/log]# hastctl status (hangs) Node B dmesg: pid 26813 (hastd), uid 0: exited on signal 6 (core dumped) pid 26814 (hastd), uid 0: exited on signal 6 (core dumped) pid 26815 (hastd), uid 0: exited on signal 6 (core dumped) pid 26816 (hastd), uid 0: exited on signal 6 (core dumped) pid 26817 (hastd), uid 0: exited on signal 6 (core dumped) pid 26822 (hastd), uid 0: exited on signal 6 (core dumped) pid 26825 (hastd), uid 0: exited on signal 6 (core dumped) pid 26828 (hastd), uid 0: exited on signal 6 (core dumped) pid 26829 (hastd), uid 0: exited on signal 6 (core dumped) pid 26830 (hastd), uid 0: exited on signal 6 (core dumped) pid 26831 (hastd), uid 0: exited on signal 6 (core dumped) pid 26833 (hastd), uid 0: exited on signal 6 (core dumped) pid 26836 (hastd), uid 0: exited on signal 6 (core dumped) pid 26837 (hastd), uid 0: exited on signal 6 (core dumped) Node B messages: Apr 12 15:02:49 gw1 kernel: pid 26891 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:02:50 gw1 hastd[26679]: [hastb] (primary) Worker process killed (pid=26891, signal=6). Apr 12 15:02:50 gw1 hastd[26893]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Apr 12 15:02:50 gw1 hastd[26893]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Apr 12 15:02:50 gw1 kernel: pid 26893 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:02:51 gw1 hastd[26679]: [hasta] (primary) Worker process killed (pid=26893, signal=6). Apr 12 15:02:51 gw1 hastd[26896]: [hastb] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Apr 12 15:02:51 gw1 hastd[26896]: [hastb] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Apr 12 15:02:52 gw1 kernel: pid 26896 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:02:52 gw1 hastd[26679]: [hastb] (primary) Worker process killed (pid=26896, signal=6). Apr 12 15:02:52 gw1 hastd[26900]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Apr 12 15:02:52 gw1 hastd[26900]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Apr 12 15:02:53 gw1 kernel: pid 26900 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:02:54 gw1 hastd[26679]: [hasta] (primary) Worker process killed (pid=26900, signal=6). Apr 12 15:02:54 gw1 hastd[26904]: [hastb] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Apr 12 15:02:54 gw1 hastd[26904]: [hastb] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Apr 12 15:02:54 gw1 kernel: pid 26904 (hastd), uid 0: exited on signal 6 (core dumped) Now when I'm trying to switch A to primary: [root@gw0:/var/log]# hastctl role primary hastb [root@gw0:/var/log]# hastctl role primary hasta [root@gw0:/var/log]# hastctl status (hangs) Node A dmesg: pid 72301 (hastd), uid 0: exited on signal 6 (core dumped) pid 72328 (hastd), uid 0: exited on signal 6 (core dumped) pid 72355 (hastd), uid 0: exited on signal 6 (core dumped) pid 72389 (hastd), uid 0: exited on signal 6 (core dumped) pid 72412 (hastd), uid 0: exited on signal 6 (core dumped) pid 72436 (hastd), uid 0: exited on signal 6 (core dumped) pid 72467 (hastd), uid 0: exited on signal 6 (core dumped) pid 72496 (hastd), uid 0: exited on signal 6 (core dumped) pid 72514 (hastd), uid 0: exited on signal 6 (core dumped) pid 72530 (hastd), uid 0: exited on signal 6 (core dumped) pid 72554 (hastd), uid 0: exited on signal 6 (core dumped) pid 72584 (hastd), uid 0: exited on signal 6 (core dumped) pid 72620 (hastd), uid 0: exited on signal 6 (core dumped) pid 72656 (hastd), uid 0: exited on signal 6 (core dumped) pid 72708 (hastd), uid 0: exited on signal 6 (core dumped) pid 72759 (hastd), uid 0: exited on signal 6 (core dumped) pid 72799 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:04:40 gw0 kernel: pid 72530 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:04:41 gw0 hastd[63097]: [hasta] (primary) Worker process killed (pid=72530, signal=6). Apr 12 15:04:41 gw0 hastd[72554]: [hastb] (primary) Descriptor 8 is open (pipe or FIFO), but should be closed. Apr 12 15:04:41 gw0 hastd[72554]: [hastb] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Apr 12 15:04:41 gw0 kernel: pid 72554 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:04:42 gw0 hastd[63097]: [hastb] (primary) Worker process killed (pid=72554, signal=6). Apr 12 15:04:42 gw0 hastd[72584]: [hasta] (primary) Descriptor 8 is open (pipe or FIFO), but should be closed. Apr 12 15:04:42 gw0 hastd[72584]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Apr 12 15:04:42 gw0 kernel: pid 72584 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:04:43 gw0 hastd[63097]: [hasta] (primary) Worker process killed (pid=72584, signal=6). Apr 12 15:04:43 gw0 hastd[72620]: [hastb] (primary) Descriptor 8 is open (pipe or FIFO), but should be closed. Apr 12 15:04:43 gw0 hastd[72620]: [hastb] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Apr 12 15:04:43 gw0 kernel: pid 72620 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:04:44 gw0 hastd[63097]: [hastb] (primary) Worker process killed (pid=72620, signal=6). Apr 12 15:04:44 gw0 hastd[72656]: [hasta] (primary) Descriptor 8 is open (pipe or FIFO), but should be closed. Apr 12 15:04:44 gw0 hastd[72656]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Apr 12 15:04:44 gw0 kernel: pid 72656 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:04:45 gw0 hastd[63097]: [hasta] (primary) Worker process killed (pid=72656, signal=6). Apr 12 15:04:45 gw0 hastd[72708]: [hastb] (primary) Descriptor 8 is open (pipe or FIFO), but should be closed. Apr 12 15:04:45 gw0 hastd[72708]: [hastb] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/has td.c, line 303. Apr 12 15:04:45 gw0 kernel: pid 72708 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:04:46 gw0 hastd[63097]: [hastb] (primary) Worker process killed (pid=72708, signal=6). Apr 12 15:04:46 gw0 hastd[72759]: [hasta] (primary) Descriptor 8 is open (pipe or FIFO), but should be closed. Apr 12 15:04:46 gw0 hastd[72759]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/has td.c, line 303. Apr 12 15:04:46 gw0 kernel: pid 72759 (hastd), uid 0: exited on signal 6 (core dumped) Apr 12 15:04:47 gw0 hastd[63097]: [hasta] (primary) Worker process killed (pid=72759, signal=6). Apr 12 15:04:47 gw0 hastd[72799]: [hastb] (primary) Descriptor 8 is open (pipe or FIFO), but should be closed. Apr 12 15:04:47 gw0 hastd[72799]: [hastb] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/has td.c, line 303. Apr 12 15:04:47 gw0 kernel: pid 72799 (hastd), uid 0: exited on signal 6 (core dumped) Node A config: ============== resource hasta { local /dev/gpt/hasta on gw0 { remote tcp4://192.168.0.247 source tcp4://192.168.0.248 } on gw1 { remote tcp4://192.168.0.248 source tcp4://192.168.0.247 } } resource hastb { local /dev/gpt/hastb on gw0 { remote tcp4://192.168.0.247 source tcp4://192.168.0.248 } on gw1 { remote tcp4://192.168.0.248 source tcp4://192.168.0.247 } } Node B config: ============== resource hasta { local /dev/gpt/hasta on gw0 { remote tcp4://192.168.0.247 source tcp4://192.168.0.248 } on gw1 { remote tcp4://192.168.0.248 source tcp4://192.168.0.247 } } resource hastb { local /dev/gpt/hastb on gw0 { remote tcp4://192.168.0.247 source tcp4://192.168.0.248 } on gw1 { remote tcp4://192.168.0.248 source tcp4://192.168.0.247 } } Backtrace: (gdb) bt #0 0x000000080155a84a in thr_kill () from /lib/libc.so.7 #1 0x000000080155a814 in __raise (s=6) at /usr/src/lib/libc/gen/raise.c:52 #2 0x000000080155a789 in abort () at /usr/src/lib/libc/stdlib/abort.c:65 #3 0x0000000000414579 in pjdlog_abort (func=0x420e3f "descriptors_assert", file=0x420aeb "/usr/src/sbin/hastd/hastd.c", line=303, failedexpr=0x0, fmt=) at /usr/src/sbin/hastd/pjdlog.c:613 #4 0x0000000000408267 in descriptors_assert (res=0x80204b400, pjdlogmode=) at /usr/src/sbin/hastd/hastd.c:303 #5 0x00000000004146eb in hastd_primary (res=0x80204b400) at /usr/src/sbin/hastd/primary.c:1030 #6 0x000000000040a55a in check_signals () at /usr/src/sbin/hastd/hastd.c:359 #7 0x0000000000408852 in main (argc=, argv=) at /usr/src/sbin/hastd/hastd.c:1138 #8 0x0000000000403b0f in _start () #9 0x000000080064f000 in ?? () #10 0x0000000000000000 in ?? () (gdb) ===Cut=== If somebody has any idea how do I bring it up - please let me know. Thanks. Eugene. From owner-freebsd-fs@freebsd.org Thu Apr 12 12:21:01 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A93F6F90BFD for ; Thu, 12 Apr 2018 12:21:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 64D34761DE for ; Thu, 12 Apr 2018 12:21:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 21157F90BF7; Thu, 12 Apr 2018 12:21:01 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E8CAF90BF4 for ; Thu, 12 Apr 2018 12:21:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89E37761D2 for ; Thu, 12 Apr 2018 12:21:00 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C885512D4 for ; Thu, 12 Apr 2018 12:20:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3CCKxCd031716 for ; Thu, 12 Apr 2018 12:20:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3CCKx1B031714 for fs@FreeBSD.org; Thu, 12 Apr 2018 12:20:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 227465] [zfs][iscsi]repeatable panics on iSCSI target/zvol creation Date: Thu, 12 Apr 2018 12:20:58 +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: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 12:21:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227465 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scsi@FreeBSD.org Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Apr 12 12:31:58 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5FDD5F91A94 for ; Thu, 12 Apr 2018 12:31:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E9C9278604 for ; Thu, 12 Apr 2018 12:31:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A3A77F91A92; Thu, 12 Apr 2018 12:31:57 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91551F91A8E for ; Thu, 12 Apr 2018 12:31:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AF8E785FE for ; Thu, 12 Apr 2018 12:31:57 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 70809154F for ; Thu, 12 Apr 2018 12:31:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3CCVuss000636 for ; Thu, 12 Apr 2018 12:31:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3CCVuom000630 for fs@FreeBSD.org; Thu, 12 Apr 2018 12:31:56 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 227465] [zfs][iscsi]repeatable panics on iSCSI target/zvol creation Date: Thu, 12 Apr 2018 12:31:56 +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: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 12:31:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227465 --- Comment #1 from Andriy Gapon --- Please try stable/11 after base r332095. --=20 You are receiving this mail because: You are the assignee for the bug.=