From owner-freebsd-fs@freebsd.org Sun May 26 02:00:14 2019 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 DCE1415BC664 for ; Sun, 26 May 2019 02:00:14 +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 6E2C86C1B8 for ; Sun, 26 May 2019 02:00:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 24EC015BC663; Sun, 26 May 2019 02:00:14 +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 10EEC15BC662 for ; Sun, 26 May 2019 02:00:14 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B3826C1B4 for ; Sun, 26 May 2019 02:00:13 +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 DADCAAB7A for ; Sun, 26 May 2019 02:00:12 +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 x4Q20CtQ021272 for ; Sun, 26 May 2019 02:00:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4Q20CJR021271 for fs@FreeBSD.org; Sun, 26 May 2019 02:00:12 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 238112] Unable to create ZVOL Date: Sun, 26 May 2019 02:00:11 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: allanjude@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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 May 2019 02:00:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238112 --- Comment #1 from Allan Jude --- This error is about the snapshot, not the dataset itself. Did the dataset n= ot get mounted as well? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun May 26 17:10:18 2019 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 E691715AB58C for ; Sun, 26 May 2019 17:10:17 +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 7570D8DC1D for ; Sun, 26 May 2019 17:10:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 36C0515AB58B; Sun, 26 May 2019 17:10:17 +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 244B215AB58A for ; Sun, 26 May 2019 17:10:17 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A55B48DC18 for ; Sun, 26 May 2019 17:10:16 +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 DD53012EDF for ; Sun, 26 May 2019 17:10:15 +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 x4QHAFvl062541 for ; Sun, 26 May 2019 17:10:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4QHAFp7062540 for fs@FreeBSD.org; Sun, 26 May 2019 17:10:15 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 238112] Unable to create ZVOL Date: Sun, 26 May 2019 17:10:15 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 May 2019 17:10:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238112 --- Comment #2 from Eugene Grosbein --- (In reply to Allan Jude from comment #1) There is no file system to mount, the dataset is a snapshow of another data= set with type=3Dvolume. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun May 26 21:00:36 2019 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 B37B615B07A1 for ; Sun, 26 May 2019 21:00:36 +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 33AF56E442 for ; Sun, 26 May 2019 21:00:36 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id E145E15B0797; Sun, 26 May 2019 21:00:35 +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 A6CE015B0791 for ; Sun, 26 May 2019 21:00:35 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 287016E437 for ; Sun, 26 May 2019 21:00:35 +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 3D0B515024 for ; Sun, 26 May 2019 21:00:34 +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 x4QL0Y4w067647 for ; Sun, 26 May 2019 21:00:34 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4QL0Y74067638 for fs@FreeBSD.org; Sun, 26 May 2019 21:00:34 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201905262100.x4QL0Y74067638@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, 26 May 2019 21:00:34 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 May 2019 21:00:36 -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 Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS Open | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data Open | 235665 | panic: handle_written_inodeblock: live inodedep Open | 237067 | ZFS: Crash in vdev_dtl_reassess when using GELI w 6 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon May 27 09:56:09 2019 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 A0A8115BEB6B for ; Mon, 27 May 2019 09:56:09 +0000 (UTC) (envelope-from nutsbastogne@gmail.com) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 982048CD58 for ; Mon, 27 May 2019 09:56:08 +0000 (UTC) (envelope-from nutsbastogne@gmail.com) Received: by mail-ed1-x535.google.com with SMTP id w33so22510461edb.10 for ; Mon, 27 May 2019 02:56:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pp1FSK5GHJs/RXL+1qWKci3tLFfwrYRlDNEJswdorbo=; b=X1iK8xyyMZO7PjZBvBgE8EVND0+vFhT7MafTZROZeX3AZcAuXrkGtUa3y2JYddULko c+/m/rfrSX4hj+2j9T8JUwI5OW9sbfVV8TfViq/U4x03Vv/kh9iptcp+mzEMQWjtZMq5 DUzUqFLcvtecP9q7XIx/LfDgQF45h+usDU0VaqTL8yNRe6pnk2ncfqMc1J9w/zfmXe5P nKiWqMzfgfxBdIeQP/HmpZ4esyfMS7nF9dgqtTM/CN2Sb1oJ0nGyR7UwwIZxDAO0iaLO 3hPwZHECFMBxOddSoHC+iEaue14PijKxVolOsi5GcIU8rp7kM1XXPVqgG3F4XXZt9qhO zYtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pp1FSK5GHJs/RXL+1qWKci3tLFfwrYRlDNEJswdorbo=; b=Z/ZC9ArQvE30y8bGIvxtvmDo+tcYVVgVe4CNUnOO3VdfZ1QUrhHnUHz4eKUIak6Gn7 IZHqTDscuRJPRzj+QeeRYcxB1q6Zo4c8vTUM677rWEMaedP/EHNMH22GJ4QaiDdf1YrU msvL86vCMEh/dfwbNkZkoYv0tcUIT891HJT1Mw7J2vSU86YZP2ZqrNe7xFS8yAQUL/F5 KHEBEln9HCetFGYUWkZvAQcYO0/dga0lKtbaxnRTEyX8MTQ9MWBrUS3jDZcxnFuHKRJO 1aiAx646k+8l75PNgnUzUn9Pms7mfibEdKvPTT8fiP1h869Lega5I1oJow8tI9eQSote cqAg== X-Gm-Message-State: APjAAAUf3YfLIlh0uXJ7DV542A4CnfxaqEUAslxaFk8Cf+W/Wuzf/l8Q J/5JkWFUd2ZRkgAz9TGo/uu4Ld/hrZQ9Nr7pl1lygK3c X-Google-Smtp-Source: APXvYqxN5QJmvZbVovr4mURx6Ym6C0sVOFfzNKWIHR6VeRwU7Gygp8vHSUoUXzUJeeBPfDLaxRJtkI60QjxqncZj4Ms= X-Received: by 2002:a50:91e3:: with SMTP id h32mr27735786eda.103.1558950967403; Mon, 27 May 2019 02:56:07 -0700 (PDT) MIME-Version: 1.0 From: Nuts Bastogne Date: Mon, 27 May 2019 11:55:56 +0200 Message-ID: Subject: ZFS space consumption To: freebsd-fs@freebsd.org X-Rspamd-Queue-Id: 982048CD58 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=X1iK8xyy; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of nutsbastogne@gmail.com designates 2a00:1450:4864:20::535 as permitted sender) smtp.mailfrom=nutsbastogne@gmail.com X-Spamd-Result: default: False [-6.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[5.3.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; IP_SCORE(-2.77)[ip: (-9.28), ipnet: 2a00:1450::/32(-2.19), asn: 15169(-2.29), country: US(-0.06)]; NEURAL_HAM_SHORT(-0.92)[-0.924,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2019 09:56:10 -0000 Hi All, I'm confused about the zfs consumption of space. I'm using ZFS to create clone from a sysprep and use it as a zvol for vm connected via iscsi. The zvol has a size of 256GB. But several dataset have a space comsuption bigger than the size of the zvol. I thought this could be happen when we use snapshot but this is not my case. here information from one zvol impacted : type volume volsize 256G used 483G referenced 507G copies 1 refreservation none compression lz4 usedbydataset 483G written 483G logicalused 238G logicalreferenced 251G logicalused and logicalreferenced are correct, so the vm didnt see a disk bigger than 256GB. As used, usedbydataset, referenced properties don't include metadata neither snapshot i dont'know what it could be. After some research on the web some people had the same issue du to the blocksize of their disk and had to change the ashift to 12. but this is our configuration already. disk : (from diskinfo -v) SSD 512 # sectorsize 3840755982336 # mediasize in bytes (3.5T) 7501476528 # mediasize in sectors 4096 # stripesize volblocksize = 16k ashift = 12 What i can check to go deeper on this issue ? or this is just a normal behavior du to my configuration ? From owner-freebsd-fs@freebsd.org Mon May 27 10:29:12 2019 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 65FF715BF2CC for ; Mon, 27 May 2019 10:29:12 +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 EBB0F8DA7A for ; Mon, 27 May 2019 10:29:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A9D3F15BF2CB; Mon, 27 May 2019 10:29:11 +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 9682C15BF2CA for ; Mon, 27 May 2019 10:29:11 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2692F8DA73 for ; Mon, 27 May 2019 10:29:11 +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 4ED381C4D7 for ; Mon, 27 May 2019 10:29:10 +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 x4RATAHZ016993 for ; Mon, 27 May 2019 10:29:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4RATA2T016992 for fs@FreeBSD.org; Mon, 27 May 2019 10:29:10 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 238112] Unable to create ZVOL Date: Mon, 27 May 2019 10:29:10 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: crest@rlwinm.de 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 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2019 10:29:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238112 crest@rlwinm.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crest@rlwinm.de --- Comment #3 from crest@rlwinm.de --- Try a shorter name. In FreeBSD < 12.0 the mount point length was quite short (IIRC 88 bytes). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon May 27 10:50:11 2019 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 11A9915BF924 for ; Mon, 27 May 2019 10:50:11 +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 9D44E8E605 for ; Mon, 27 May 2019 10:50:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5EC8815BF923; Mon, 27 May 2019 10:50:10 +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 4C1F515BF922 for ; Mon, 27 May 2019 10:50:10 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC5058E601 for ; Mon, 27 May 2019 10:50:09 +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 41E471C7BB for ; Mon, 27 May 2019 10:50:09 +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 x4RAo90l056179 for ; Mon, 27 May 2019 10:50:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4RAo9cp056178 for fs@FreeBSD.org; Mon, 27 May 2019 10:50:09 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 238112] Unable to create ZVOL Date: Mon, 27 May 2019 10:50:07 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mail@rubenvos.com 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 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2019 10:50:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238112 mail@rubenvos.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mail@rubenvos.com --- Comment #4 from mail@rubenvos.com --- @crest: I've been looking for a "fix" for quite some time now : http://freebsd.1045724.x6.nabble.com/zfs-snapshot-make-dev-63-character-lim= it-td6147061.html Does your comment imply that the limits involved have been altered/upped in 12.0 ? Kind regards, Ruben --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon May 27 10:53:11 2019 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 91BBB15BFB3A for ; Mon, 27 May 2019 10:53:11 +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 295D48E96B for ; Mon, 27 May 2019 10:53:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DCBE715BFB39; Mon, 27 May 2019 10:53:10 +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 C8CBF15BFB38 for ; Mon, 27 May 2019 10:53:10 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 599D58E965 for ; Mon, 27 May 2019 10:53: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 85C2D1C91D for ; Mon, 27 May 2019 10:53:09 +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 x4RAr9on068772 for ; Mon, 27 May 2019 10:53:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4RAr9N5068771 for fs@FreeBSD.org; Mon, 27 May 2019 10:53:09 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 238112] Unable to create ZVOL Date: Mon, 27 May 2019 10:53: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: 11.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: crest@rlwinm.de 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2019 10:53:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238112 --- Comment #5 from crest@rlwinm.de --- As part of the 64 Bit inode support a lot of those limits got increased (if= you have to break the ABI make it count). IIRC the limit went from a few dozen bytes to 1024 in FreeBSD 12. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon May 27 11:16:20 2019 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 14D0B15C01DA for ; Mon, 27 May 2019 11:16: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 A022D8F329 for ; Mon, 27 May 2019 11:16:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5F4E215C01D9; Mon, 27 May 2019 11:16:19 +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 4C9CE15C01D8 for ; Mon, 27 May 2019 11:16: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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC8098F327 for ; Mon, 27 May 2019 11:16:18 +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 EFDC01CBFF for ; Mon, 27 May 2019 11:16:17 +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 x4RBGH6H014863 for ; Mon, 27 May 2019 11:16:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4RBGHZ8014860 for fs@FreeBSD.org; Mon, 27 May 2019 11:16:17 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 238112] Unable to create ZVOL Date: Mon, 27 May 2019 11:16:17 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2019 11:16:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238112 --- Comment #6 from Eugene Grosbein --- (In reply to crest from comment #3) Have you actually read PR description? It is not about how to shorten the n= ame. It is about warning message being too cryptic for user and limit being obsc= ure. And no, I've just checked stable/12 sources and they were not changed for t= his case: same mentioned function do same things and limit is SPECNAMELEN minus strlen("zvol/"). And SPECNAMELEN is still 63 in stable/12. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon May 27 11:28:09 2019 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 EB30915C0512 for ; Mon, 27 May 2019 11:28:08 +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 827898FA6D for ; Mon, 27 May 2019 11:28:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 402AF15C0511; Mon, 27 May 2019 11:28:08 +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 2D59B15C0510 for ; Mon, 27 May 2019 11:28:08 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B6F118FA68 for ; Mon, 27 May 2019 11:28:07 +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 025D51CD61 for ; Mon, 27 May 2019 11:28:07 +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 x4RBS6cX034915 for ; Mon, 27 May 2019 11:28:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4RBS6Y1034914 for fs@FreeBSD.org; Mon, 27 May 2019 11:28:06 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 238112] Unable to create ZVOL Date: Mon, 27 May 2019 11:28:07 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2019 11:28:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238112 --- Comment #7 from Eugene Grosbein --- (In reply to crest from comment #3) This is not about mounting anything. The dataset is volume, not file system. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon May 27 13:20:52 2019 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 927C915940FC for ; Mon, 27 May 2019 13:20:52 +0000 (UTC) (envelope-from nutsbastogne@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 818986CD4F; Mon, 27 May 2019 13:20:51 +0000 (UTC) (envelope-from nutsbastogne@gmail.com) Received: by mail-ed1-x529.google.com with SMTP id w37so26699151edw.4; Mon, 27 May 2019 06:20:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=V3RsFyM97UXQXpVryWb0gDpoqHUI7Hb/kLJkecXnTvo=; b=G3ul6P3jgqgu9WG2YsV/yWEEDQayueqg5vuHeFa+BSN+Dge0B3sCy+mROlizH8jBgq wYel/ZG1cdmowy6ls71e5fsFAYa9oFrDfuQic+1zsHE1l8wrsBfQd9qorHAhaLBvFuBk 3KFoiZmYHa8i4MuZjY5TvHigUBRDSYjKhMDz8mMXDoJNbxkrP3hTGJW7hGq9J0D1fKHO trTDsd+qSZZi5WVDwqYcVABWjDiuEHeAw9zpN8SDh8uQ1qZctjRr51/pAXXeXUWfLnea mseX4GbuD4mcySfmSnNGm55h9+ugz0fYLI3Zjizc0dEhN0D4kBp3ZO0oM8FGOW2ENEb+ lqpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=V3RsFyM97UXQXpVryWb0gDpoqHUI7Hb/kLJkecXnTvo=; b=IlKpi3vVmFjqsVjfo3XDNZ1p+NmMNvuettchcTctvkraNfJsD7IAGiiS0d6jTAToEw wlI7NrbQwIzanPw2tncEuqP+Ja6utRo3w3bbyNwLuykAJbodo3qpuvIIZIJFeM76N+dS O/Rjmk63X1hiRIpfmUqBSQl59BkovCMqWZB5c7rB7xphXkrnZp9zV7exiSfiYkd/bcfZ 0lvfQYeCRkauqfWdvHfe7ZQhNGAOO8LKm+O7pvsTuO/l6M2Qq5MO3kEUuwez18TdGZNl ZQtD053unPfNRyR1aD07bhHLaBVTgzYRWVYPtJ6QwRpA33d+mLxoTZpLwwfT3hkzjxuq BXzQ== X-Gm-Message-State: APjAAAW6nwPkmrn5dfidC3zh+H/d9NuhXflj7rQnMbtADZmyCIXKddHj RdtP/8Z+CzrCdnu1HzNIaHvUN/qmXEjYkUvKak9+Ramv X-Google-Smtp-Source: APXvYqyCNiXZUVpV8rdwbdLxd3vKjedBhfbGeS0FC1ybW0V48H3uQ/Ac31enbkuCAttIdJ1k6GiMB+OvlQZOTBlPrw0= X-Received: by 2002:a17:906:1fcb:: with SMTP id e11mr89067770ejt.221.1558963250247; Mon, 27 May 2019 06:20:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nuts Bastogne Date: Mon, 27 May 2019 15:20:39 +0200 Message-ID: Subject: Re: ZFS space consumption To: Stefan Esser , freebsd-fs@freebsd.org X-Rspamd-Queue-Id: 818986CD4F X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=G3ul6P3j; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of nutsbastogne@gmail.com designates 2a00:1450:4864:20::529 as permitted sender) smtp.mailfrom=nutsbastogne@gmail.com X-Spamd-Result: default: False [-6.75 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[9.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.99)[-0.991,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.75)[ip: (-9.22), ipnet: 2a00:1450::/32(-2.19), asn: 15169(-2.29), country: US(-0.06)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2019 13:20:52 -0000 Hi Stefan, Thanks for your answer. The compressratio and refcompressratio are : compressratio 1.05x refcompressratio 1.07x Maybe i'm wrong but i don't think this ii related to my "issue" and if i understand well, the compression should decreased the space used property not the logicalused property. Le lun. 27 mai 2019 =C3=A0 13:47, Stefan Esser a =C3=A9cri= t : > Am 27.05.19 um 11:55 schrieb Nuts Bastogne: > > Hi All, > > > > I'm confused about the zfs consumption of space. > > > > I'm using ZFS to create clone from a sysprep and use it as a zvol for = vm > > connected via iscsi. > > The zvol has a size of 256GB. > > But several dataset have a space comsuption bigger than the size of the > > zvol. > > I thought this could be happen when we use snapshot but this is not my > case. > > > > here information from one zvol impacted : > > type volume > > volsize 256G > > used 483G > > referenced 507G > > copies 1 > > refreservation none > > compression lz4 > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Might that be the answer? > > Look at the current compression ratio ... > > > usedbydataset 483G > > written 483G > > logicalused 238G > > logicalreferenced 251G > > > > logicalused and logicalreferenced are correct, so the vm didnt see a di= sk > > bigger than 256GB. > > As used, usedbydataset, referenced properties don't include metadata > > neither snapshot i dont'know what it could be. > > > > After some research on the web some people had the same issue du to the > > blocksize of their disk and had to change the ashift to 12. but this is > our > > configuration already. > > > > disk : (from diskinfo -v) > > SSD > > 512 # sectorsize > > 3840755982336 # mediasize in bytes (3.5T) > > 7501476528 # mediasize in sectors > > 4096 # stripesize > > > > volblocksize =3D 16k > > ashift =3D 12 > > > > What i can check to go deeper on this issue ? > > or this is just a normal behavior du to my configuration ? > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > > > From owner-freebsd-fs@freebsd.org Tue May 28 03:51:37 2019 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 4348715B4A9B for ; Tue, 28 May 2019 03:51:37 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 86B3794277 for ; Tue, 28 May 2019 03:51:35 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: by mail-vs1-xe36.google.com with SMTP id q13so11917048vso.2 for ; Mon, 27 May 2019 20:51:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphix.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=j6dLzbzSmv1xswgetI4RuFTSP4AJ8FDPDu9uxn1MShQ=; b=akbh1Efi5PLmn3p/NU1K1+PcUtQ45uRB0Lu5R8xoAeSQnGrEdshDSa3qqvzJ0Y5vQC 6ckEIVeOb/snSV9e6jd5ykCd8LP6jDUAOT7zjOp0/7JNsidH9b+MyGgt9+eGUFa/YVZ6 JwLkDeruTGKBWbQZrorgQuYxcpjA9awM7rBGo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=j6dLzbzSmv1xswgetI4RuFTSP4AJ8FDPDu9uxn1MShQ=; b=IIhJtFSQsLiLJk3iIr/wO9BY2LlE3RuoNw/DURoVfoPhJ0yPsAJtAfhY7Vd8/6nt/y AXXTC/rInGeTqbjIRq8NJMwoDVv/dzzq7+VEmNVOUYvOl+72IH6vmaP8B2+5FCKYOfXq V572FPG6kRh9vAoQGhxMxzsE3NDPKxPJAeBMae29wjq+7DccEo572OnKDC96t/hxrhlB XaSaYqWmw6YHVFumTqOhU5yNU7wVTK4zAwLeDXjfNFreb1xJS3/Y5HW4MMAc8Z1u9Cx2 cR3jdBYha5Sjg5cVEyqA9fcuBwOSvqwq1c6tSo3Qrf25rQl7nrvtPiSZamEdOBDfKUKP RztQ== X-Gm-Message-State: APjAAAUIu/wvKQd5vUUQTvvYec8EZxR+8JaTkzB7Z2gysVEL29d8N0Qv ad2katlJjCjVK00nXNP5uaLZQMr7KtdynhO310me+BJJ X-Google-Smtp-Source: APXvYqybK2e+M00Eycqd5e0y7+ajyb9ODM0ICC+WECVaKrVmtvFvd1nrU+BE+YRKPIZpq3KeeaeUK6u8lFjHaczLvY8= X-Received: by 2002:a05:6102:101a:: with SMTP id q26mr34443992vsp.56.1559015494248; Mon, 27 May 2019 20:51:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Ahrens Date: Mon, 27 May 2019 20:51:23 -0700 Message-ID: Subject: May OpenZFS Leadership Meeting To: developer , illumos-zfs , zfs-devel@list.zfsonlinux.org, zfs-devel@freebsd.org, freebsd-fs , zfs-discuss X-Rspamd-Queue-Id: 86B3794277 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=delphix.com header.s=google header.b=akbh1Efi; dmarc=pass (policy=none) header.from=delphix.com; spf=pass (mx1.freebsd.org: domain of matthew.ahrens@delphix.com designates 2607:f8b0:4864:20::e36 as permitted sender) smtp.mailfrom=matthew.ahrens@delphix.com X-Spamd-Result: default: False [-6.75 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[delphix.com:s=google]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[delphix.com:+]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,aspmx.l.google.com,aspmx2.googlemail.com,alt2.aspmx.l.google.com,aspmx3.googlemail.com]; RCVD_IN_DNSWL_NONE(0.00)[6.3.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.99)[-0.991,0]; DMARC_POLICY_ALLOW(-0.50)[delphix.com,none]; IP_SCORE(-3.05)[ip: (-9.61), ipnet: 2607:f8b0::/32(-3.29), asn: 15169(-2.28), country: US(-0.06)]; FORGED_SENDER(0.30)[mahrens@delphix.com,matthew.ahrens@delphix.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[mahrens@delphix.com,matthew.ahrens@delphix.com]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 03:51:37 -0000 The next OpenZFS Leadership meeting will be held tomorrow, May 28, 1pm-2pm Pacific time. We don't have much on the agenda for this month, so if there are things you'd like to discuss, this is a good opportunity - send me an email or edit the doc :) Everyone is welcome to attend and participate, and we will try to keep the meeting on agenda and on time. The meetings will be held online via Zoom, and recorded and posted to the website and YouTube after the meeting. The agenda for the meeting will be a discussion of the projects listed in the agenda doc. For more information and details on how to attend, as well as notes and video from the previous meeting, please see the agenda document: https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAnWHhV-BM/edit --matt From owner-freebsd-fs@freebsd.org Tue May 28 09:45:07 2019 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 51C5615BC4E2 for ; Tue, 28 May 2019 09:45:07 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Received: from unimail.uni-dortmund.de (mx1.hrz.uni-dortmund.de [129.217.128.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "unimail.tu-dortmund.de", Issuer "TU Dortmund CA - G01" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 938577082B for ; Tue, 28 May 2019 09:45:01 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Received: from [129.217.43.37] (kalamos.cs.uni-dortmund.de [129.217.43.37]) (authenticated bits=0) by unimail.uni-dortmund.de (8.16.0.41/8.16.0.41) with ESMTPSA id x4S9YaHQ002278 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 28 May 2019 11:34:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tu-dortmund.de; s=unimail; t=1559036076; bh=m4TH30rguyOqa/zDzXTfSKglLvnVWUb4KXIoF/hWKCg=; h=To:Cc:From:Subject:Date; b=bww2jPBVUWDPZjQ7HNKslGP8H5GsJ6G7LVEGVFdqVXyw5TE585nc+/M97NbPJLPdu RMvxhCc/qhiOqvixyMDeSPx45IfwlldO5YztddeZ1FWGT7a/UiOPlHhoNAPGrPI9eF gnQcnLYJbGGPiOU3xBI8sDKUED7+dloTukL0WbKg= To: freebsd-fs@freebsd.org Cc: Horst Schirmeier From: Alexander Lochmann Subject: RFC: LockDoc - Detecting Locking Bugs in the FreeBSD Kernel Openpgp: preference=signencrypt Autocrypt: addr=alexander.lochmann@tu-dortmund.de; prefer-encrypt=mutual; keydata= mQINBFQIyUEBEADZ+x+Ssg/46SiU66zm2lPGYAdqYfmXVv+sf/23+/KSj0FQHZKywzWjsmgR vWZZVlGJolwcW3MJ/g6ctZeOpfYiZVpzbZwNgKU0ETGjUmqmlq5/o5KnENKOimZzaKSaNn9p IC+EIeWXvu7pQjW0w1bK/RVVNw0p1Iz82W4Z+vKtD8CS+YJLAcZ6YoZMvQEg84O9odlV2Ryp oVj9EzHH40TWEdtgd4pQkaOks01PEr19sJXUjnP0VxLfs91AZjRnmGJKnI4HcrOKwquoQEeL DtHCxK0VNeoXCWkz33uBxSL5cicQ7D09hxjWthMilUpDZT94x0K452q4nybQ1TSLTYC8mlW+ xKUvJmqfHZbITJ10dTgjNvOe0kLbpXeQ1789lNmnA9bkQAK5Cefo55WbXmr1Mo3PV7y0XCib OaiijPlZo/Isc03EOK3lHPK8NuY8G+ftvphO4RyXCUWXw/o01cDnPaIEcTWkUbXvMhf/6ltP 1QWEfkguzGVjTw7Xssm9YuokC+P+49JKRyZzyCJZ022OxMlsX6c1BNZ4+cWUNmn6xr1xRNse SglpMLL1m3K1KuLf1hdAor6PBzFLiLa33lUhsWtg1ACFhpfZZOQRVas2McXTYUUpmCzOYI5F +km5q6cZStr9m7O3Y3DDGotiaJDpLtATwZ4MIM4ADbg/xl6ZgwARAQABtDZBbGV4YW5kZXIg TG9jaG1hbm4gPGFsZXhhbmRlci5sb2NobWFubkB0dS1kb3J0bXVuZC5kZT6JAj4EEwECACgF AlQIyUECGyMFCQlmAYAGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEFk+7QW8Pvb9I34Q AIEGy9Pt1nK8r+0baVF5KBXzoZuQIQ7ZfxJ0MFrCQSvRYEWevm2a0p5lBDOpb/VL8VtYMVO2 xZewerWoXyWMIeWmmCeSuVGdLDT/YV6BA54KzJkptmXxQaUVdiY+Fl0jxFODAXvSxI36MdzQ PFMwcSqxs5lZaxxyUWPidwanaQ5QNkShY2ljFD8gnKALiCxd/PqexLRlLinvqJ01EArxmPum PeA6nckWh4PGk1IGm7FiNZ5TYhCaq9lh5Hg5LsSJhJrOfgeT92hI7cLEwjKvRLrjH+NzbNFW tX4gWlwUHU5afP71AY9RfNXt/Ul8w+R5CX6W9xaiuS5MZZS5SZYeHU5QAfqaomSRkVb2uqwf Lahx76ONwOtsVbMLshaA9mxsgMUNDhOYxyKQOnYz2qThwZloEOgICaxIZG7WJug0HL4YGXG7 EJdFn2fEs6WUCeZ1DWGUGf92N+AFMBBJ/HP1fVlkAwuubOF7QdPTrsGwd8Tz0tkFzxd/W496 OvGO/OZZCw+pKnDODJyXtBs3jr6cu9evEasiaQEVL+nfhTGyNVW+dldn6uj7tJ3qLQbuk+o4 BLrUwjWXLdA4nMEGgtm8WabEyjoolP2BfjMTgEFQHhxaW0t4fIYLO5kM3lNphwXxmA4Lys+x RCPyLSitlqwrqDW19v56NTipcAqsczgpGZRGuQINBFQIyUEBEACcIW4RnxXteHv/Hl4/l926 sozOCL8iwT/OD9QvL3171Y1MDX8bt8LneMoh5RG4SegtdVaA4jLkdv8BTmRbY7qZrzJjYJX4 PUyvmuZbqpa+PF1c5uqUcuhwpXlQAupL1dCgO5p1xbdCxEOB9Lm+2hUFJy1LsvidwieJdFqR l09a/IypKtqywJxa6sSJp9ZPPCPMJnJxIVzGqAwHWO84LfIX5I6BRUbqAhxljJm40Bk79z+P HdytD0SaTuWIhsVYRFchKLxqbXokUhJaWupE1v4xFe2Sqty9vSCrJZMRZRTLvngRxbJVHIJJ sK685HNS3QJSrFtql+SGMkPHpX92+ZCmyTH6DAQ3Y0MtjJTcoYKu3fI8KT9BSsLuuXUToX7Y l4RbFB5s0rwZ2XMweKJdkwypC5fSZmLtEwgimMQ4VfBBUPJCvHhmvOHKX3Wls99D7xYWP7Lr iinmjbduiaO/A+bLjAdLqqGJpjQ7T3z+vqxzp3IaeJ3ObSnnnPppcKVAf6qZqu5Yfc31q/OY n19WyGIhwK3MuuVmjatxMmGgkSxzgTTP3jFQ008qymPcgrvgOR+MECCIpXjOMfenOhhsKnhu F7hxUS/6JtYKsEMEwJXVN509sNhJiEzSY9q+VYn9IArHSBMmpi5l6XvI1iwPD9HRNursPxKV lfi8lQsC7zxuTQARAQABiQIlBBgBAgAPBQJUCMlBAhsMBQkJZgGAAAoJEFk+7QW8Pvb9EkkP /2LyGWWOoTAGBhzvgKiYzarS3WQNZCuFHSfB/XXg4SRSX3NsxGVZWdLvVVgzWo1+tC1Qk6wO IVQSSw20wQXe8boZ8yiB8eM4ohfS0lySO9gOkQLYLijWg3JIYwTbqyK2X8LpbCs7eUTXM9NO 6pmVtoc3LBBIXQElX8ir0BZZ19OCSConTkyVHYK6IbEJ11PxjJG5ZS7anI4FQt0muzykZrhk bmf5IV3DtJ/KUfhQjnJa2B/KoT7F6vpTCoyPtaBUHQXEAb2NaZVwF06WXsqfX4yleym3Jlfx Rfa4+BOJ4Gf2EFd3wYCsIb33ulaXBLWa8w3A/FdQSW9NBM4iYlPxRg+5eXn+oajpyKqPLetH WRNMN4NSHVSpu+JRqRlTDO3HCn/peQ0OB/Iaf3HN3DLZdbjtZY40xl1iR9TMgD2fn2MlAFy3 dSKfjeCAQYP9can1MgebE729MI7QhtzuUYdHy+iJO/ENNlSgFo5DLwRqssEGqWag0xWPgcni UAERITTzHJeevSeZh5ThHyD173Pwn+tIhR4bK5RFy/gnzwqHckl8Hw7o06m51yI4dUVeatNT mAiNrmW3iQnvehjLZOYXOXx4ovsWdvQn01dUo3gCXdEWQ5yQLOQRGTCcrq1hzCEd//viy9oT spNrcZJf1pbo3EKkCwUPAltq51ramtYzOu4K Message-ID: <67482bf7-be1a-8f8d-ca80-2087bfc8cf99@tu-dortmund.de> Date: Tue, 28 May 2019 11:34:36 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="R8bcOoHpld8vLVY30TDF0wrUdb6YxMbAJ" X-Rspamd-Queue-Id: 938577082B X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tu-dortmund.de header.s=unimail header.b=bww2jPBV; spf=pass (mx1.freebsd.org: domain of alexander.lochmann@tu-dortmund.de designates 129.217.128.51 as permitted sender) smtp.mailfrom=alexander.lochmann@tu-dortmund.de X-Spamd-Result: default: False [-6.13 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:129.217.128.0/24]; HAS_ATTACHMENT(0.00)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DKIM_TRACE(0.00)[tu-dortmund.de:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_MED(-0.20)[51.128.217.129.list.dnswl.org : 127.0.11.2]; SIGNED_PGP(-2.00)[]; MX_GOOD(-0.01)[esa3.itmc.tu-dortmund.de,esa4.itmc.tu-dortmund.de]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; IP_SCORE(-0.00)[asn: 680(-0.02), country: DE(-0.00)]; ASN(0.00)[asn:680, ipnet:129.217.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[tu-dortmund.de:s=unimail]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_MED(0.00)[tu-dortmund.de.dwl.dnswl.org : 127.0.11.2]; NEURAL_HAM_SHORT(-0.82)[-0.818,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[tu-dortmund.de]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RBL_COMPOSITE_RCVD_IN_DNSWL_MED_DWL_DNSWL_MED(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 09:45:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --R8bcOoHpld8vLVY30TDF0wrUdb6YxMbAJ Content-Type: multipart/mixed; boundary="f0bfobHOpjofq6rsGsDkAd5w5OsOYqjj6"; protected-headers="v1" From: Alexander Lochmann To: freebsd-fs@freebsd.org Cc: Horst Schirmeier Message-ID: <67482bf7-be1a-8f8d-ca80-2087bfc8cf99@tu-dortmund.de> Subject: RFC: LockDoc - Detecting Locking Bugs in the FreeBSD Kernel --f0bfobHOpjofq6rsGsDkAd5w5OsOYqjj6 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi folks, during the past months we've been developing LockDoc, a trace-based approach of Lock Analysis in the FreeBSD kernel. LockDoc uses execution traces of an instrumented FreeBSd kernel to automatically deduce locking rules for all members of arbitrary kernel data structures. The traces are gathered running a manually selected fs-specific subset of the Linux Test Project in a virtual machine. We use the Linux Test Project, because we weren't able to find such benchmark suite for FreeBSD and we initially applied our approach to Linu= x. These locking rules can be used to generate a comprehensive locking documentation and to reveal potential bugs. LockDoc generates rules for each tuple of (data structure, member, {r,w})= =2E It completely ignores any atomic_*() function. Accesses during initialization and destruction of objects are also ignore= d. The output of LockDoc looks like this: cdev_priv member: cdp_c.si_usecount [r] (5 lock combinations) hypotheses: 24 34.8% (24 out of 69 mem accesses): EMBOTHER(vnode.v_lock[r]) -> EMBOTHER(vnode.v_interlock[w]) -> devmtx:89(sleep mutex[w]) 34.8% (24 out of 69 mem accesses): EMBOTHER(vnode.v_lock[r]) -> devmtx:89(sleep mutex[w]) 34.8% (24 out of 69 mem accesses): EMBOTHER(vnode.v_lock[r]) -> EMBOTHER(vnode.v_interlock[w]) 34.8% (24 out of 69 mem accesses): EMBOTHER(vnode.v_lock[r]) 63.8% (44 out of 69 mem accesses): EMBOTHER(vnode.v_lock[w]) -> EMBOTHER(vnode.v_interlock[w]) -> devmtx:89(sleep mutex[w]) 63.8% (44 out of 69 mem accesses): EMBOTHER(vnode.v_lock[w]) -> EMBOTHER(vnode.v_interlock[w]) 65.2% (45 out of 69 mem accesses): EMBOTHER(vnode.v_lock[w]) -> devmtx:89(sleep mutex[w]) 65.2% (45 out of 69 mem accesses): EMBOTHER(vnode.v_lock[w]) 98.6% (68 out of 69 mem accesses): EMBOTHER(vnode.v_interlock[w]) -> devmtx:89(sleep mutex[w]) 98.6% (68 out of 69 mem accesses): EMBOTHER(vnode.v_interlock[w]) ! 100% (69 out of 69 mem accesses): devmtx:89(sleep mutex[w]) 100% (69 out of 69 mem accesses): (no locks held) In this example LockDoc concludes that the lock "devmtx:89(sleep mutex[w])" is necessary for reading cdev_priv.cdp_c.si_usecount. In this case, devmtx means a global lock of type sleep mutex. To be more precise, the write lock (--> "[w]") of devmtx is needed. Btw, EMBSAME stands for the lock embedded in the data type being accessed= =2E EMBOTHER respectively stands for a lock embedded in another object that is currently not accessed. Based on this methodology, we can determine code locations that do not adhere to the deduced locking rules. The reports on rule-violating code include the stack trace and the actual locks held. We've now created a series of bug reports for the following data types: struct devfs_dirent, devfs_mount, mount, namecache, pipepair, and vnode We present the counterexamples for each tuple of (data structure, member, {r,w}). Depending on the complexity of the callgraph, the counterexamples are either embedded in the callgraph or the callgraph is shown below them. In the latter case, zooming can be enabled via a button in the heading. We kindly ask you to have a look at our findings and send us some comments back: https://ess.cs.tu-dortmund.de/lockdoc-bugs/freebsd/ If you are interested in the derived locking rules, have a look at: https://ess.cs.tu-dortmund.de/lockdoc-bugs/freebsd/all-txns-members-locks= -hypo-nostack-nosubclasses.txt It might be possible that LockDoc considers a certain access as a bug due to an incomplete blacklist of init and destroy functions. Hence, we appreciate any feedback refining our blacklist. Best regards, Alex and Horst --=20 Technische Universit=C3=A4t Dortmund Alexander Lochmann PGP key: 0xBC3EF6FD Otto-Hahn-Str. 16 phone: +49.231.7556141 D-44227 Dortmund fax: +49.231.7556116 http://ess.cs.tu-dortmund.de/Staff/al --f0bfobHOpjofq6rsGsDkAd5w5OsOYqjj6-- --R8bcOoHpld8vLVY30TDF0wrUdb6YxMbAJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEElhZsUHzVP0dbkjCRWT7tBbw+9v0FAlztAKwACgkQWT7tBbw+ 9v1weg/+NVynCPz85Liz4TZShjNqqn+7Va9Suy6sLxoEwVEL3N7lLoZdTPafqpsp a/RZNtmGNvosW1XZsmQ3xp19JKmVog0xs8MnhlyTCsY8Qm/ZqSSCN3c0VVnq1JTP e0eXmSu7FR795X9ZkkycuO9HzZWypPBErgKgwuErlizGEDPoeZJaLJIhS3/7FecV tq/0wm/aybfMX7f1JJK/zYC2u9DQDDBTTnRkjzMVc2iCQAuMXmOMpNirjla41LcB KtcazudMbPNPN/3NxE+l0HFmkSM8CQ4QuikfiAbhgHHFEznoYJP0xlw4kQl2Xyjp Bi26xRjDrbBL22eNi/aOtmrFdqWnddKRaXVtDsG4+m9NTwCf8s23sL9ctflf3tpB u8S0XUV6CxvUAqtFUXxbIUhOOY13k1knGHC7AkPS99gJoSyuPAQvQ2Fe+jOaXlYM DKQnOrs++G7f7Lg8VRTJ5MFqIIYZoH8w6rHj8xwxFabWKe0moO67opAd+Z37MgVq 0Ak+iditQWVvpu0dd+spUu0TbpCDfdU5dtTuSXYbaEDrWGrui5d0shBA7DR70yek sziC2yR6+sDiLcraCLNGCGIJpZRYC7LfOFjZlwKfcJAyOIr0iBSe4ROO1Ibl28sr t/zRI/5/tsfmzu4x753vaP9qJpiar1NlF6NoWvzNGAJnBWNaZP8= =xQf/ -----END PGP SIGNATURE----- --R8bcOoHpld8vLVY30TDF0wrUdb6YxMbAJ-- From owner-freebsd-fs@freebsd.org Tue May 28 10:55:42 2019 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 093DB15BE162 for ; Tue, 28 May 2019 10:55:42 +0000 (UTC) (envelope-from kib@freebsd.org) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8476E73690 for ; Tue, 28 May 2019 10:55:41 +0000 (UTC) (envelope-from kib@freebsd.org) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x4SAtTio057661 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 28 May 2019 13:55:32 +0300 (EEST) (envelope-from kib@freebsd.org) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x4SAtTio057661 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x4SAtT2T057651; Tue, 28 May 2019 13:55:29 +0300 (EEST) (envelope-from kib@freebsd.org) X-Authentication-Warning: tom.home: kostik set sender to kib@freebsd.org using -f Date: Tue, 28 May 2019 13:55:29 +0300 From: Konstantin Belousov To: Alexander Lochmann Cc: freebsd-fs@freebsd.org, Horst Schirmeier Subject: Re: RFC: LockDoc - Detecting Locking Bugs in the FreeBSD Kernel Message-ID: <20190528105529.GH2748@kib.kiev.ua> References: <67482bf7-be1a-8f8d-ca80-2087bfc8cf99@tu-dortmund.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <67482bf7-be1a-8f8d-ca80-2087bfc8cf99@tu-dortmund.de> User-Agent: Mutt/1.11.4 (2019-03-13) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 10:55:42 -0000 On Tue, May 28, 2019 at 11:34:36AM +0200, Alexander Lochmann wrote: > Hi folks, > > during the past months we've been developing LockDoc, a trace-based > approach of Lock Analysis in the FreeBSD kernel. > LockDoc uses execution traces of an instrumented FreeBSd kernel to > automatically deduce > locking rules for all members of arbitrary kernel data structures. > The traces are gathered running a manually selected fs-specific subset > of the Linux Test Project in a virtual machine. > We use the Linux Test Project, because we weren't able to find such > benchmark suite for FreeBSD and we initially applied our approach to Linux. > These locking rules can be used to generate a comprehensive locking > documentation and to reveal potential bugs. > > LockDoc generates rules for each tuple of (data structure, member, {r,w}). > It completely ignores any atomic_*() function. > Accesses during initialization and destruction of objects are also ignored. > The output of LockDoc looks like this: > cdev_priv member: cdp_c.si_usecount [r] (5 lock combinations) > hypotheses: 24 > 34.8% (24 out of 69 mem accesses): EMBOTHER(vnode.v_lock[r]) -> > EMBOTHER(vnode.v_interlock[w]) -> devmtx:89(sleep mutex[w]) > 34.8% (24 out of 69 mem accesses): EMBOTHER(vnode.v_lock[r]) -> > devmtx:89(sleep mutex[w]) > 34.8% (24 out of 69 mem accesses): EMBOTHER(vnode.v_lock[r]) -> > EMBOTHER(vnode.v_interlock[w]) > 34.8% (24 out of 69 mem accesses): EMBOTHER(vnode.v_lock[r]) > 63.8% (44 out of 69 mem accesses): EMBOTHER(vnode.v_lock[w]) -> > EMBOTHER(vnode.v_interlock[w]) -> devmtx:89(sleep mutex[w]) > 63.8% (44 out of 69 mem accesses): EMBOTHER(vnode.v_lock[w]) -> > EMBOTHER(vnode.v_interlock[w]) > 65.2% (45 out of 69 mem accesses): EMBOTHER(vnode.v_lock[w]) -> > devmtx:89(sleep mutex[w]) > 65.2% (45 out of 69 mem accesses): EMBOTHER(vnode.v_lock[w]) > 98.6% (68 out of 69 mem accesses): EMBOTHER(vnode.v_interlock[w]) > -> devmtx:89(sleep mutex[w]) > 98.6% (68 out of 69 mem accesses): EMBOTHER(vnode.v_interlock[w]) > ! 100% (69 out of 69 mem accesses): devmtx:89(sleep mutex[w]) > 100% (69 out of 69 mem accesses): (no locks held) > > In this example LockDoc concludes that the lock > "devmtx:89(sleep mutex[w])" is necessary for reading > cdev_priv.cdp_c.si_usecount. > In this case, devmtx means a global lock of type sleep mutex. > To be more precise, the write lock (--> "[w]") of devmtx is needed. > Btw, EMBSAME stands for the lock embedded in the data type being accessed. > EMBOTHER respectively stands for a lock embedded in another object > that is currently not accessed. > > Based on this methodology, we can determine code locations that do not > adhere to the deduced locking rules. > The reports on rule-violating code include the stack trace and the > actual locks held. > > We've now created a series of bug reports for the following data types: > struct devfs_dirent, devfs_mount, mount, namecache, pipepair, and vnode > We present the counterexamples for each tuple of (data structure, > member, {r,w}). > Depending on the complexity of the callgraph, the counterexamples are > either embedded in the callgraph or the callgraph is shown below them. > In the latter case, zooming can be enabled via a button in the heading. > > We kindly ask you to have a look at our findings and send us some > comments back: > https://ess.cs.tu-dortmund.de/lockdoc-bugs/freebsd/ > > If you are interested in the derived locking rules, have a look at: > https://ess.cs.tu-dortmund.de/lockdoc-bugs/freebsd/all-txns-members-locks-hypo-nostack-nosubclasses.txt > > It might be possible that LockDoc considers a certain access as a bug > due to an incomplete blacklist of init and destroy functions. > Hence, we appreciate any feedback refining our blacklist. It is worse. I did quick look, and all the issues among 5 I looked at where reported because the tool does not understand the vnode visibility. It is safe to access a vnode without holding any locks as far as the vnode cannot be found by other threads. For instance, while mount (VFS_MOUNT) initializes the filesystem, VFS ensures that no thread could ever reach into it, e.g. by lookups. One way of ensuring it is by locking the covered vnode. So a report that devfs mount operates on some not-enough-locked vnode is false positive. Same for the freshly created vnode on the mounted filesystem, while the vnode not inserted into vfs hash or mount point vnode' list. In fact, we typically lock the new vnode exclusively right before adding to hash and calling insmntque(), exactly to prevent other threads to operate on partially initialized vnode. There could be valid reports, but digging in the present amount of reports with false positive is mostly equivalent to reviewing all mount/unmount and vnode creation/reclamation paths. It is too much to spend time usefully, IMO. From owner-freebsd-fs@freebsd.org Tue May 28 11:36:41 2019 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 2767115BF2A1 for ; Tue, 28 May 2019 11:36:41 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Received: from unimail.uni-dortmund.de (mx1.hrz.uni-dortmund.de [129.217.128.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "unimail.tu-dortmund.de", Issuer "TU Dortmund CA - G01" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 813D37567F; Tue, 28 May 2019 11:36:40 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Received: from [129.217.43.37] (kalamos.cs.uni-dortmund.de [129.217.43.37]) (authenticated bits=0) by unimail.uni-dortmund.de (8.16.0.41/8.16.0.41) with ESMTPSA id x4SBabSk028367 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 28 May 2019 13:36:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tu-dortmund.de; s=unimail; t=1559043398; bh=taWJ89+SNBwMwu1rNoShUnsHX8tM7gT0WP9yL4GZhcM=; h=To:Cc:References:From:Subject:Date:In-Reply-To; b=sx5J+fzjxdKcWNanFE9zJVMqawqcSH/v/pMzCzUXKnxvipZFU7NWAHUUZ1nDsyRPX 7jus0Uz7x6rxLgYuwdX0o61ZUuHEp8jsWilwFdlzEv6GMyuujmMJguUp5CUL7DsvPp az9ygYw5X9Fd7rMNjPQk8K6RT/SvNxUoISX+iopI= To: Konstantin Belousov Cc: freebsd-fs@freebsd.org, Horst Schirmeier References: <67482bf7-be1a-8f8d-ca80-2087bfc8cf99@tu-dortmund.de> <20190528105529.GH2748@kib.kiev.ua> From: Alexander Lochmann Openpgp: preference=signencrypt Autocrypt: addr=alexander.lochmann@tu-dortmund.de; prefer-encrypt=mutual; keydata= mQINBFQIyUEBEADZ+x+Ssg/46SiU66zm2lPGYAdqYfmXVv+sf/23+/KSj0FQHZKywzWjsmgR vWZZVlGJolwcW3MJ/g6ctZeOpfYiZVpzbZwNgKU0ETGjUmqmlq5/o5KnENKOimZzaKSaNn9p IC+EIeWXvu7pQjW0w1bK/RVVNw0p1Iz82W4Z+vKtD8CS+YJLAcZ6YoZMvQEg84O9odlV2Ryp oVj9EzHH40TWEdtgd4pQkaOks01PEr19sJXUjnP0VxLfs91AZjRnmGJKnI4HcrOKwquoQEeL DtHCxK0VNeoXCWkz33uBxSL5cicQ7D09hxjWthMilUpDZT94x0K452q4nybQ1TSLTYC8mlW+ xKUvJmqfHZbITJ10dTgjNvOe0kLbpXeQ1789lNmnA9bkQAK5Cefo55WbXmr1Mo3PV7y0XCib OaiijPlZo/Isc03EOK3lHPK8NuY8G+ftvphO4RyXCUWXw/o01cDnPaIEcTWkUbXvMhf/6ltP 1QWEfkguzGVjTw7Xssm9YuokC+P+49JKRyZzyCJZ022OxMlsX6c1BNZ4+cWUNmn6xr1xRNse SglpMLL1m3K1KuLf1hdAor6PBzFLiLa33lUhsWtg1ACFhpfZZOQRVas2McXTYUUpmCzOYI5F +km5q6cZStr9m7O3Y3DDGotiaJDpLtATwZ4MIM4ADbg/xl6ZgwARAQABtDZBbGV4YW5kZXIg TG9jaG1hbm4gPGFsZXhhbmRlci5sb2NobWFubkB0dS1kb3J0bXVuZC5kZT6JAj4EEwECACgF AlQIyUECGyMFCQlmAYAGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEFk+7QW8Pvb9I34Q AIEGy9Pt1nK8r+0baVF5KBXzoZuQIQ7ZfxJ0MFrCQSvRYEWevm2a0p5lBDOpb/VL8VtYMVO2 xZewerWoXyWMIeWmmCeSuVGdLDT/YV6BA54KzJkptmXxQaUVdiY+Fl0jxFODAXvSxI36MdzQ PFMwcSqxs5lZaxxyUWPidwanaQ5QNkShY2ljFD8gnKALiCxd/PqexLRlLinvqJ01EArxmPum PeA6nckWh4PGk1IGm7FiNZ5TYhCaq9lh5Hg5LsSJhJrOfgeT92hI7cLEwjKvRLrjH+NzbNFW tX4gWlwUHU5afP71AY9RfNXt/Ul8w+R5CX6W9xaiuS5MZZS5SZYeHU5QAfqaomSRkVb2uqwf Lahx76ONwOtsVbMLshaA9mxsgMUNDhOYxyKQOnYz2qThwZloEOgICaxIZG7WJug0HL4YGXG7 EJdFn2fEs6WUCeZ1DWGUGf92N+AFMBBJ/HP1fVlkAwuubOF7QdPTrsGwd8Tz0tkFzxd/W496 OvGO/OZZCw+pKnDODJyXtBs3jr6cu9evEasiaQEVL+nfhTGyNVW+dldn6uj7tJ3qLQbuk+o4 BLrUwjWXLdA4nMEGgtm8WabEyjoolP2BfjMTgEFQHhxaW0t4fIYLO5kM3lNphwXxmA4Lys+x RCPyLSitlqwrqDW19v56NTipcAqsczgpGZRGuQINBFQIyUEBEACcIW4RnxXteHv/Hl4/l926 sozOCL8iwT/OD9QvL3171Y1MDX8bt8LneMoh5RG4SegtdVaA4jLkdv8BTmRbY7qZrzJjYJX4 PUyvmuZbqpa+PF1c5uqUcuhwpXlQAupL1dCgO5p1xbdCxEOB9Lm+2hUFJy1LsvidwieJdFqR l09a/IypKtqywJxa6sSJp9ZPPCPMJnJxIVzGqAwHWO84LfIX5I6BRUbqAhxljJm40Bk79z+P HdytD0SaTuWIhsVYRFchKLxqbXokUhJaWupE1v4xFe2Sqty9vSCrJZMRZRTLvngRxbJVHIJJ sK685HNS3QJSrFtql+SGMkPHpX92+ZCmyTH6DAQ3Y0MtjJTcoYKu3fI8KT9BSsLuuXUToX7Y l4RbFB5s0rwZ2XMweKJdkwypC5fSZmLtEwgimMQ4VfBBUPJCvHhmvOHKX3Wls99D7xYWP7Lr iinmjbduiaO/A+bLjAdLqqGJpjQ7T3z+vqxzp3IaeJ3ObSnnnPppcKVAf6qZqu5Yfc31q/OY n19WyGIhwK3MuuVmjatxMmGgkSxzgTTP3jFQ008qymPcgrvgOR+MECCIpXjOMfenOhhsKnhu F7hxUS/6JtYKsEMEwJXVN509sNhJiEzSY9q+VYn9IArHSBMmpi5l6XvI1iwPD9HRNursPxKV lfi8lQsC7zxuTQARAQABiQIlBBgBAgAPBQJUCMlBAhsMBQkJZgGAAAoJEFk+7QW8Pvb9EkkP /2LyGWWOoTAGBhzvgKiYzarS3WQNZCuFHSfB/XXg4SRSX3NsxGVZWdLvVVgzWo1+tC1Qk6wO IVQSSw20wQXe8boZ8yiB8eM4ohfS0lySO9gOkQLYLijWg3JIYwTbqyK2X8LpbCs7eUTXM9NO 6pmVtoc3LBBIXQElX8ir0BZZ19OCSConTkyVHYK6IbEJ11PxjJG5ZS7anI4FQt0muzykZrhk bmf5IV3DtJ/KUfhQjnJa2B/KoT7F6vpTCoyPtaBUHQXEAb2NaZVwF06WXsqfX4yleym3Jlfx Rfa4+BOJ4Gf2EFd3wYCsIb33ulaXBLWa8w3A/FdQSW9NBM4iYlPxRg+5eXn+oajpyKqPLetH WRNMN4NSHVSpu+JRqRlTDO3HCn/peQ0OB/Iaf3HN3DLZdbjtZY40xl1iR9TMgD2fn2MlAFy3 dSKfjeCAQYP9can1MgebE729MI7QhtzuUYdHy+iJO/ENNlSgFo5DLwRqssEGqWag0xWPgcni UAERITTzHJeevSeZh5ThHyD173Pwn+tIhR4bK5RFy/gnzwqHckl8Hw7o06m51yI4dUVeatNT mAiNrmW3iQnvehjLZOYXOXx4ovsWdvQn01dUo3gCXdEWQ5yQLOQRGTCcrq1hzCEd//viy9oT spNrcZJf1pbo3EKkCwUPAltq51ramtYzOu4K Subject: Re: RFC: LockDoc - Detecting Locking Bugs in the FreeBSD Kernel Message-ID: Date: Tue, 28 May 2019 13:36:37 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190528105529.GH2748@kib.kiev.ua> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UvUJfYpdjsYTzuinmVwFQmDAxb6ujYqdw" X-Rspamd-Queue-Id: 813D37567F X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.92 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.92)[-0.918,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 11:36:41 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UvUJfYpdjsYTzuinmVwFQmDAxb6ujYqdw Content-Type: multipart/mixed; boundary="upj5BSVFJBoVVn8D7Azzj03BkKop7d49I"; protected-headers="v1" From: Alexander Lochmann To: Konstantin Belousov Cc: freebsd-fs@freebsd.org, Horst Schirmeier Message-ID: Subject: Re: RFC: LockDoc - Detecting Locking Bugs in the FreeBSD Kernel References: <67482bf7-be1a-8f8d-ca80-2087bfc8cf99@tu-dortmund.de> <20190528105529.GH2748@kib.kiev.ua> In-Reply-To: <20190528105529.GH2748@kib.kiev.ua> --upj5BSVFJBoVVn8D7Azzj03BkKop7d49I Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Thanks for your fast feedback! On 28.05.19 12:55, Konstantin Belousov wrote: >> >> It might be possible that LockDoc considers a certain access as a bug >> due to an incomplete blacklist of init and destroy functions. >> Hence, we appreciate any feedback refining our blacklist. > It is worse. I did quick look, and all the issues among 5 I looked at > where reported because the tool does not understand the vnode visibilit= y. > It is safe to access a vnode without holding any locks as far as the vn= ode > cannot be found by other threads. At which data type have you looked at? vnode? Can you please tell us which functions should be blacklisted? We have an idea in mind to overcome that issue. For now, we have to rely on the function blacklist. >=20 > For instance, while mount (VFS_MOUNT) initializes the filesystem, VFS > ensures that no thread could ever reach into it, e.g. by lookups. One > way of ensuring it is by locking the covered vnode. So a report that > devfs mount operates on some not-enough-locked vnode is false positive.= >=20 Can you please tell us to which report you are referring to? > Same for the freshly created vnode on the mounted filesystem, while the= > vnode not inserted into vfs hash or mount point vnode' list. In fact, > we typically lock the new vnode exclusively right before adding to > hash and calling insmntque(), exactly to prevent other threads to opera= te > on partially initialized vnode. Dito. - Alex >=20 > There could be valid reports, but digging in the present amount of repo= rts > with false positive is mostly equivalent to reviewing all mount/unmount= > and vnode creation/reclamation paths. It is too much to spend time use= fully, > IMO. >=20 --=20 Technische Universit=C3=A4t Dortmund Alexander Lochmann PGP key: 0xBC3EF6FD Otto-Hahn-Str. 16 phone: +49.231.7556141 D-44227 Dortmund fax: +49.231.7556116 http://ess.cs.tu-dortmund.de/Staff/al --upj5BSVFJBoVVn8D7Azzj03BkKop7d49I-- --UvUJfYpdjsYTzuinmVwFQmDAxb6ujYqdw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEElhZsUHzVP0dbkjCRWT7tBbw+9v0FAlztHUUACgkQWT7tBbw+ 9v0nwg//XsLET6bGE7kW90igUf3oU2e6CVKDeYMDyZePTFsVc0Zl/QHLTvrF/plC L3WKQ4gwiMul4rjzSfzVhZ6eTas1imacErUNp9l+BeWKHG5EU3jWPHBuWF9A0DNb h2NRA1Up3hXZ5TJiygtl1re5uR8/lQf6AJVRzMVAdp+nlGmAU+oH31MJ4hX36HvT gq49FeYyumrVDc079MpG3kcI6bbvee04UT0kcK6D1mv1FWuAfWKkNRo49fBJN+lw SjNe/VOarNuhMM7fjEkKuUm/FXfV+qVUMQzdPdICYF9MBRK70VMPTsVaEZSQrsm7 u1LIEWFAqMwI8g61XSfJwqEPqYQOa+IWuZ4tqoiAu+9ObaMvd01lSEHVHOCFn3Iq MUCbJYPUSxztgO0u2aGt1G/n3BFD9CgS0v+l2L1l4bYUCtYY49PVAzfgPrXTeDDP 3kJYJpsGSwNp2JulKPVo1UsCDSMCecbw2PIyWcASqhLkhvrssYpDapdC716Qu6r4 n+TpZBPWlj6qcarsIt2lE3gU+jxD2hDeXKfXjGs+rClyVsqyUHOud+U5ujqh4RYe PL5YGvTORKYE8JSqnVbO4vAE4/M4v7QvmiD+8ljp9vSy9iq2SvZ2awkXWiaIWZjq G+P8grLOx+gssdiEH5bY03YfbXeMs3tIEZrVjEzO/39rP4SSkGY= =6Zy1 -----END PGP SIGNATURE----- --UvUJfYpdjsYTzuinmVwFQmDAxb6ujYqdw-- From owner-freebsd-fs@freebsd.org Tue May 28 12:11:53 2019 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 08E5F15C059E for ; Tue, 28 May 2019 12:11:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 408F676A35 for ; Tue, 28 May 2019 12:11:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x4SCBgas075536 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 28 May 2019 15:11:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x4SCBgas075536 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x4SCBgVi075535; Tue, 28 May 2019 15:11:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 28 May 2019 15:11:42 +0300 From: Konstantin Belousov To: Alexander Lochmann Cc: freebsd-fs@freebsd.org, Horst Schirmeier Subject: Re: RFC: LockDoc - Detecting Locking Bugs in the FreeBSD Kernel Message-ID: <20190528121142.GI2748@kib.kiev.ua> References: <67482bf7-be1a-8f8d-ca80-2087bfc8cf99@tu-dortmund.de> <20190528105529.GH2748@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 12:11:53 -0000 On Tue, May 28, 2019 at 01:36:37PM +0200, Alexander Lochmann wrote: > Thanks for your fast feedback! > > On 28.05.19 12:55, Konstantin Belousov wrote: > >> > >> It might be possible that LockDoc considers a certain access as a bug > >> due to an incomplete blacklist of init and destroy functions. > >> Hence, we appreciate any feedback refining our blacklist. > > It is worse. I did quick look, and all the issues among 5 I looked at > > where reported because the tool does not understand the vnode visibility. > > It is safe to access a vnode without holding any locks as far as the vnode > > cannot be found by other threads. > At which data type have you looked at? vnode? > Can you please tell us which functions should be blacklisted? No, I cannot, this was the sole point of my response. > We have an idea in mind to overcome that issue. For now, we have to rely > on the function blacklist. > > > > For instance, while mount (VFS_MOUNT) initializes the filesystem, VFS > > ensures that no thread could ever reach into it, e.g. by lookups. One > > way of ensuring it is by locking the covered vnode. So a report that > > devfs mount operates on some not-enough-locked vnode is false positive. > > > Can you please tell us to which report you are referring to? > > Same for the freshly created vnode on the mounted filesystem, while the > > vnode not inserted into vfs hash or mount point vnode' list. In fact, > > we typically lock the new vnode exclusively right before adding to > > hash and calling insmntque(), exactly to prevent other threads to operate > > on partially initialized vnode. > Dito. > > - Alex > > > > > There could be valid reports, but digging in the present amount of reports > > with false positive is mostly equivalent to reviewing all mount/unmount > > and vnode creation/reclamation paths. It is too much to spend time usefully, > > IMO. > > > > -- > Technische Universität Dortmund > Alexander Lochmann PGP key: 0xBC3EF6FD > Otto-Hahn-Str. 16 phone: +49.231.7556141 > D-44227 Dortmund fax: +49.231.7556116 > http://ess.cs.tu-dortmund.de/Staff/al > From owner-freebsd-fs@freebsd.org Tue May 28 14:00:37 2019 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 0C9B2159877A for ; Tue, 28 May 2019 14:00:37 +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 98B1A821FF for ; Tue, 28 May 2019 14:00:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5981A1598779; Tue, 28 May 2019 14:00:36 +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 46A3F1598777 for ; Tue, 28 May 2019 14:00:36 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D5B18821FB for ; Tue, 28 May 2019 14:00:35 +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 186F9B417 for ; Tue, 28 May 2019 14:00:35 +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 x4SE0Yo6018626 for ; Tue, 28 May 2019 14:00:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4SE0YKt018625 for fs@FreeBSD.org; Tue, 28 May 2019 14:00:34 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 238112] Unable to create ZVOL Date: Tue, 28 May 2019 14:00:31 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mav@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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 14:00:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238112 --- Comment #8 from Alexander Motin --- Unfortunately SPECNAMELEN was bumped only in head (13). Too later to be mer= ged into 12 due to ABI (or mostly KBI) breakage. I agree that message may be n= ot perfect, but error=3D63 means ENAMETOOLONG, which is hardto to interpret wr= ong once it is decoded. I think we could add specific error message for that c= ase. In FreeNAS we just block those messages and limit ZVOL name lengths in external means. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue May 28 23:35:17 2019 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 9153B15AFCFF for ; Tue, 28 May 2019 23:35:17 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 72A296FE05 for ; Tue, 28 May 2019 23:35:16 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lj1-f173.google.com with SMTP id q16so553288ljj.8 for ; Tue, 28 May 2019 16:35:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dvr8DflzbaOk+WT4wVPbzLDBESuk6xDbQBrO9D7k7YQ=; b=eG65FYY/gH5spbN9y9TX78WY1ESTdYFYcsiVHFrfiZZSdERfpfiKu6KDhY+xAv9n4P lx/6GCMwkhypw+afe6+ss79d7f5so3HFXwaabDmdXjM5RBSTbvaIJqBkvWNWFV9mN2aH dwqsaWuivIsOLeqBt+gyewK+ZDFuu/uDH3MDp/rzhoH4phKmpW1egc6xt4Y5lNmuuXxQ LZ+bIGLm251P2+DSwb1gQCqlZWBpUtpJlTvVKAhj286i4+SewZlRYBciCZDlEJ2gNVzn CS7lw+t/OTAHcFla+2FjbJykRe5qiSVIpQtcGt569s9z8XccSJxHLhy2FIN3NbJG5p7v r/+g== X-Gm-Message-State: APjAAAUEcXEtPpMwZdB0QLRM5Qh/J4tiheKupuhzok668kfMVQGxrFoi Lfnp8CjNH4H4qeCyG4tk0yFs12Bdo+LExdpKLiJoPRl3uMc= X-Google-Smtp-Source: APXvYqyd2uMHu5Am1DGIcuP5pBznIBekrGNNQp8gkWnMYQbPKZo+JOhnmq9eDlesRMeGpFADmA/2zJWEjAUPh0BKyH8= X-Received: by 2002:a2e:5d9c:: with SMTP id v28mr22663369lje.32.1559086508377; Tue, 28 May 2019 16:35:08 -0700 (PDT) MIME-Version: 1.0 From: Alan Somers Date: Tue, 28 May 2019 17:34:57 -0600 Message-ID: Subject: FreeBSD fusefs(5) features survey To: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 72A296FE05 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.208.173 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-4.09 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.82)[-0.823,0]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[173.208.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-1.26)[ip: (-0.57), ipnet: 209.85.128.0/17(-3.38), asn: 15169(-2.29), country: US(-0.06)] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 23:35:17 -0000 I've been working on updating FreeBSD's fusefs driver. There are a lot of new features I could add, but there are too many to add them all. If you use, develop, or maintain a fuse file system, could you please give me some feedback on which features you'd like to see? Vote for as many features as you want in the poll below. And if there's something important that I left out, mention it in the comments. https://reviews.freebsd.org/V9 Thanks for your input! -Alan From owner-freebsd-fs@freebsd.org Wed May 29 11:55:28 2019 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 A489115C0762 for ; Wed, 29 May 2019 11:55:28 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) 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 088B08F9AA for ; Wed, 29 May 2019 11:55:28 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: by mailman.ysv.freebsd.org (Postfix) id B35A515C0761; Wed, 29 May 2019 11:55:27 +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 7D84515C0760 for ; Wed, 29 May 2019 11:55:27 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id 45E1D8F9A9 for ; Wed, 29 May 2019 11:55:25 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 53842 invoked from network); 29 May 2019 14:28:44 +0300 Received: from 109-252-107-70.nat.spd-mgts.ru (109-252-107-70.nat.spd-mgts.ru [109.252.107.70]) by mail.sub.ru ([88.212.205.2]) with ESMTP via TCP; 31 Dec 1969 23:59:59 -0000 To: fs@freebsd.org From: =?UTF-8?B?0JDQu9C10LrRgdCw0L3QtNGAINCf0L7QstC+0LvQvtGG0LrQuNC5?= Subject: Crashed ZFS Message-ID: Date: Wed, 29 May 2019 14:28:43 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 Content-Language: en-US X-Antivirus: Avast (VPS 190529-0, 29.05.2019), Outbound message X-Antivirus-Status: Clean X-Rspamd-Queue-Id: 45E1D8F9A9 X-Spamd-Bar: ++++++++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [10.19 / 15.00]; ARC_NA(0.00)[]; RSPAMD_URIBL(4.50)[sudo.su]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(1.00)[0.999,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[sub.ru]; AUTH_NA(1.00)[]; URI_COUNT_ODD(1.00)[7]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(0.70)[ip: (1.83), ipnet: 88.212.192.0/19(0.92), asn: 39134(0.73), country: RU(0.01)]; MX_GOOD(-0.01)[cached: gab2.sub.ru]; NEURAL_SPAM_LONG(1.00)[1.000,0]; NEURAL_SPAM_MEDIUM(1.00)[1.000,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:39134, ipnet:88.212.192.0/19, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; GREYLIST(0.00)[pass,body]; RECEIVED_SPAMHAUS_PBL(0.00)[70.107.252.109.zen.spamhaus.org : 127.0.0.11] X-Spam: Yes Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2019 11:55:29 -0000 Hello After power surge, one of my zpools yields errors |root@stor:/home/tarkhil # zpool status -v big_fast_one|| ||  pool: big_fast_one|| || state: FAULTED|| ||status: The pool metadata is corrupted and the pool cannot be opened.|| ||action: Recovery is possible, but will result in some data loss.|| ||        Returning the pool to its state as of Tue May 28 02:00:35 2019|| ||        should correct the problem.  Approximately 5 seconds of data|| ||        must be discarded, irreversibly.  Recovery can be attempted|| ||        by executing 'zpool clear -F big_fast_one'. A scrub of the pool|| ||        is strongly recommended after recovery.|| ||   see: http://illumos.org/msg/ZFS-8000-72|| ||  scan: none requested|| ||config:|| || ||        NAME              STATE     READ WRITE CKSUM|| ||        big_fast_one      FAULTED      0     0     1|| ||          raidz1-0        ONLINE       0     0     7|| ||            gpt/ZA21TJA7  ONLINE       0     0     0|| ||            gpt/ZA21P6JQ  ONLINE       0     0     0|| ||            gpt/ZA21PJZY  ONLINE       0     0     0|| ||            gpt/ZA21T6L6  ONLINE       0     0     0|| ||            gpt/ZA21TN3R  ONLINE       0     0     0|| | |root@stor:/home/tarkhil # zpool clear -Fn big_fast_one|| ||internal error: out of memory||| while there are plenty of RAM|(96 Gb)| |gpart shows everything OK| |root@stor:/home/tarkhil # zdb -AAA -L -e big_fast_one Configuration for import:         vdev_children: 1         version: 5000         pool_guid: 4972776226197917949         name: 'big_fast_one'         state: 0         hostid: 773241384         hostname: 'stor.inf.sudo.su'         vdev_tree:             type: 'root'             id: 0             guid: 4972776226197917949             children[0]:                 type: 'raidz'                 id: 0                 guid: 58821498572043303                 nparity: 1                 metaslab_array: 41                 metaslab_shift: 38                 ashift: 12                 asize: 50004131840000                 is_log: 0                 create_txg: 4                 children[0]:                     type: 'disk'                     id: 0                     guid: 13318923208485210326                     phys_path: 'id1,enc@n50030480005d387f/type@0/slot@e/elmdesc@013/p1'                     whole_disk: 1                     DTL: 57                     create_txg: 4                     path: '/dev/gpt/ZA21TJA7'                 children[1]:                     type: 'disk'                     id: 1                     guid: 5421240647062683539                     phys_path: 'id1,enc@n50030480005d387f/type@0/slot@1/elmdesc@000/p1'                     whole_disk: 1                     DTL: 56                     create_txg: 4                     path: '/dev/gpt/ZA21P6JQ'                 children[2]:                     type: 'disk'                     id: 2                     guid: 17788210514601115893                     phys_path: 'id1,enc@n50030480005d387f/type@0/slot@5/elmdesc@004/p1'                     whole_disk: 1                     DTL: 55                     create_txg: 4                     path: '/dev/gpt/ZA21PJZY'                 children[3]:                     type: 'disk'                     id: 3                     guid: 11411950711187621765                     phys_path: 'id1,enc@n50030480005d387f/type@0/slot@9/elmdesc@008/p1'                     whole_disk: 1                     DTL: 54                     create_txg: 4                     path: '/dev/gpt/ZA21T6L6'                 children[4]:                     type: 'disk'                     id: 4                     guid: 6486033012937503138                     phys_path: 'id1,enc@n50030480005d387f/type@0/slot@d/elmdesc@012/p1'                     whole_disk: 1                     DTL: 52                     create_txg: 4                     path: '/dev/gpt/ZA21TN3R' zdb: can't open 'big_fast_one': File exists ZFS_DBGMSG(zdb): | |root@stor:/home/tarkhil # zdb -AAA -L -u -e big_fast_one zdb: can't open 'big_fast_one': File exists root@stor:/home/tarkhil # zdb -AAA -L -d -e big_fast_one zdb: can't open 'big_fast_one': File exists root@stor:/home/tarkhil # zdb -AAA -L -h -e big_fast_one zdb: can't open 'big_fast_one': File exists | |What should I do? Export and import? Rename zpool.cache and import (it's a remote box, I cannot afford another 3 hours to and from it)? Something else?| |--| |Alex | --- Это сообщение проверено на вирусы антивирусом Avast. https://www.avast.com/antivirus From owner-freebsd-fs@freebsd.org Wed May 29 13:22:27 2019 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 D4C8815C2B9E for ; Wed, 29 May 2019 13:22:26 +0000 (UTC) (envelope-from mike@sentex.net) 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 F09D56C118 for ; Wed, 29 May 2019 13:22:25 +0000 (UTC) (envelope-from mike@sentex.net) Received: by mailman.ysv.freebsd.org (Postfix) id AA7E515C2B9D; Wed, 29 May 2019 13:22:25 +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 8577D15C2B9C for ; Wed, 29 May 2019 13:22:25 +0000 (UTC) (envelope-from mike@sentex.net) Received: from pyroxene.sentex.ca (unknown [IPv6:2607:f3e0:0:3::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "pyroxene.sentex.ca", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B0446C114 for ; Wed, 29 May 2019 13:22:25 +0000 (UTC) (envelope-from mike@sentex.net) Received: from [192.168.43.26] ([192.168.43.26]) by pyroxene.sentex.ca (8.15.2/8.15.2) with ESMTP id x4TDMLo3048821; Wed, 29 May 2019 09:22:22 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Crashed ZFS To: =?UTF-8?B?0JDQu9C10LrRgdCw0L3QtNGAINCf0L7QstC+0LvQvtGG0LrQuNC5?= , fs@freebsd.org References: From: Mike Tancsa Openpgp: preference=signencrypt Autocrypt: addr=mike@sentex.net; prefer-encrypt=mutual; keydata= mQENBEzcA24BCACpwI/iqOrs0GfQSfhA1v6Z8AcXVeGsRyKEKUpxoOYxXWc2z3vndbYlIP6E YJeifzKhS/9E+VjhhICaepLHfw865TDTUPr5D0Ed+edSsKjlnDtb6hfNJC00P7eoiuvi85TW F/gAxRY269A5d856bYrzLbkWp2lKUR3Bg6NnORtflGzx9ZWAltZbjYjjRqegPv0EQNYcHqWo eRpXilEo1ahT6nmOU8V7yEvT2j4wlLcQ6qg7w+N/vcBvyd/weiwHU+vTQ9mT61x5/wUrQhdw 2gJHeQXeDGMJV49RT2EEz+QVxaf477eyWsdQzPVjAKRMT3BVdK8WvpYAEfBAbXmkboOxABEB AAG0HG1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5jYT6JATgEEwECACIFAkzcA24CGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEJXHwM2kc8rX+sMH/2V6pTBKsQ5mpWWLgs6wVP2k BC+6r/YKNXv9Rw/PrC6+9hTbgA+sSjJ+8gxsCbJsOQXZrxF0x3l9oYdYfuKcwdwXFX1/FS8p HfBeDkmlH+dI709xT9wgrR4dS5aMmKp0scPrXPIAKiYVOHjOlNItcLYTEEWEFBepheEVsgmk GrNbcrHwOx/u4igUQ8vcpyXPyUki+BsftPw8ZQvBU887igh0OxaCR8AurJppQ5UQd63r81cX E1ZjoFoWCaGK/SjPb/OhpYpu5swoZIhOxQbn7OtakYPsDd5t2A5KhvjI8BMTnd5Go+2xsCmr jlIEq8Bi29gCcfQUvNiClevi13ifmnm5AQ0ETNwDbgEIALWGNJHRAhpd0A4vtd3G0oRqMBcM FGThQr3qORmEBTPPEomTdBaHcn+Xl+3YUvTBD/67/mutWBwgp2R5gQOSqcM7axvgMSHbKqBL 9sd1LsLw0UT2O5AYxv3EwzhG84pwRg3XcUqvWA4lA8tIj/1q4Jzi5qOkg1zxq4W9qr9oiYK5 bBR638JUvr3eHMaz/Nz+sDVFgwHmXZj3M6aE5Ce9reCGbvrae7H5D5PPvtT3r22X8SqfVAiO TFKedCf/6jbSOedPN931FJQYopj9P6b3m0nI3ZiCDVSqeyOAIBLzm+RBUIU3brzoxDhYR8pz CJc2sK8l6YjqivPakrD86bFDff8AEQEAAYkBHwQYAQIACQUCTNwDbgIbDAAKCRCVx8DNpHPK 1+iQB/99aqNtez9ZTBWELj269La8ntuRx6gCpzfPXfn6SDIfTItDxTh1hrdRVP5QNGGF5wus N4EMwXouskva1hbFX3Pv72csYSxxEJXjW16oV8WK4KjKXoskLg2RyRP4uXqL7Mp2ezNtVY5F 9nu3fj4ydpHCSaqKy5xd70A8D50PfZsFgkrsa5gdQhPiGGEdxhq/XSeAAnZ4uVLJKarH+mj5 MEhgZPEBWkGrbDZpezl9qbFcUem/uT9x8FYT/JIztMVh9qDcdP5tzANW5J7nvgXjska+VFGY ryZK4SPDczh74mn6GI/+RBi7OUzXXPgpPBrhS5FByjwCqjjsSpTjTds+NGIY Organization: Sentex Communications Message-ID: <460609b1-35a6-6bfc-318c-bd796a3e3239@sentex.net> Date: Wed, 29 May 2019 09:22:18 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 1B0446C114 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.988,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2019 13:22:27 -0000 I would wait for a few more people to chime with what to do, but I had a similar issue (same error IIRC) last week after physically moving the disks to a new controller.  I did zpool clear -F zpool export zpool import The clear gave an error but after the export / import, it came back online.  A scrub was done, but showed no errors. Good luck!     ---Mike On 5/29/2019 7:28 AM, Александр Поволоцкий wrote: > Hello > > After power surge, one of my zpools yields errors > > |root@stor:/home/tarkhil # zpool status -v big_fast_one|| > ||  pool: big_fast_one|| > || state: FAULTED|| > ||status: The pool metadata is corrupted and the pool cannot be opened.|| > ||action: Recovery is possible, but will result in some data loss.|| > ||        Returning the pool to its state as of Tue May 28 02:00:35 > 2019|| > ||        should correct the problem.  Approximately 5 seconds of data|| > ||        must be discarded, irreversibly.  Recovery can be attempted|| > ||        by executing 'zpool clear -F big_fast_one'. A scrub of the > pool|| > ||        is strongly recommended after recovery.|| > ||   see: http://illumos.org/msg/ZFS-8000-72|| > ||  scan: none requested|| > ||config:|| > || > ||        NAME              STATE     READ WRITE CKSUM|| > ||        big_fast_one      FAULTED      0     0     1|| > ||          raidz1-0        ONLINE       0     0     7|| > ||            gpt/ZA21TJA7  ONLINE       0     0     0|| > ||            gpt/ZA21P6JQ  ONLINE       0     0     0|| > ||            gpt/ZA21PJZY  ONLINE       0     0     0|| > ||            gpt/ZA21T6L6  ONLINE       0     0     0|| > ||            gpt/ZA21TN3R  ONLINE       0     0     0|| > | > > |root@stor:/home/tarkhil # zpool clear -Fn big_fast_one|| > ||internal error: out of memory||| > > while there are plenty of RAM|(96 Gb)| > > |gpart shows everything OK| > > |root@stor:/home/tarkhil # zdb -AAA -L -e big_fast_one > > Configuration for import: >         vdev_children: 1 >         version: 5000 >         pool_guid: 4972776226197917949 >         name: 'big_fast_one' >         state: 0 >         hostid: 773241384 >         hostname: 'stor.inf.sudo.su' >         vdev_tree: >             type: 'root' >             id: 0 >             guid: 4972776226197917949 >             children[0]: >                 type: 'raidz' >                 id: 0 >                 guid: 58821498572043303 >                 nparity: 1 >                 metaslab_array: 41 >                 metaslab_shift: 38 >                 ashift: 12 >                 asize: 50004131840000 >                 is_log: 0 >                 create_txg: 4 >                 children[0]: >                     type: 'disk' >                     id: 0 >                     guid: 13318923208485210326 >                     phys_path: > 'id1,enc@n50030480005d387f/type@0/slot@e/elmdesc@013/p1' >                     whole_disk: 1 >                     DTL: 57 >                     create_txg: 4 >                     path: '/dev/gpt/ZA21TJA7' >                 children[1]: >                     type: 'disk' >                     id: 1 >                     guid: 5421240647062683539 >                     phys_path: > 'id1,enc@n50030480005d387f/type@0/slot@1/elmdesc@000/p1' >                     whole_disk: 1 >                     DTL: 56 >                     create_txg: 4 >                     path: '/dev/gpt/ZA21P6JQ' >                 children[2]: >                     type: 'disk' >                     id: 2 >                     guid: 17788210514601115893 >                     phys_path: > 'id1,enc@n50030480005d387f/type@0/slot@5/elmdesc@004/p1' >                     whole_disk: 1 >                     DTL: 55 >                     create_txg: 4 >                     path: '/dev/gpt/ZA21PJZY' >                 children[3]: >                     type: 'disk' >                     id: 3 >                     guid: 11411950711187621765 >                     phys_path: > 'id1,enc@n50030480005d387f/type@0/slot@9/elmdesc@008/p1' >                     whole_disk: 1 >                     DTL: 54 >                     create_txg: 4 >                     path: '/dev/gpt/ZA21T6L6' >                 children[4]: >                     type: 'disk' >                     id: 4 >                     guid: 6486033012937503138 >                     phys_path: > 'id1,enc@n50030480005d387f/type@0/slot@d/elmdesc@012/p1' >                     whole_disk: 1 >                     DTL: 52 >                     create_txg: 4 >                     path: '/dev/gpt/ZA21TN3R' > zdb: can't open 'big_fast_one': File exists > > ZFS_DBGMSG(zdb): > | > > |root@stor:/home/tarkhil # zdb -AAA -L -u -e big_fast_one > zdb: can't open 'big_fast_one': File exists > root@stor:/home/tarkhil # zdb -AAA -L -d -e big_fast_one > zdb: can't open 'big_fast_one': File exists > root@stor:/home/tarkhil # zdb -AAA -L -h -e big_fast_one > zdb: can't open 'big_fast_one': File exists > | > > |What should I do? Export and import? Rename zpool.cache and import > (it's a remote box, I cannot afford another 3 hours to and from it)? > Something else?| > > |--| > > |Alex > | > > > > > --- > Это сообщение проверено на вирусы антивирусом Avast. > https://www.avast.com/antivirus > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-fs@freebsd.org Wed May 29 14:56:42 2019 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 DB20615A4122 for ; Wed, 29 May 2019 14:56:41 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) 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 2A77E70332 for ; Wed, 29 May 2019 14:56:41 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: by mailman.ysv.freebsd.org (Postfix) id D7F8815A4121; Wed, 29 May 2019 14:56:40 +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 B31E115A411E for ; Wed, 29 May 2019 14:56:40 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id F05FD70331 for ; Wed, 29 May 2019 14:56:39 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 88520 invoked from network); 29 May 2019 17:56:38 +0300 Received: from 109-252-107-70.nat.spd-mgts.ru (109-252-107-70.nat.spd-mgts.ru [109.252.107.70]) by mail.sub.ru ([88.212.205.2]) with ESMTP via TCP; 31 Dec 1969 23:59:59 -0000 Subject: Re: Crashed ZFS To: Mike Tancsa , fs@freebsd.org References: <460609b1-35a6-6bfc-318c-bd796a3e3239@sentex.net> From: =?UTF-8?B?0JDQu9C10LrRgdCw0L3QtNGAINCf0L7QstC+0LvQvtGG0LrQuNC5?= Message-ID: Date: Wed, 29 May 2019 17:56:37 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <460609b1-35a6-6bfc-318c-bd796a3e3239@sentex.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Antivirus: Avast (VPS 190529-0, 29.05.2019), Outbound message X-Antivirus-Status: Clean X-Rspamd-Queue-Id: F05FD70331 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2019 14:56:42 -0000 It worked! On 29.05.2019 16:22, Mike Tancsa wrote: > I would wait for a few more people to chime with what to do, but I had a > similar issue (same error IIRC) last week after physically moving the > disks to a new controller.  I did > zpool clear -F > zpool export > zpool import > > The clear gave an error but after the export / import, it came back > online.  A scrub was done, but showed no errors. Good luck! > >     ---Mike > > > > On 5/29/2019 7:28 AM, Александр Поволоцкий wrote: >> Hello >> >> After power surge, one of my zpools yields errors >> >> |root@stor:/home/tarkhil # zpool status -v big_fast_one|| >> ||  pool: big_fast_one|| >> || state: FAULTED|| >> ||status: The pool metadata is corrupted and the pool cannot be opened.|| >> ||action: Recovery is possible, but will result in some data loss.|| >> ||        Returning the pool to its state as of Tue May 28 02:00:35 >> 2019|| >> ||        should correct the problem.  Approximately 5 seconds of data|| >> ||        must be discarded, irreversibly.  Recovery can be attempted|| >> ||        by executing 'zpool clear -F big_fast_one'. A scrub of the >> pool|| >> ||        is strongly recommended after recovery.|| >> ||   see: http://illumos.org/msg/ZFS-8000-72|| >> ||  scan: none requested|| >> ||config:|| >> || >> ||        NAME              STATE     READ WRITE CKSUM|| >> ||        big_fast_one      FAULTED      0     0     1|| >> ||          raidz1-0        ONLINE       0     0     7|| >> ||            gpt/ZA21TJA7  ONLINE       0     0     0|| >> ||            gpt/ZA21P6JQ  ONLINE       0     0     0|| >> ||            gpt/ZA21PJZY  ONLINE       0     0     0|| >> ||            gpt/ZA21T6L6  ONLINE       0     0     0|| >> ||            gpt/ZA21TN3R  ONLINE       0     0     0|| >> | >> >> |root@stor:/home/tarkhil # zpool clear -Fn big_fast_one|| >> ||internal error: out of memory||| >> >> while there are plenty of RAM|(96 Gb)| >> >> |gpart shows everything OK| >> >> |root@stor:/home/tarkhil # zdb -AAA -L -e big_fast_one >> >> Configuration for import: >>         vdev_children: 1 >>         version: 5000 >>         pool_guid: 4972776226197917949 >>         name: 'big_fast_one' >>         state: 0 >>         hostid: 773241384 >>         hostname: 'stor.inf.sudo.su' >>         vdev_tree: >>             type: 'root' >>             id: 0 >>             guid: 4972776226197917949 >>             children[0]: >>                 type: 'raidz' >>                 id: 0 >>                 guid: 58821498572043303 >>                 nparity: 1 >>                 metaslab_array: 41 >>                 metaslab_shift: 38 >>                 ashift: 12 >>                 asize: 50004131840000 >>                 is_log: 0 >>                 create_txg: 4 >>                 children[0]: >>                     type: 'disk' >>                     id: 0 >>                     guid: 13318923208485210326 >>                     phys_path: >> 'id1,enc@n50030480005d387f/type@0/slot@e/elmdesc@013/p1' >>                     whole_disk: 1 >>                     DTL: 57 >>                     create_txg: 4 >>                     path: '/dev/gpt/ZA21TJA7' >>                 children[1]: >>                     type: 'disk' >>                     id: 1 >>                     guid: 5421240647062683539 >>                     phys_path: >> 'id1,enc@n50030480005d387f/type@0/slot@1/elmdesc@000/p1' >>                     whole_disk: 1 >>                     DTL: 56 >>                     create_txg: 4 >>                     path: '/dev/gpt/ZA21P6JQ' >>                 children[2]: >>                     type: 'disk' >>                     id: 2 >>                     guid: 17788210514601115893 >>                     phys_path: >> 'id1,enc@n50030480005d387f/type@0/slot@5/elmdesc@004/p1' >>                     whole_disk: 1 >>                     DTL: 55 >>                     create_txg: 4 >>                     path: '/dev/gpt/ZA21PJZY' >>                 children[3]: >>                     type: 'disk' >>                     id: 3 >>                     guid: 11411950711187621765 >>                     phys_path: >> 'id1,enc@n50030480005d387f/type@0/slot@9/elmdesc@008/p1' >>                     whole_disk: 1 >>                     DTL: 54 >>                     create_txg: 4 >>                     path: '/dev/gpt/ZA21T6L6' >>                 children[4]: >>                     type: 'disk' >>                     id: 4 >>                     guid: 6486033012937503138 >>                     phys_path: >> 'id1,enc@n50030480005d387f/type@0/slot@d/elmdesc@012/p1' >>                     whole_disk: 1 >>                     DTL: 52 >>                     create_txg: 4 >>                     path: '/dev/gpt/ZA21TN3R' >> zdb: can't open 'big_fast_one': File exists >> >> ZFS_DBGMSG(zdb): >> | >> >> |root@stor:/home/tarkhil # zdb -AAA -L -u -e big_fast_one >> zdb: can't open 'big_fast_one': File exists >> root@stor:/home/tarkhil # zdb -AAA -L -d -e big_fast_one >> zdb: can't open 'big_fast_one': File exists >> root@stor:/home/tarkhil # zdb -AAA -L -h -e big_fast_one >> zdb: can't open 'big_fast_one': File exists >> | >> >> |What should I do? Export and import? Rename zpool.cache and import >> (it's a remote box, I cannot afford another 3 hours to and from it)? >> Something else?| >> >> |--| >> >> |Alex >> | >> >> >> >> >> --- >> Это сообщение проверено на вирусы антивирусом Avast. >> https://www.avast.com/antivirus >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> >> From owner-freebsd-fs@freebsd.org Wed May 29 16:15:17 2019 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 6E68015A69D2 for ; Wed, 29 May 2019 16:15:17 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: from mail-ua1-x942.google.com (mail-ua1-x942.google.com [IPv6:2607:f8b0:4864:20::942]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BADF073ADA for ; Wed, 29 May 2019 16:15:15 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: by mail-ua1-x942.google.com with SMTP id n2so1195047uad.8 for ; Wed, 29 May 2019 09:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphix.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=+Sli7tmUKZg4GrJjMgfcjwvKUsrVpU8AZtqnqo7EN4U=; b=JLahOFFm6ampEp4XQGLrXQ4hwImoZiBMBU8z08W4tehGNR4owkKv180sPoaJmIuuYY zszQynQ2xLSgSHzoVlbjYjnDndb8RgcufoTR/P4IkkoC9GpLZsTHH+y77q+vEUdVulg9 cgvSn6orsENCKoLcjFEI/npMzv+2iO6ZPwW2U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+Sli7tmUKZg4GrJjMgfcjwvKUsrVpU8AZtqnqo7EN4U=; b=eFKhUr/+jpwbmtM79nt+gGp1tM25q6k0qOp90DT5JVUUE2nZ1jpoex5AYdOBjmw9qj lJ0BGIsuyYUSTOO8CKA0yGR9Ey6lNVu0H0qlqBUyC5j8agRHVcA9knY/D569omtNqN2b RHT9E7Bd+9lOqSbI5dHiS+heqZhkWKPnCK9csyvdUOoev/0A2ppngZSrZh3Am7ci4rBm SjvMyKV4b8A7l+Kv98/kFTahPYCUqL5W/8+MPCEsVHg0lllbxvUW80eHWbABR3P7PiDx WhsQSeiZJWn94Iysrk/LQgLtgDwMNOnx6xi700CQAyXHUCoplN2zeotvSpa6B1GH30va r16Q== X-Gm-Message-State: APjAAAV3u2aM8TjGG9Tuwhhsl0WcocOV0Bf2PPNiiLCvSbfb1LV/2cWx wBzYaYsXeVO2hP9WVDwvZqgsdL4Khe5ru8P5Z3fxcQ== X-Google-Smtp-Source: APXvYqzI2Tg9Vc4kPvg0HuA+9cRIsVbdutM3bGOEMHEjvLrRZZFa4OjdfaHYuSrGE+UHZJBO74d8IixD+AP0AdMlzp8= X-Received: by 2002:ab0:7346:: with SMTP id k6mr44237053uap.89.1559146513867; Wed, 29 May 2019 09:15:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Ahrens Date: Wed, 29 May 2019 09:15:02 -0700 Message-ID: Subject: Re: May OpenZFS Leadership Meeting To: developer , illumos-zfs , zfs-devel@list.zfsonlinux.org, zfs-devel@freebsd.org, freebsd-fs , zfs-discuss X-Rspamd-Queue-Id: BADF073ADA X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=delphix.com header.s=google header.b=JLahOFFm; dmarc=pass (policy=none) header.from=delphix.com; spf=pass (mx1.freebsd.org: domain of matthew.ahrens@delphix.com designates 2607:f8b0:4864:20::942 as permitted sender) smtp.mailfrom=matthew.ahrens@delphix.com X-Spamd-Result: default: False [-3.13 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; R_DKIM_ALLOW(-0.20)[delphix.com:s=google]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; URI_COUNT_ODD(1.00)[17]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[delphix.com:+]; DMARC_POLICY_ALLOW(-0.50)[delphix.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2.4.9.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,aspmx.l.google.com,aspmx2.googlemail.com,alt2.aspmx.l.google.com,aspmx3.googlemail.com]; NEURAL_HAM_SHORT(-0.85)[-0.849,0]; IP_SCORE(-0.57)[ip: (2.78), ipnet: 2607:f8b0::/32(-3.30), asn: 15169(-2.29), country: US(-0.06)]; FORGED_SENDER(0.30)[mahrens@delphix.com,matthew.ahrens@delphix.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[mahrens@delphix.com,matthew.ahrens@delphix.com]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2019 16:15:17 -0000 Thanks everyone who participated in yesterday's meeting. The video recording is now up: https://youtu.be/EzyPr3BuePo The next meeting will be June 25, at 1pm pacific time. The meeting notes follow: - Happy ZoL 0.8! - Lots of downloads and excited people. Successful so far! - Illumos encryption status (Jerry/Jason/J=C3=B6rgen) - Jerry has all of J=C3=B6rgen=E2=80=99s work pulled over and building = on illumos. Resolving some test failures and then will put it out for an illumos = code review. - The code review will go out to the illumos developer mailing list and ask that they identify issues with the platform-dependent changes in = the port. People will have ample time to comment and raise issues before = the RTI is submitted. - RAIDZ Expansion status (Matt) - Will have an Alpha out this week or next. Pools will need to be destroyed if you use it. - The change lets you add a device to an existing pool and reflows the data between disks. - All of the caveats and details of what does and doesn=E2=80=99t work = will be included in the PR. - Call for testing! Once the code is up, any manual testing under different workloads and setups will be greatly appreciated. It would = also be great if people could help write systemic tests. - BSDCAN update - The future of ZFS on FreeBSD (Allan) - One of the goals of the talk was to motivate the ZFS repo of FreeBSD rebasing over ZoL. The advantages of having the consumers of ZFS closer together was highlighted. - There was some initial pushback people thought that the rebase will make ZFS use the Linux Compatibility layer of FreeBSD, which is not the case. Once this was clear, there were no further pushbacks - Matt brought up that once the rebase is done and stable, discussions may be initiated for potentially renaming the ZoL repo= . - snapshot scalability (Matt) - Slides are posted and video will be up eventually. Please check them out if you=E2=80=99re interested in learning more about snaps= hots. - Matt will post a link to #openzfs once he has one. - DRAID meeting recap (Richard Elling) - There were about 11 participants - There is a design doc (linked above) with all the history of its edits based on the discussions that took place. Please add comments to the doc to further the discussion. - There is still work to be done but since the code changes are sizeable, we=E2=80=99ll try to split them into individual commits whe= n it makes sense. - Sef says he is available to do reviews at any time, just reach out= . - CoC update (Matt/Karyn) - Code of Conduct was put into place since the last meeting. We made several changes based on community feedback. Thanks for participating= ! - We will have a call for nominees for the Working Group in the fall, and then will review the CoC at that point and have another community comment period. The goal is to complete this before the Dev Summit. - The Dev Summit is Nov 4-5 in SF. See open-zfs.org for upcoming dates (e.g., call for presentations). - Registration opens July 8th - Send presentations to Matt by August 19th - Thanks to Datto, Delphix, and Intel for already sponsoring! Reach out to @kritter if you want to sponsor and she can give you the details. - Request from sef! The On-Disk Format document is out of date, and doesn=E2=80=99t reflect recent changes (e.g., encryption). It would = be really helpful to update this and keep it up-to-date going forward (Perhaps in = a semi-automated way?) - Tom: The info about how things look today exists in various places, so it is just a question of pulling it together into a single place. - Matt: We only have a pdf for that, and we probably can=E2=80=99t just copy-paste it somewhere else. It would be good to have a document with this info. Let=E2=80=99s put out a call for a volunteer to do this. - Paul pointed out that it is licensed under a Berkeley License - Compressed arc performance issue - single threaded sequential read - Sequential reads are decompressed by the (one) user=E2=80=99s thread. - With non-compressed ARC, they are decompressed by the (several) zio threads, leading to more parallelism and improved performance. - This is a good reason to disable compressed ARC (for workloads with single threaded sequential read). - We could make the prefetches decompress into the dbuf cache, to get this performance back. - If we do that, could we then make compressed ARC mandatory? - Maybe=E2=80=A6 but Allan may have found another way to address the= problem that motivated him to make compressed ARC mandatory - Please take a look at the redacted send-receive requests as soon as you get a chance so we can push this now that 0.8 is out. It=E2=80=99s in sy= nc with 0.8. - Next meeting will be in 4 weeks: June 25 On Mon, May 27, 2019 at 8:51 PM Matthew Ahrens wrote: > The next OpenZFS Leadership meeting will be held tomorrow, May 28, > 1pm-2pm Pacific time. We don't have much on the agenda for this month, s= o > if there are things you'd like to discuss, this is a good opportunity - > send me an email or edit the doc :) > > Everyone is welcome to attend and participate, and we will try to keep th= e > meeting on agenda and on time. The meetings will be held online via Zoom= , > and recorded and posted to the website and YouTube after the meeting. > > The agenda for the meeting will be a discussion of the projects listed in > the agenda doc. > > For more information and details on how to attend, as well as notes and > video from the previous meeting, please see the agenda document: > > > https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAnW= HhV-BM/edit > > --matt > From owner-freebsd-fs@freebsd.org Fri May 31 08:59:59 2019 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 C519015B6B76 for ; Fri, 31 May 2019 08:59:59 +0000 (UTC) (envelope-from rm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6247D89C00 for ; Fri, 31 May 2019 08:59:59 +0000 (UTC) (envelope-from rm@FreeBSD.org) Received: from [127.0.0.1] (unknown [127.0.1.132]) by freefall.freebsd.org (Postfix) with ESMTP id E9C5664CE for ; Fri, 31 May 2019 08:59:58 +0000 (UTC) (envelope-from rm@FreeBSD.org) To: freebsd-fs@freebsd.org From: Ruslan Makhmatkhanov Subject: [ZFS] Empty shapshot diffs Message-ID: <5199c23e-a1bb-6019-4ff6-505db370604e@FreeBSD.org> Date: Fri, 31 May 2019 11:59:58 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 6247D89C00 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.97 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.976,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2019 08:59:59 -0000 Hello, there is standard dataset with a bunch of snapshots: root@sys:~ # zfs list -rt snapshot storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c NAME USED AVAIL REFER MOUNTPOINT storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190423000010 37,6M - 43,7G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190424000707 40,6M - 43,7G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190425001008 39,9M - 43,7G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190426001139 212M - 43,7G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190427001036 69,8M - 43,7G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190428000245 40,4M - 43,7G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190429000715 64,0M - 43,6G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190430001449 38,2M - 43,7G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190501000943 32,2M - 43,7G - storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190502001414 34,7M - 43,7G - But diffing of these snapshots shows nothing: root@sys:~ # zfs diff storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190423000010 storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190428000245 root@sys:~ # More old snapshots of this dataset can be diffed successfully: root@sys:~ # zfs diff storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20181130000342 storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c@20190507000343 M /storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c/ - /storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c/disk + /storage03/disks/f0878a5b0a3546e99fa33ba3f0b5476c/disk Any suggestions what can it be and how to debug/fix that? FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 01:43:23 UTC 2016 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 -- Regards, Ruslan T.O.S. Of Reality From owner-freebsd-fs@freebsd.org Fri May 31 15:12:15 2019 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 F194015BF78B; Fri, 31 May 2019 15:12:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 691DD7074E; Fri, 31 May 2019 15:12:13 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1hWjCM-000I1A-A0; Fri, 31 May 2019 18:12:02 +0300 Date: Fri, 31 May 2019 18:12:02 +0300 From: Slawa Olhovchenkov To: Ian Lepore Cc: lev@FreeBSD.org, freebsd-fs@freebsd.org, freebsd-hackers@FreeBSD.org, Alexander Motin Subject: Re: Commit r345200 (new ARC reclamation threads) looks suspicious to me. Message-ID: <20190531151202.GG47119@zxy.spb.ru> References: <55989579-a228-498e-2842-453cad6f315f@FreeBSD.org> <174f71126ca39907370a8904c07546b712ad91b9.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <174f71126ca39907370a8904c07546b712ad91b9.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 691DD7074E X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.61 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.83)[0.827,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zxy.spb.ru]; AUTH_NA(1.00)[]; RCPT_COUNT_FIVE(0.00)[5]; NEURAL_SPAM_MEDIUM(0.93)[0.928,0]; IP_SCORE(0.00)[country: RU(0.01)]; MX_GOOD(-0.01)[zxy.spb.ru]; NEURAL_SPAM_LONG(0.96)[0.961,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:5495, ipnet:195.70.192.0/19, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2019 15:12:15 -0000 On Mon, May 20, 2019 at 10:10:16AM -0600, Ian Lepore wrote: > On Mon, 2019-05-20 at 18:38 +0300, Lev Serebryakov wrote: > > I'm looking at last commit to > > 'sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c' (r345200) and > > have one question. > > > > Is it Ok for two threads to communicate via simple global variable? > > Now > > new code has (line 315): > > > > static boolean_t arc_adjust_needed = B_FALSE; > > > > And after that some threads run code like this: > > > > mutex_enter(&arc_adjust_lock); > > arc_adjust_needed = B_TRUE; > > mutex_exit(&arc_adjust_lock); > > zthr_wakeup(arc_adjust_zthr); > > > > And thread `arc_adjust_zthr` has code like this (line 4874): > > > > return (arc_adjust_needed); > > > > This variable is not atomic. It is not updated and/or read in atomic > > way. What code gives guarantees that `arc_adjust_zthr` will detect > > this > > change? I don't see any. Am I wrong? > > The arc_adjust_needed variable is the gating condition associated with > a condition variable and lock. It is only read or changed while > holding a lock, and the acquiring and releasing of that lock provides > the needed memory barriers. In this case, the association with the > condition variable and lock is somewhat obscured by the way the zthread > timer stuff works. The arc_adjust_cb_check() function is called from > line 193 of contrib/opensolaris/uts/common/fs/zfs/zthr.c, and that's > where you'll find the code that makes it clear this is an idiomatic > condition variable pattern. What about arc_no_grow, for example? arc_no_grow set in arc_reap_cb_check(), called from arc_reap_zthr thread and in arc_lowmem(). arc_no_grow test in arc_adapt(), called from arc_read()/arc_get_data_impl() called from many unsynced thread. How synced visibility of this varibale? From owner-freebsd-fs@freebsd.org Fri May 31 21:27:59 2019 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 E2FB015C6184 for ; Fri, 31 May 2019 21:27:58 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670087.outbound.protection.outlook.com [40.107.67.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B751C852B3 for ; Fri, 31 May 2019 21:27:56 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM (52.132.86.223) by QB1PR01MB3780.CANPRD01.PROD.OUTLOOK.COM (52.132.87.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.18; Fri, 31 May 2019 21:27:54 +0000 Received: from QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM ([fe80::a890:15d:5609:414d]) by QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM ([fe80::a890:15d:5609:414d%3]) with mapi id 15.20.1922.021; Fri, 31 May 2019 21:27:54 +0000 From: Rick Macklem To: "freebsd-fs@freebsd.org" Subject: mountd patch for review Thread-Topic: mountd patch for review Thread-Index: AQHVF/cRb+kzXai9F0ifeYWlTlKvkw== Date: Fri, 31 May 2019 21:27:54 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: f449def1-14d8-4103-1498-08d6e60ed81c x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:QB1PR01MB3780; x-ms-traffictypediagnostic: QB1PR01MB3780: x-ms-exchange-purlcount: 1 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:4502; x-forefront-prvs: 00540983E2 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(136003)(39860400002)(376002)(366004)(396003)(199004)(189003)(966005)(7696005)(99286004)(476003)(68736007)(3480700005)(14454004)(2351001)(305945005)(6506007)(33656002)(786003)(46003)(102836004)(71190400001)(71200400001)(316002)(8936002)(52536014)(6306002)(25786009)(2501003)(5660300002)(81156014)(74316002)(55016002)(8676002)(74482002)(76116006)(53936002)(81166006)(66946007)(2906002)(86362001)(256004)(4744005)(9686003)(73956011)(66556008)(64756008)(6436002)(186003)(486006)(14444005)(6916009)(66446008)(478600001)(66476007); DIR:OUT; SFP:1101; SCL:1; SRVR:QB1PR01MB3780; H:QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: RshUhvXnrHeVnjoMZE5aMpjaQMrW9z8thJl+fXFUpkqU4u3u/3e6PH9SaUB1OWRb82M8/COMgXShOaDVOfGTRktvqBCoqopgTtkelmbx/0n/Z023R7M+TyeK+dFUUJJM+KzkWWt5aV/M0csaQHj1TmlHM2VsSEGG7SbI1Q2Lun8WVx+04d7aguTXwaOXo3lN//oBwTc0+TLSv9C18c2TQdVHgnvBD6NB95spTsMlbEQzfIDgrh7XTSCXF9/kfooeiQznXkDV5v36t2+/+MDPU3iMWgc/ztMQFxo7LQ8rqcbrTwHQAf5zc/a7/Z5YgA7SfgCG4dZojoozTBcgv+t5Vu6kKzUdhLUw/nYKdCn3CYqWB1JO0FooWIstHbL4fOH4BEXrbo1+UReZwS5iNS9UoiWkCFQcHTUxq6SkU85LqiQ= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: f449def1-14d8-4103-1498-08d6e60ed81c X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2019 21:27:54.8553 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: rmacklem@uoguelph.ca X-MS-Exchange-Transport-CrossTenantHeadersStamped: QB1PR01MB3780 X-Rspamd-Queue-Id: B751C852B3 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rmacklem@uoguelph.ca designates 40.107.67.87 as permitted sender) smtp.mailfrom=rmacklem@uoguelph.ca X-Spamd-Result: default: False [-4.06 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[uoguelph.ca]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-1.02)[ipnet: 40.64.0.0/10(-2.84), asn: 8075(-2.18), country: US(-0.06)]; MX_GOOD(-0.01)[mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com]; NEURAL_HAM_SHORT(-0.74)[-0.738,0]; RCVD_IN_DNSWL_NONE(0.00)[87.67.107.40.list.dnswl.org : 127.0.3.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8075, ipnet:40.64.0.0/10, country:US]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2019 21:27:59 -0000 Hi, I have created https://reviews.freebsd.org/D20487 for review. It adds a "-I" mountd option, which tells mountd to only update the exports in the kernel for cases that have changed during a reload of the exports file(s). It is for PR#237860 and can reduce the time that the nfsd threads are suspe= nded during a reload from seconds->milliseconds for a server with 20,000 exporte= d file systems. The patch is pretty large and, as such, won't be easy to review, but I hope= that someone can at least take a quick look at it. (I've listed asomers@ and kib@ as possible reviewers, but if anyone else wa= nts to review it, feel free to add yourself to the reviewers list.) I am looking to commit it in about two weeks. Thanks, rick From owner-freebsd-fs@freebsd.org Fri May 31 21:50:13 2019 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 B3A0F15C6BB6 for ; Fri, 31 May 2019 21:50:13 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670062.outbound.protection.outlook.com [40.107.67.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85B4F85DDA for ; Fri, 31 May 2019 21:50:12 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM (52.132.86.223) by QB1PR01MB3154.CANPRD01.PROD.OUTLOOK.COM (52.132.86.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.17; Fri, 31 May 2019 21:50:10 +0000 Received: from QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM ([fe80::a890:15d:5609:414d]) by QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM ([fe80::a890:15d:5609:414d%3]) with mapi id 15.20.1922.021; Fri, 31 May 2019 21:50:10 +0000 From: Rick Macklem To: "freebsd-fs@freebsd.org" Subject: RFC: should an incremental reload of exports for mountd be optional? Thread-Topic: RFC: should an incremental reload of exports for mountd be optional? Thread-Index: AQHVF/n5fA6XHqwN4UmNwJInW+ldyQ== Date: Fri, 31 May 2019 21:50:10 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 4edbaaa7-24a7-460f-82a2-08d6e611f477 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:QB1PR01MB3154; x-ms-traffictypediagnostic: QB1PR01MB3154: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:4502; x-forefront-prvs: 00540983E2 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(366004)(136003)(346002)(376002)(189003)(199004)(2501003)(786003)(316002)(53936002)(71190400001)(71200400001)(7696005)(74316002)(9686003)(99286004)(55016002)(305945005)(256004)(6436002)(14444005)(102836004)(6916009)(2906002)(81156014)(478600001)(25786009)(52536014)(2351001)(86362001)(5660300002)(6506007)(66446008)(486006)(33656002)(74482002)(46003)(4744005)(68736007)(186003)(8676002)(73956011)(66946007)(76116006)(66556008)(66476007)(64756008)(14454004)(81166006)(8936002)(476003); DIR:OUT; SFP:1101; SCL:1; SRVR:QB1PR01MB3154; H:QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: 6j8FpY7HpvoeAoqmGLEsUkVX2FYtp3o9XK+LYubY86OXQBdJaoznu6+cYzzZhRw4rZeJ1po5HwNJZLRCJby6/yiE+99Cn4olbicVxqQI/0nxsl1FN1jjqfMxP/UwxNazQ0prXqXjPkcLCOEeJROOYAHtLUavSwmJdIjhQyS/jp+dRqvoAMm9uOGCu6ccm4d0aN+KwpnudY2GK0tp86dIbAAxODmlGmN+IaUEWNl+tqFRc81abfkgk4VbYuWwYWfp/4sdAeix+lwITQ0XIYC0+eU2CAlDE9fOdwwCM6b0TDZaR78aGzVsKjxZbJNVqGdkZn4WgC3SWWLYxuuSVHVjlMpZsIo2foWr32vnrTJg6QpXQUwQZSgPw2DVI0azPoDMXqjMY5/0vTzDR5e5gTrK6LRpjA8b2BwjuYBDmfhcbPU= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 4edbaaa7-24a7-460f-82a2-08d6e611f477 X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2019 21:50:10.9179 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: rmacklem@uoguelph.ca X-MS-Exchange-Transport-CrossTenantHeadersStamped: QB1PR01MB3154 X-Rspamd-Queue-Id: 85B4F85DDA X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rmacklem@uoguelph.ca designates 40.107.67.62 as permitted sender) smtp.mailfrom=rmacklem@uoguelph.ca X-Spamd-Result: default: False [-3.21 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; DMARC_NA(0.00)[uoguelph.ca]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-1.02)[ipnet: 40.64.0.0/10(-2.84), asn: 8075(-2.18), country: US(-0.06)]; MX_GOOD(-0.01)[cached: mx2.hc184-76.ca.iphmx.com]; NEURAL_HAM_SHORT(-0.88)[-0.882,0]; RCVD_IN_DNSWL_NONE(0.00)[62.67.107.40.list.dnswl.org : 127.0.3.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8075, ipnet:40.64.0.0/10, country:US]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2019 21:50:13 -0000 Hi, I have created a patch for PR#237860 that improves the time it takes to rel= oad the exports file(s) for an NFS file server from seconds->milliseconds by on= ly doing system calls for the changes to the exports file(s). (Assumes each reload i= ncludes changes to only a small fraction of the entries.) I made it a non-default option of "-I", but asomers@ asked why it needed to= be optional. Basically, I made it optional because I felt the patch might still be buggy= and not handle some case of an exports file change that I missed. However, I can see the argument of making it non-optional (or optional but = enabled by default) so that sysadmins don't need to add "-I" to avoid long periods = where the nfsd threads are suspended. If it is broken, the deamon would need to be restarted to do a full reload,= but that would also be the case if a sysadmin specified the "-I" option. So, the question is... "do you think this should be an option or just alway= s enabled?". Thanks , rick From owner-freebsd-fs@freebsd.org Fri May 31 23:48:16 2019 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 BEDE015A483D for ; Fri, 31 May 2019 23:48:16 +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 4EB33895E3 for ; Fri, 31 May 2019 23:48:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0E1A715A483C; Fri, 31 May 2019 23:48:16 +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 EC61815A483B for ; Fri, 31 May 2019 23:48:15 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E4F8895E0 for ; Fri, 31 May 2019 23:48:15 +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 BDC561780A for ; Fri, 31 May 2019 23:48:14 +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 x4VNmEfc016638 for ; Fri, 31 May 2019 23:48:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4VNmEq3016637 for fs@FreeBSD.org; Fri, 31 May 2019 23:48:14 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 147881] [zfs] [patch] ZFS "sharenfs" doesn't allow different "exports" options for different hosts Date: Fri, 31 May 2019 23:48:14 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dgilbert@eicat.ca X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2019 23:48:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D147881 dgilbert@eicat.ca changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgilbert@eicat.ca --- Comment #11 from dgilbert@eicat.ca --- Please note, on dual stack systems this is required by practically the _default_ configuration. I was just rejiging my network a bit. I had 100'= s of hosts listed in my nfsshare property. It would all boil down to two network statements ... one ipv4 and one ipv6. EPHASIS MINE: this is a DEFAULT CONFIG IMHO on DUAL STACK systems. Something like sharenfs=3D"-network 1234:5678:9012:3456::/64 -network 192.168.0.0/24" --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Jun 1 21:57:28 2019 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 CB93715C6383 for ; Sat, 1 Jun 2019 21:57:28 +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 5C5DF77CCB for ; Sat, 1 Jun 2019 21:57:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1CFE915C637F; Sat, 1 Jun 2019 21:57:28 +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 0910B15C637E for ; Sat, 1 Jun 2019 21:57:28 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9486677CC6 for ; Sat, 1 Jun 2019 21:57:27 +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 D135C3911 for ; Sat, 1 Jun 2019 21:57:26 +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 x51LvQe7071388 for ; Sat, 1 Jun 2019 21:57:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x51LvQuP071387 for fs@FreeBSD.org; Sat, 1 Jun 2019 21:57:26 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 238229] zfs: scrub exceeds I/O qlen scrub_max_active limit, causes latency on 11.3-BETA1 Date: Sat, 01 Jun 2019 21:57:26 +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.2-STABLE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jun 2019 21:57:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238229 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.=