From owner-freebsd-fs@freebsd.org Sun Aug 28 04:27:25 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8CCAA9478B for ; Sun, 28 Aug 2016 04:27:25 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by mx1.freebsd.org (Postfix) with ESMTP id 6B892813 for ; Sun, 28 Aug 2016 04:27:24 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp14-2-4-72.lns21.adl2.internode.on.net (HELO leader.local) ([14.2.4.72]) by ipmail04.adl6.internode.on.net with ESMTP; 28 Aug 2016 13:57:18 +0930 Subject: Re: [ZFS] ARC accounting bug ? To: Ben RUBSON , FreeBSD FS References: <71DED907-10BE-44C2-982B-12974152895D@gmail.com> From: Shane Ambler Message-ID: <16ca6964-4d10-e4b0-7d9f-c1da5a95f5ac@ShaneWare.Biz> Date: Sun, 28 Aug 2016 13:57:16 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <71DED907-10BE-44C2-982B-12974152895D@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 04:27:25 -0000 On 28/08/2016 01:45, Ben RUBSON wrote: > >> On 27 Aug 2016, at 07:22, Shane Ambler wrote: >> >> On 26/08/2016 19:09, Ben RUBSON wrote: >>> Hello, >>> >>> Before opening a bug report, I would like to know whether what I see >>> is "normal" or not, and why. >> What I am seeing leads me to think that not all metadata is cached, >> maybe filename isn't cached, which can be a large string. >> >> while [ 1 ]; do find /usr/ports > /dev/null; done >> >> will list the path to every file and I see about 2 hits to a miss, yet >> >> while [ 1 ]; do ls -lR /usr/ports > /dev/null; done >> >> lists every filename as well as it's size, mod date, owner, permissions >> and it sits closer to 4 hits to every miss. >> >> And if the system disk cache contains the filenames that zfs isn't >> caching we won't need disk access to get the zfs misses. > > Playing with these commands : > # dtrace -n 'sdt:zfs::arc-hit {@[execname, stack()] = count();}' > # dtrace -n 'sdt:zfs::arc-miss {@[execname, stack()] = count();}' > > We can see that these are readdir calls which produce arc-misses, > andthat readdir calls also produce arc-hits. > > It would be interesting to know why some lead to hits, and some lead > to misses. > > (note that ls -lR / rsync commands produces exactly the same dtrace > results/numbers as find command) ls outputs the filename - find outputs the full path, could tracing back through parent folders get the extra misses. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-fs@freebsd.org Sun Aug 28 05:30:20 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6EEDB78AD1 for ; Sun, 28 Aug 2016 05:30:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6A6FC80 for ; Sun, 28 Aug 2016 05:30:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7S5UJQC079581 for ; Sun, 28 Aug 2016 05:30:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Sun, 28 Aug 2016 05:30:20 +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.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: peter@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 05:30:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 --- Comment #6 from Peter Wemm --- It is very confusing as the compiler is doing extensive inlining. As near as I can tell, the area you asked about is like this: softdep_freefile(): handle_bufwait(inodedep, &freefile->fx_jwork); 7568 clear_unlinked_inodedep(inodedep); -> clear_unlinked_inodedep(): 9685: bwrite(bp); ACQUIRE_LOCK(ump); ->=20 bwrite(): 393: return (BO_WRITE(bp->b_bufobj, bp)); -> I'm confused after here. The return address of the frame is softdep_freefile+0x66c, which is the inlined sys/buf.h BO_WRITE macro. I *think* the chain continues from BO_WRITE() -> ffs_bufwrite() -> bufwrite= () -> bstrategy()-> ffs_geom_strategy(). I am 100% confident that it is originating from clear_unlinked_inodedep(). = 99% sure it is the first bwrite(), not the second one at line 9699. Is this of any help? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Aug 28 05:38:07 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7213EB78C7A for ; Sun, 28 Aug 2016 05:38: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 mx1.freebsd.org (Postfix) with ESMTPS id 5444EF77 for ; Sun, 28 Aug 2016 05:38:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7S5c6r7098087 for ; Sun, 28 Aug 2016 05:38:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Sun, 28 Aug 2016 05:38: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.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: peter@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 05:38:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 --- Comment #7 from Peter Wemm --- FWIW; I'm comparing 'objdump --disassemble' vs adding the '-S -fverbose-asm' flags to the compile phases. That plus picking fragments out of the console= log of past crashes. The machine is running RC1 binaries so you can recreate t= hem and look at them too. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Aug 28 05:46:57 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73BA6B78F37 for ; Sun, 28 Aug 2016 05:46:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63A767C7 for ; Sun, 28 Aug 2016 05:46:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7S5kuV4018013 for ; Sun, 28 Aug 2016 05:46:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Sun, 28 Aug 2016 05:46:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: peter@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 05:46:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 --- Comment #8 from Peter Wemm --- One more comment: ffs_vfree() appears to be compiled as a tail jump into the body of ffs_freefile() rather than a call/return. This may lead to "interesting" backtraces. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Aug 28 20:06:58 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5377DB7869D for ; Sun, 28 Aug 2016 20:06:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 435808E for ; Sun, 28 Aug 2016 20:06:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7SK6vj0093684 for ; Sun, 28 Aug 2016 20:06:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Sun, 28 Aug 2016 20:06:57 +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.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: Andrew@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 20:06:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 --- Comment #9 from Andrew Turner --- I think you can add '-fno-optimize-sibling-calls' to CFLAGS to disable the = tail jumps, e.g. in sys/conf/Makefile.arm64. >From my reading of the asm wk is valid, wk->wk_mp is invalid. The VFSTOUFS macro contains: #define VFSTOUFS(mp) ((struct ufsmount *)((mp)->mnt_data)) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Aug 28 21:00:38 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F10FBC1A5E for ; Sun, 28 Aug 2016 21:00:38 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 725D420B for ; Sun, 28 Aug 2016 21:00:38 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7SL01Me005972 for ; Sun, 28 Aug 2016 21:00:38 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201608282100.u7SL01Me005972@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 28 Aug 2016 21:00:38 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 21:00:38 -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 | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 203419 | solaris assert: (dn->dn_phys->dn_nlevels == 0 && Open | 211491 | System hangs after "Uptime" on reboot with ZFS 7 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Aug 29 21:29:22 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91758BC7918 for ; Mon, 29 Aug 2016 21:29:22 +0000 (UTC) (envelope-from julien@perdition.city) Received: from relay-b01.edpnet.be (relay-b01.edpnet.be [212.71.1.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "edpnet.email", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5136736D for ; Mon, 29 Aug 2016 21:29:20 +0000 (UTC) (envelope-from julien@perdition.city) X-ASG-Debug-ID: 1472505001-0a7ff52c9eb74980001-3nHGF7 Received: from mordor.lan (77.109.124.121.adsl.dyn.edpnet.net [77.109.124.121]) by relay-b01.edpnet.be with ESMTP id 68ChFQ4k32ggp5Ds (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 29 Aug 2016 23:10:02 +0200 (CEST) X-Barracuda-Envelope-From: julien@perdition.city X-Barracuda-Effective-Source-IP: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Apparent-Source-IP: 77.109.124.121 Date: Mon, 29 Aug 2016 23:10:01 +0200 From: Julien Cigar To: freebsd-fs@freebsd.org Subject: ZFS + NFS + multiple hosts/mount options ..? Message-ID: <20160829211001.GI1779@mordor.lan> X-ASG-Orig-Subj: ZFS + NFS + multiple hosts/mount options ..? MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JsihDCElWRmQcbOr" Content-Disposition: inline User-Agent: Mutt/1.6.1 (2016-04-27) X-Barracuda-Connect: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Start-Time: 1472505001 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://212.71.1.221:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 621 X-Virus-Scanned: by bsmtpd at edpnet.be X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.5047 1.0000 0.7500 X-Barracuda-Spam-Score: 2.25 X-Barracuda-Spam-Status: No, SCORE=2.25 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=BSF_SC0_MV0713, BSF_SC0_MV0713_2 X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.32435 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.50 BSF_SC0_MV0713 Custom rule MV0713 1.00 BSF_SC0_MV0713_2 BSF_SC0_MV0713_2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2016 21:29:22 -0000 --JsihDCElWRmQcbOr Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, Is there a way through the zfs set sharenfs=3D"..." property to share data/somefs readonly to host "dev.lan" _and_ read/write to host=20 "duvel.prod.lan" ? Or should I just set sharenfs=3D"off" and use /etc/exports (I'm using NFS4) ? It seems impossible to have multiple hosts/options/... when the sharenfs property is used .. Thanks! Julien --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --JsihDCElWRmQcbOr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCgAGBQJXxKSkAAoJELK7NxCiBCPAkcQQANWV0TdpcB2bphphL3FEW8vS v+Hwk1JQWAkDhEV/vNhTlSF0b+1B2/USRPIT5+jp+uXDQ6yO6bdqP36arxO1sjNX zdCplV85qxSFASFhPYnH+QwsUCLxo13JZExvT5T8lyt1r2chzybHa6lTATC3TEhj uc7DlLuukaDU7B9Y2uFa7Y7I0IOPZErmhA3VzBJJqGF+2+lPitXj3ddJN9hcdROu Ic3my/yl7ildq7F4Id5N2T3eYRTYTgfBVl03vW10p6PHivKDqBU6IBemZ1DCrQe1 1heeTyEs063RfSex+hPxaXilwWY6YSChvZikBFLDn4PbMB1zBoZE21DK/OXxC5gr /ngutuR9GJxGtqE97abZxXTF3lrbtZILWFlH0uEQiG1nBRDXXp69VRIegEN5JxtX d5TvCU8iDowSbYqCEbJ1TH7HlEDfPaZYFmHzEw/anca/mZcUG93RV+01ME3RGXOW jfQF8RLO+MiObb9fM+wluRAGcGu0DbEnAuQBZVwbrm3/H/fVBL1bZvOhD7VjmQN6 KikBM4k4rmDeQOo/ZAnJoSo3ryQcsMIrM6Y6SdelgKgaVPsBbFlLO5hb6Xa7/hkg tTG+qbg1LPbr6r86eyErpMb4CmAUwS6LjorXJ55nm2TW8vjzYt7ZesdgOMHoygid NGlkqXCEGONVtbGyG9JA =VVJr -----END PGP SIGNATURE----- --JsihDCElWRmQcbOr-- From owner-freebsd-fs@freebsd.org Tue Aug 30 12:01:18 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E374BC889F for ; Tue, 30 Aug 2016 12:01:18 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 14F327B4 for ; Tue, 30 Aug 2016 12:01:18 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.221.107] (unknown [185.79.217.61]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 20C4F2B3; Tue, 30 Aug 2016 15:01:10 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: ZFS + NFS + multiple hosts/mount options ..? References: <20160829211001.GI1779@mordor.lan> To: Julien Cigar , freebsd-fs@freebsd.org From: Lev Serebryakov Organization: FreeBSD Message-ID: <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> Date: Tue, 30 Aug 2016 14:01:09 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160829211001.GI1779@mordor.lan> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 12:01:18 -0000 On 29.08.2016 23:10, Julien Cigar wrote: > Is there a way through the zfs set sharenfs="..." property to share > data/somefs readonly to host "dev.lan" _and_ read/write to host > "duvel.prod.lan" ? Or should I just set sharenfs="off" and use > /etc/exports (I'm using NFS4) ? It seems impossible to have multiple > hosts/options/... when the sharenfs property is used .. No luck here. I've raised this question multiple times withoput any reaction. Here is (very old) PRs with patch, which implements this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147881 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202820 -- // Lev Serebryakov From owner-freebsd-fs@freebsd.org Tue Aug 30 13:37:11 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74C5FBC7626 for ; Tue, 30 Aug 2016 13:37:11 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 41DE2F72 for ; Tue, 30 Aug 2016 13:37:11 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bejDw-0007CN-T8; Tue, 30 Aug 2016 14:37:09 +0100 Date: Tue, 30 Aug 2016 14:37:08 +0100 From: Gary Palmer To: Ben RUBSON Cc: FreeBSD FS Subject: Re: [ZFS] ARC accounting bug ? Message-ID: <20160830133708.GD56297@in-addr.com> References: <71DED907-10BE-44C2-982B-12974152895D@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <71DED907-10BE-44C2-982B-12974152895D@gmail.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 13:37:11 -0000 On Sat, Aug 27, 2016 at 06:15:18PM +0200, Ben RUBSON wrote: > Playing with these commands : > # dtrace -n 'sdt:zfs::arc-hit {@[execname, stack()] = count();}' > # dtrace -n 'sdt:zfs::arc-miss {@[execname, stack()] = count();}' > > We can see that these are readdir calls which produce arc-misses, and that readdir calls also produce arc-hits. > > It would be interesting to know why some lead to hits, and some lead to misses. > > (note that ls -lR / rsync commands produces exactly the same dtrace results/numbers as find command) If the *same* readdir() call produces both a hit and a miss, my guess would be that it is hitting two data sources for the data. I am not familiar with ZFS, however UFS treats a directory as a special type of file. Filename information and the inode associated with that filename would be in the directory "file. The inodes would be in the inode table. If ZFS is similar, then the directory "file" reads would be misses and the inode table reads would be hits Regards, Gary From owner-freebsd-fs@freebsd.org Tue Aug 30 16:31:36 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9862BC8EA3 for ; Tue, 30 Aug 2016 16:31:36 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (gtw.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 71D1EB62; Tue, 30 Aug 2016 16:31:36 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 4C22326EC3; Tue, 30 Aug 2016 18:31:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DXtwTp-kEAiv; Tue, 30 Aug 2016 18:31:31 +0200 (CEST) Received: from [192.168.10.10] (asus [192.168.10.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 966DA26EC2; Tue, 30 Aug 2016 18:31:31 +0200 (CEST) Subject: Re: ZFS + NFS + multiple hosts/mount options ..? To: lev@FreeBSD.org, Julien Cigar , freebsd-fs@freebsd.org References: <20160829211001.GI1779@mordor.lan> <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> From: Willem Jan Withagen Message-ID: Date: Tue, 30 Aug 2016 18:31:30 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 16:31:36 -0000 On 30-8-2016 14:01, Lev Serebryakov wrote: > On 29.08.2016 23:10, Julien Cigar wrote: > >> Is there a way through the zfs set sharenfs="..." property to share >> data/somefs readonly to host "dev.lan" _and_ read/write to host >> "duvel.prod.lan" ? Or should I just set sharenfs="off" and use >> /etc/exports (I'm using NFS4) ? It seems impossible to have multiple >> hosts/options/... when the sharenfs property is used .. > No luck here. I've raised this question multiple times withoput any > reaction. Here is (very old) PRs with patch, which implements this: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147881 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202820 > I'd say, forget about getting any flexible through sharenfs. Did that discussion about 3 years ago, and it boiled down. Don't dare to change it because the people doing ZFS don't like it. No use in pulling a dead horse. --WjW From owner-freebsd-fs@freebsd.org Tue Aug 30 16:46:47 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1691BC83E1 for ; Tue, 30 Aug 2016 16:46:47 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id 986BCBA4 for ; Tue, 30 Aug 2016 16:46:47 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.221.107] (unknown [185.79.217.61]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 54655313; Tue, 30 Aug 2016 19:46:45 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: ZFS + NFS + multiple hosts/mount options ..? References: <20160829211001.GI1779@mordor.lan> <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> To: Willem Jan Withagen , Julien Cigar , freebsd-fs@freebsd.org From: Lev Serebryakov Organization: FreeBSD Message-ID: <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org> Date: Tue, 30 Aug 2016 18:46:44 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 16:46:47 -0000 On 30.08.2016 18:31, Willem Jan Withagen wrote: >>> Is there a way through the zfs set sharenfs="..." property to share >>> data/somefs readonly to host "dev.lan" _and_ read/write to host >>> "duvel.prod.lan" ? Or should I just set sharenfs="off" and use >>> /etc/exports (I'm using NFS4) ? It seems impossible to have multiple >>> hosts/options/... when the sharenfs property is used .. >> No luck here. I've raised this question multiple times withoput any >> reaction. Here is (very old) PRs with patch, which implements this: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147881 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202820 >> > > I'd say, forget about getting any flexible through sharenfs. WHY?! > Did that discussion about 3 years ago, and it boiled down. Don't dare to I don't see any good reason to not support this, aside "It will not be compatible with Illumos". I don't buy this, sorry. Any other reasons? > change it because the people doing ZFS don't like it. There is one BIG problem: deep ZFS hierarchies. If I need to export 100 FSes (100 users' home directories, for example) in one ZFS tree to 4 networks (2xIPv4, 2xIPv6) I need to add 400 (!!!) lines to /etc/exports by hands. All these lines will be virtually the same, and good luck to maintain this mess. If "sharenfs" supports multiple hosts/networks, I need to set this property ONCE (on zpool/home, parent of all FSes in question) and IT'S ALL! And if I need to change same options, I need to change it ONCE and re-export ZFS. Unfortunately, it is NOT enough to export parent FS :( -- // Lev Serebryakov From owner-freebsd-fs@freebsd.org Tue Aug 30 17:40:45 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0BC5EBC9595 for ; Tue, 30 Aug 2016 17:40:45 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (gtw.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 C8F07C9C; Tue, 30 Aug 2016 17:40:44 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 52398261DA; Tue, 30 Aug 2016 19:40:40 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZ0sxkzAAXPu; Tue, 30 Aug 2016 19:40:39 +0200 (CEST) Received: from [192.168.10.10] (asus [192.168.10.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 65AE9261D9; Tue, 30 Aug 2016 19:40:39 +0200 (CEST) Subject: Re: ZFS + NFS + multiple hosts/mount options ..? To: lev@FreeBSD.org, Julien Cigar , freebsd-fs@freebsd.org References: <20160829211001.GI1779@mordor.lan> <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org> From: Willem Jan Withagen Message-ID: Date: Tue, 30 Aug 2016 19:40:37 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 17:40:45 -0000 On 30-8-2016 18:46, Lev Serebryakov wrote: > On 30.08.2016 18:31, Willem Jan Withagen wrote: > >>>> Is there a way through the zfs set sharenfs="..." property to share >>>> data/somefs readonly to host "dev.lan" _and_ read/write to host >>>> "duvel.prod.lan" ? Or should I just set sharenfs="off" and use >>>> /etc/exports (I'm using NFS4) ? It seems impossible to have multiple >>>> hosts/options/... when the sharenfs property is used .. >>> No luck here. I've raised this question multiple times withoput any >>> reaction. Here is (very old) PRs with patch, which implements this: >>> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147881 >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202820 >>> >> >> I'd say, forget about getting any flexible through sharenfs. > WHY?! > >> Did that discussion about 3 years ago, and it boiled down. Don't dare to > I don't see any good reason to not support this, aside "It will not be > compatible with Illumos". I don't buy this, sorry. Any other reasons? > >> change it because the people doing ZFS don't like it. > There is one BIG problem: deep ZFS hierarchies. If I need to export 100 > FSes (100 users' home directories, for example) in one ZFS tree to 4 > networks (2xIPv4, 2xIPv6) I need to add 400 (!!!) lines to /etc/exports > by hands. All these lines will be virtually the same, and good luck to > maintain this mess. > > If "sharenfs" supports multiple hosts/networks, I need to set this > property ONCE (on zpool/home, parent of all FSes in question) and IT'S > ALL! And if I need to change same options, I need to change it ONCE and > re-export ZFS. > > Unfortunately, it is NOT enough to export parent FS :( Hi Lev, I agree with you More or less the arguments I had at that time. (though I don't have that many FSes.) And I gave up. Perhaps that tells more about me than anything else. The discussion I tried to have was cut short with the argument that it would not go in because upstream would not like it, or would not want in the version I submitted. But please do feel free and get something in that would please more. --WjW From owner-freebsd-fs@freebsd.org Tue Aug 30 18:11:16 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 388E3BC9F8A for ; Tue, 30 Aug 2016 18:11:16 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF223386 for ; Tue, 30 Aug 2016 18:11:15 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id i5so4248095wmg.2 for ; Tue, 30 Aug 2016 11:11:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=747im0ieYr+BvUDRtf247axFCqL69k8DXXAv8DffLbM=; b=0oWFCwVhAH02ZBpDtt4+19LpZB/96gcOCXZ/qSOIYWX1vUvk8HkPT7nKHz9CKdFE6j 7FWWnfz9FSduwhKozvR27Lf8iscFPDSWsnFR0fMp1xC4WvNqFRkHk2oYaV28wBhZ7zJB I5trh/Npgwob3bkZvlNkYLiFWfN0lsJPz4qvnFN852B7a+ic5qLOlqh0b2zhWdIVBtG9 UGWAzjTwHOTtNzxF1SMouuO1xzygumvRADVa51jKdvVrfHnqb3SFKo1JkrCn++Fn7kKI VBCHKfqUAZmuTbCxgDlg7eMrEEFWegCulAu/Ez46BxtRiq0ug6P0mKs7uj4KROnPMDnB HPCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=747im0ieYr+BvUDRtf247axFCqL69k8DXXAv8DffLbM=; b=B/WOayRb7LRSNaiJ5gN/oO0DZTlPBRkcNrW2ncp62dbMKqEEHuzBHOtFj6LeKc4z6k tO7BkGjEyy4+JHm43uhlUI8+HXrhkZys0q2OWbBnpOVMTzjfRC6QyHhRLpC6UVnsV1Us 538RZHNEnNfWScPwfJxfyuLGlviZ/jOnqT83vDUwwAEST0YdNJqEeygICwvNMYYHOLEv nuf+82FQHvrWCGlc3IyTOvOa+ipGD6+pAihYcHLDcQCdjmU9Sp2m7Z7xVV0WYmAbwGXq /GbRTrd/eIYxzTEmDfxotlOOpi1VYxJ7NnM5HTNv0lga4xm6qOnOrwPyvOry38M3RWmr Fmew== X-Gm-Message-State: AE9vXwMjp2YXdY1bQvsWZEp5/ysjxyf0O95b6eiAY6mMCxFGqHONkAnAWauS4WBHiC2vdQ== X-Received: by 10.194.142.78 with SMTP id ru14mr4523289wjb.41.1472580673866; Tue, 30 Aug 2016 11:11:13 -0700 (PDT) Received: from macbook-air-de-benjamin-1.home (ANice-651-1-19-245.w86-203.abo.wanadoo.fr. [86.203.34.245]) by smtp.gmail.com with ESMTPSA id o2sm40604273wjo.3.2016.08.30.11.11.12 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 30 Aug 2016 11:11:13 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [ZFS] ARC accounting bug ? From: Ben RUBSON In-Reply-To: <20160830133708.GD56297@in-addr.com> Date: Tue, 30 Aug 2016 20:11:12 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <234E7AF8-389C-4D27-82D1-81BF270D9376@gmail.com> References: <71DED907-10BE-44C2-982B-12974152895D@gmail.com> <20160830133708.GD56297@in-addr.com> To: FreeBSD FS X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 18:11:16 -0000 > On 30 Aug 2016, at 15:37, Gary Palmer wrote: >=20 > On Sat, Aug 27, 2016 at 06:15:18PM +0200, Ben RUBSON wrote: >> Playing with these commands : >> # dtrace -n 'sdt:zfs::arc-hit {@[execname, stack()] =3D count();}' >> # dtrace -n 'sdt:zfs::arc-miss {@[execname, stack()] =3D count();}' >>=20 >> We can see that these are readdir calls which produce arc-misses, and = that readdir calls also produce arc-hits. >>=20 >> It would be interesting to know why some lead to hits, and some lead = to misses. >>=20 >> (note that ls -lR / rsync commands produces exactly the same dtrace = results/numbers as find command) >=20 > If the *same* readdir() call produces both a hit and a miss, my guess = would > be that it is hitting two data sources for the data. I investigated further, and found that : - readdir() first produces a miss when it returns the "." entry. - readdir() then does not produce any miss for the other entries. - readdir() finally produces a miss when it does not return any value = (no more entry). I also noted that misses are not produced every time, it seems to depend = on the folder content. It is possible to generate so many misses when using find in a loop on a = huge folder that if these misses were finally redirect to disks, zpool = iostat would show use some IOs. But this is not the case. It looks strange. Cache hits statistics can then be degraded even if there are no disk IOs = at all. > I am not familiar with ZFS, however UFS treats a directory as a = special=20 > type of file. Filename information and the inode associated with that > filename would be in the directory "file. The inodes would be in the = inode > table. >=20 > If ZFS is similar, then the directory "file" reads would be misses and > the inode table reads would be hits >=20 > Regards, >=20 > Gary Thank you for your answer Gary ! Regards, Ben From owner-freebsd-fs@freebsd.org Tue Aug 30 19:15:20 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0F49BC9BC6 for ; Tue, 30 Aug 2016 19:15:20 +0000 (UTC) (envelope-from julien@perdition.city) Received: from relay-b03.edpnet.be (relay-b03.edpnet.be [212.71.1.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "edpnet.email", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6902F80D for ; Tue, 30 Aug 2016 19:15:19 +0000 (UTC) (envelope-from julien@perdition.city) X-ASG-Debug-ID: 1472583604-0a88181ce43213a60001-3nHGF7 Received: from mordor.lan (77.109.124.121.adsl.dyn.edpnet.net [77.109.124.121]) by relay-b03.edpnet.be with ESMTP id v1IHGdFyY7ea7UvM (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Aug 2016 21:00:05 +0200 (CEST) X-Barracuda-Envelope-From: julien@perdition.city X-Barracuda-Effective-Source-IP: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Apparent-Source-IP: 77.109.124.121 Date: Tue, 30 Aug 2016 21:00:04 +0200 From: Julien Cigar To: Lev Serebryakov Cc: Willem Jan Withagen , freebsd-fs@freebsd.org Subject: Re: ZFS + NFS + multiple hosts/mount options ..? Message-ID: <20160830190004.GM1779@mordor.lan> X-ASG-Orig-Subj: Re: ZFS + NFS + multiple hosts/mount options ..? References: <20160829211001.GI1779@mordor.lan> <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="sy9WyBOsCRoUO165" Content-Disposition: inline In-Reply-To: <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-Barracuda-Connect: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Start-Time: 1472583604 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://212.71.1.220:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 2479 X-Virus-Scanned: by bsmtpd at edpnet.be X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.5000 1.0000 0.0100 X-Barracuda-Spam-Score: 0.01 X-Barracuda-Spam-Status: No, SCORE=0.01 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.32464 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 19:15:20 -0000 --sy9WyBOsCRoUO165 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 30, 2016 at 06:46:44PM +0200, Lev Serebryakov wrote: > On 30.08.2016 18:31, Willem Jan Withagen wrote: >=20 > >>> Is there a way through the zfs set sharenfs=3D"..." property to share > >>> data/somefs readonly to host "dev.lan" _and_ read/write to host=20 > >>> "duvel.prod.lan" ? Or should I just set sharenfs=3D"off" and use > >>> /etc/exports (I'm using NFS4) ? It seems impossible to have multiple > >>> hosts/options/... when the sharenfs property is used .. > >> No luck here. I've raised this question multiple times withoput any > >> reaction. Here is (very old) PRs with patch, which implements this: > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D147881 > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202820 > >> > >=20 > > I'd say, forget about getting any flexible through sharenfs. > WHY?! >=20 > > Did that discussion about 3 years ago, and it boiled down. Don't dare to > I don't see any good reason to not support this, aside "It will not be > compatible with Illumos". I don't buy this, sorry. Any other reasons? >=20 > > change it because the people doing ZFS don't like it. > There is one BIG problem: deep ZFS hierarchies. If I need to export 100 > FSes (100 users' home directories, for example) in one ZFS tree to 4 > networks (2xIPv4, 2xIPv6) I need to add 400 (!!!) lines to /etc/exports > by hands. All these lines will be virtually the same, and good luck to > maintain this mess. I agree with you, although in my case it's not so much an issue as everything is managed by SaltStack ... but it's rather ugly to have 100+ lines in /etc/exports. What's more problematic is that it's virtually impossible (without ugly=20 hacks) to share a simple zfs fs "ro" to one net, and "rw" to another=20 one with the sharenfs property Anyway, I ditched sharenfs, zfs share, ... and I use /etc/exports >=20 > If "sharenfs" supports multiple hosts/networks, I need to set this > property ONCE (on zpool/home, parent of all FSes in question) and IT'S > ALL! And if I need to change same options, I need to change it ONCE and > re-export ZFS. >=20 > Unfortunately, it is NOT enough to export parent FS :( >=20 > --=20 > // Lev Serebryakov --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --sy9WyBOsCRoUO165 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCgAGBQJXxdewAAoJELK7NxCiBCPAq8oP/23of3AKnzKRg0QXJWn2P1Py lVca2VI4skItpDT97Vr3BGmjnF3DuWd1e6UThR55HafvuCj8fEje8DJsh/sgJtBH x4cDYH0SZ+B92cQqux+p1SuJTtcdv1gqj3OczQfrOLU1RsRhBvaLz40hVar0lBiH uTUzKWBEtHbcxmYtlKDMmLwJqH/gP3wewmUhxxuHuvfxDKV+0DQ7eDf7OBiFM3rT B/iaWpwoqcBFe5oRpfLIhcKL3jkQHZrGWGhLXFEAZyxkNG/YxeE0yNcSkf48Ol98 RygB0c8hF/yBj8y7rga1Xm93olQUXw/UHUmwbRrlSq0puGHlmrlhEK4GjUKQ/YW/ X7Khg0V4hfqMlv8UbMiWG/umzVQtE6iai9YMG4Z9RVA1O2cVm4DjHJmsFkHvEnu4 2V2T7+moank05FnWl4Bz59rVYbjKaR2yB4MPM8JMInZvZ+9sNacMIIACprSyGA3k WLj/i7KVAR3dT8hkcacYPTpv5iuDsS4GDZQRjFhbg9l+QBeSbvHsKLItU5r8vAa/ PA3tm7VzlbX4uMs83BJz5ldxAK/XMd3t7iBCCUv2Vu4b9gAmKkarW026+yLYcBt5 VmpLE09OjXpXG9OG1E6NYWDghdA/JodNioYZD03P34+psmNRQfa63gCO64mCMAak pvp5zqxam/FIZ5WE5ng6 =K9Ky -----END PGP SIGNATURE----- --sy9WyBOsCRoUO165-- From owner-freebsd-fs@freebsd.org Tue Aug 30 23:55:28 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C7E8BC92C5 for ; Tue, 30 Aug 2016 23:55:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D6B44265C for ; Tue, 30 Aug 2016 23:55:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7UNtQ47087972 for ; Tue, 30 Aug 2016 23:55:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Tue, 30 Aug 2016 23:55: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.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 23:55:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 --- Comment #10 from Kirk McKusick --- It appears that there is an item on the worklist that has been prematurely freed. This freeing should be impossible as anything on a worklist has its ONWORKLIST flag set and the worklist freeing routine will panic if the ONWORKLIST flag is set. However I have written the following check to see i= f we are finding freed items on the worklist in softdep_disk_io_initiation(): Index: sys/ufs/ffs/ffs_softdep.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/ufs/ffs/ffs_softdep.c (revision 305057) +++ sys/ufs/ffs/ffs_softdep.c (working copy) @@ -9949,6 +9949,13 @@ if ((wk =3D LIST_FIRST(&bp->b_dep)) =3D=3D NULL) return; + if (wk->wk_type > D_LAST + 1) { + printf("dead worklist: %p next %p prev %p type %s state 0x%X\n", + wk, wk->wk_list.le_next, wk->wk_list.le_prev, + TYPENAME(wk->wk_type), wk->wk_state); + LIST_INIT(&bp->b_dep); + return; + } ump =3D VFSTOUFS(wk->wk_mp); marker.wk_type =3D D_LAST + 1; /* Not a normal workitem */ I would appreciate your running with this patch and reporting if you get the "dead worklist" error message. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 31 12:12:36 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7BC4BCA125 for ; Wed, 31 Aug 2016 12:12:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7575BAC for ; Wed, 31 Aug 2016 12:12:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7VCCakB090507 for ; Wed, 31 Aug 2016 12:12:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Wed, 31 Aug 2016 12:12:37 +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.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: Andrew@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 12:12:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 --- Comment #11 from Andrew Turner --- I see that WORKLIST_INSERT will set ONWORKLIST in wk_state. Is this always locked? The existence of WORKLIST_INSERT_UNLOCKED seems to imply it's not. = As arm64 has a weaker memory model than x86 the ordering of setting this bit a= nd adding the item to the list is not guaranteed. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 31 13:49:34 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A958ABC9D51 for ; Wed, 31 Aug 2016 13:49:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 98D67EAC for ; Wed, 31 Aug 2016 13:49:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7VDnY4L034949 for ; Wed, 31 Aug 2016 13:49:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212245] ZFS volume (zvol) does not honor fsync() with sync=standard Date: Wed, 31 Aug 2016 13:49:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 13:49:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212245 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org CC|freebsd-amd64@FreeBSD.org | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 31 14:04:08 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B595FBCA3A8 for ; Wed, 31 Aug 2016 14:04:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A53B4F2 for ; Wed, 31 Aug 2016 14:04:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7VE48WP008867 for ; Wed, 31 Aug 2016 14:04:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212245] ZFS volume (zvol) does not honor fsync() with sync=standard Date: Wed, 31 Aug 2016 14:04:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: lordcrc@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 14:04:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212245 --- Comment #3 from Asbj=C3=B8rn --- When sync=3Dalways, the results are as expected, the issue is when sync=3Ds= tandard, which, according to the documentation should respect fsync(). As mentioned, the issue is present with iSTGT using the zvol, so this is no= t a UFS-on-zvol issue as far as I can see. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 31 15:06:24 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7BA0BCA22E for ; Wed, 31 Aug 2016 15:06:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C79E29F5 for ; Wed, 31 Aug 2016 15:06:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7VF6OkL056938 for ; Wed, 31 Aug 2016 15:06:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Wed, 31 Aug 2016 15:06:24 +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.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 15:06:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 --- Comment #12 from Konstantin Belousov --- (In reply to Andrew Turner from comment #11) WORKLIST_INSERT_UNLOCKED() is used in only one place, where workhead is private. Also, from what I understand, the workitems from that list cannot= be attached to the inodeblock. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 31 16:51:07 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23FD9BCA072 for ; Wed, 31 Aug 2016 16:51:07 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-it0-f47.google.com (mail-it0-f47.google.com [209.85.214.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDA25A34; Wed, 31 Aug 2016 16:51:06 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-it0-f47.google.com with SMTP id g62so107514599ith.1; Wed, 31 Aug 2016 09:51:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=BpTZgxhOvjUbzm3buCMksnauD4uA+CsWj73h+NSXgBo=; b=HORtBsCTpkNV3qPG0OLUpZURq2ZCo1Qi7DVDk7qtNNK/EbQQxScNlZIqJtZifYP3Wk yFbWRKjGcjjK6j+n0JLhv0Q99ABbOmSpbl6+9y96WBq73KTmCg1idvtGHdyED8Z2MwS2 jxgWO9YtVvYtBsptVBgC71VfKZu1Kh9q6sj4JAVjuhBfMbziQlir1FX4kdX63jZ3GYC4 nDia0G5bhe77cbSPDZV8r7ggFw14k3s7lNbpKeUMByoJOJ7DsiqZRf31oJpXjrwrZfia cIrEJiaK+EI6ji7aAdxe07t6X3tI9aznB78TUPn6xi7ezH2ETOxkBMQPkU6RkJhPS38z iqcw== X-Gm-Message-State: AE9vXwN0QYVHdgqQvvmNXj4JP9gRdYaFKzUhIgRrmviKeTXzI50K3mH3wJF8Nsyesczk4A== X-Received: by 10.36.104.73 with SMTP id v70mr15178142itb.12.1472662265626; Wed, 31 Aug 2016 09:51:05 -0700 (PDT) Received: from WorkBox.Home.gmail.com (97-116-18-208.mpls.qwest.net. [97.116.18.208]) by smtp.gmail.com with ESMTPSA id 140sm12704608itl.4.2016.08.31.09.51.04 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 31 Aug 2016 09:51:04 -0700 (PDT) References: <20160829211001.GI1779@mordor.lan> <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org> User-agent: mu4e 0.9.16; emacs 24.5.1 From: Brandon J. Wandersee To: Willem Jan Withagen Cc: lev@FreeBSD.org, Julien Cigar , freebsd-fs@freebsd.org Subject: Re: ZFS + NFS + multiple hosts/mount options ..? In-reply-to: Date: Wed, 31 Aug 2016 11:51:05 -0500 Message-ID: <86zinsswzq.fsf@WorkBox.Home> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 16:51:07 -0000 Willem Jan Withagen writes: >> There is one BIG problem: deep ZFS hierarchies. If I need to export 100 >> FSes (100 users' home directories, for example) in one ZFS tree to 4 >> networks (2xIPv4, 2xIPv6) I need to add 400 (!!!) lines to /etc/exports >> by hands. All these lines will be virtually the same, and good luck to >> maintain this mess. >> >> If "sharenfs" supports multiple hosts/networks, I need to set this >> property ONCE (on zpool/home, parent of all FSes in question) and IT'S >> ALL! And if I need to change same options, I need to change it ONCE and >> re-export ZFS. >> >> Unfortunately, it is NOT enough to export parent FS :( > > Hi Lev, > > I agree with you > > More or less the arguments I had at that time. > (though I don't have that many FSes.) > > And I gave up. Perhaps that tells more about me than anything else. > The discussion I tried to have was cut short with the argument that it > would not go in because upstream would not like it, or would not want > in the version I submitted. > > But please do feel free and get something in that would please more. Has a script that recurses through a directory tree and adds valid entries to the exports file been considered as a viable option? "sharenfs=" just adds syntactically valid entries to /etc/zfs/exports; NFS does the rest. There are probably a number of reasons that making "sharenfs" more complicated isn't in the cards. I suspect "upstream won't like it" may just be short-hand for "Nobody wants to do the work to implement and maintain a feature across multiple operating systems that can be implemented by the tiny fraction of users who want it with the tools already available to them." But besides that, yes, being able to set an option once at a root point and have that option affect all descendant filesystems appears simple and easy, because you're dealing with one very simple use case with predictable results. That simplicity and predictability immediately break down once you start changing options for individual descendant filesystems, which someone would inevitably want to do. ("If it's possible to implement this, then why not that? That's simple enough, right?") Or what about people who only want to export 60 of the 100 child filesystems? They still have to either set the property manually on all their filesystems, or create new dataset trees to separate shared from unshared filesystems. Is implementing inheritance for "sharenfs" really going to relieve enough tedium of enough users to make it worthwhile? And then there's the fact that NFS by its nature does not cross filesystem boundaries, which ZFS inheritance would do if the "sharenfs" property were inherited, making ZFS sharing unpredictable to someone used to managing complicated NFS groups on anything other than ZFS. At that point it's become easier to manage lots of shares and harder to manage only a few shares exclusively. In such cases, is it really easier *not* to write an exports file by hand? That's what you're getting, after all: whether you copy lines in a text file or enter `zfs set sharenfs=` 50 times, you're still typing out the name of filesystem 50 times while everything else is automated... I'm not saying none of this can be implemented, or that the developers shouldn't be sympathetic to users. Just that a small group's convenience doesn't trump the needs of a larger group, and that the developers probably have more reasons not to bother with this than mere laziness or a lack of compassion. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ---------------------------------- From owner-freebsd-fs@freebsd.org Wed Aug 31 17:30:07 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA7ECBCADF6 for ; Wed, 31 Aug 2016 17:30:07 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (gtw.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 71F4E3B5; Wed, 31 Aug 2016 17:30:07 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 120D7263FF; Wed, 31 Aug 2016 19:30:04 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUrI_n9MFJv3; Wed, 31 Aug 2016 19:30:03 +0200 (CEST) Received: from [192.168.10.10] (asus [192.168.10.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id E8292263FD; Wed, 31 Aug 2016 19:30:02 +0200 (CEST) Subject: Re: ZFS + NFS + multiple hosts/mount options ..? To: "Brandon J. Wandersee" References: <20160829211001.GI1779@mordor.lan> <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org> <86zinsswzq.fsf@WorkBox.Home> Cc: lev@FreeBSD.org, Julien Cigar , freebsd-fs@freebsd.org From: Willem Jan Withagen Message-ID: <17d071ba-2692-993c-864b-3fad98fd5526@digiware.nl> Date: Wed, 31 Aug 2016 19:30:01 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <86zinsswzq.fsf@WorkBox.Home> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 17:30:07 -0000 On 31-8-2016 18:51, Brandon J. Wandersee wrote: > > Willem Jan Withagen writes: > >>> There is one BIG problem: deep ZFS hierarchies. If I need to export 100 >>> FSes (100 users' home directories, for example) in one ZFS tree to 4 >>> networks (2xIPv4, 2xIPv6) I need to add 400 (!!!) lines to /etc/exports >>> by hands. All these lines will be virtually the same, and good luck to >>> maintain this mess. >>> >>> If "sharenfs" supports multiple hosts/networks, I need to set this >>> property ONCE (on zpool/home, parent of all FSes in question) and IT'S >>> ALL! And if I need to change same options, I need to change it ONCE and >>> re-export ZFS. >>> >>> Unfortunately, it is NOT enough to export parent FS :( >> >> Hi Lev, >> >> I agree with you >> >> More or less the arguments I had at that time. >> (though I don't have that many FSes.) >> >> And I gave up. Perhaps that tells more about me than anything else. >> The discussion I tried to have was cut short with the argument that it >> would not go in because upstream would not like it, or would not want >> in the version I submitted. >> >> But please do feel free and get something in that would please more. > > Has a script that recurses through a directory tree and adds valid > entries to the exports file been considered as a viable option? > "sharenfs=" just adds syntactically valid entries to /etc/zfs/exports; > NFS does the rest. > > There are probably a number of reasons that making "sharenfs" more > complicated isn't in the cards. I suspect "upstream won't like it" may > just be short-hand for "Nobody wants to do the work to implement and > maintain a feature across multiple operating systems that can be > implemented by the tiny fraction of users who want it with the tools > already available to them." But besides that, yes, being able to set an > option once at a root point and have that option affect all descendant > filesystems appears simple and easy, because you're dealing with one > very simple use case with predictable results. That simplicity and > predictability immediately break down once you start changing options > for individual descendant filesystems, which someone would inevitably > want to do. ("If it's possible to implement this, then why not that? > That's simple enough, right?") Or what about people who only want to > export 60 of the 100 child filesystems? They still have to either set > the property manually on all their filesystems, or create new dataset > trees to separate shared from unshared filesystems. Is implementing > inheritance for "sharenfs" really going to relieve enough tedium of > enough users to make it worthwhile? And then there's the fact that NFS > by its nature does not cross filesystem boundaries, which ZFS > inheritance would do if the "sharenfs" property were inherited, making > ZFS sharing unpredictable to someone used to managing complicated NFS > groups on anything other than ZFS. At that point it's become easier to > manage lots of shares and harder to manage only a few shares > exclusively. In such cases, is it really easier *not* to write an > exports file by hand? That's what you're getting, after all: whether you > copy lines in a text file or enter `zfs set sharenfs=` 50 times, you're > still typing out the name of filesystem 50 times while everything else > is automated... > > I'm not saying none of this can be implemented, or that the developers > shouldn't be sympathetic to users. Just that a small group's convenience > doesn't trump the needs of a larger group, and that the developers > probably have more reasons not to bother with this than mere laziness or > a lack of compassion. not a bad idea at all. Once you decide to go beyond sharing code with openZFS lots of things are possible... And then you can also start abusing the fact that you now can add your own attributes to the pools and volumes... Like what zfstools is doing for the backup scenarios. Than whack a script over it to fill /etc/exports. --WjW From owner-freebsd-fs@freebsd.org Thu Sep 1 13:06:31 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68AC5BCB99A for ; Thu, 1 Sep 2016 13:06:31 +0000 (UTC) (envelope-from julien@perdition.city) Received: from relay-b02.edpnet.be (relay-b02.edpnet.be [212.71.1.222]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "edpnet.email", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0255AAD9 for ; Thu, 1 Sep 2016 13:06:30 +0000 (UTC) (envelope-from julien@perdition.city) X-ASG-Debug-ID: 1472735179-0a7b8d2a6d2a07d20001-3nHGF7 Received: from mordor.lan (77.109.124.121.adsl.dyn.edpnet.net [77.109.124.121]) by relay-b02.edpnet.be with ESMTP id 20eOD3yMFXspEwVv (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 01 Sep 2016 15:06:20 +0200 (CEST) X-Barracuda-Envelope-From: julien@perdition.city X-Barracuda-Effective-Source-IP: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Apparent-Source-IP: 77.109.124.121 Date: Thu, 1 Sep 2016 15:06:19 +0200 From: Julien Cigar To: Borja Marcos Cc: linda@kateley.com, freebsd-fs@freebsd.org, juergen.gotteswinter@internetx.com Subject: Re: HAST + ZFS + NFS + CARP Message-ID: <20160901130618.GT1779@mordor.lan> X-ASG-Orig-Subj: Re: HAST + ZFS + NFS + CARP References: <472bc879-977f-8c4c-c91a-84cc61efcd86@internetx.com> <20160817085413.GE22506@mordor.lan> <465bdec5-45b7-8a1d-d580-329ab6d4881b@internetx.com> <20160817095222.GG22506@mordor.lan> <52d5b687-1351-9ec5-7b67-bfa0be1c8415@kateley.com> <92F4BE3D-E4C1-4E5C-B631-D8F124988A83@gmail.com> <6b866b6e-1ab3-bcc5-151b-653e401742bd@kateley.com> <7468cc18-85e8-3765-2b2b-a93ef73ca05a@internetx.com> <4c34cbf9-84b5-5d42-e0b4-bf18aa1ef9a7@kateley.com> <3F002B89-353E-41CE-8ACF-B34D7D774BCC@sarenet.es> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8KmZJhJMEENkOiL3" Content-Disposition: inline In-Reply-To: <3F002B89-353E-41CE-8ACF-B34D7D774BCC@sarenet.es> User-Agent: Mutt/1.6.1 (2016-04-27) X-Barracuda-Connect: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Start-Time: 1472735179 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://212.71.1.222:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 1501 X-Virus-Scanned: by bsmtpd at edpnet.be X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.5000 1.0000 0.7500 X-Barracuda-Spam-Score: 0.75 X-Barracuda-Spam-Status: No, SCORE=0.75 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.32528 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 13:06:31 -0000 --8KmZJhJMEENkOiL3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable back on this .. :) So.. I finally had the time to test my setup here for a week and I haven't managed to corrupt the zpool with the following failover (SLAVE->MASTER) script https://gist.github.com/silenius/ceb37c392763db3c5a55033d97e3739a I tested with heavy writes, plug the power cable off, power on both machines at the same time, etc .. I'd really appreciate some feedbacks on my failover script above (things I wouldn't have thought, etc)=20 (The SLAVE (old MASTER) -> MASTER (old SLAVE) failover is done manually) Thanks! Julien On Fri, Aug 19, 2016 at 10:49:20AM +0200, Borja Marcos wrote: >=20 > > On 18 Aug 2016, at 19:19, Linda Kateley wrote: > >> here: running nexenta ha setup since several years with one catastroph= ic > >> failure due to split brain > > Just trying to say I don't see projects ongoing.. just at beginning >=20 > I saw consultants near the T=C3=A4nnhauser Gate=E2=80=A6 >=20 > Some kind of feedback loop is terrific, really! ;) >=20 >=20 > Borja. >=20 > _______________________________________________ > 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" --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --8KmZJhJMEENkOiL3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCgAGBQJXyCfHAAoJELK7NxCiBCPA/ooP/0xcVnajT7ABDsPxm4OAdvWi otscUnhFmoE9JpUGGPqdvLwqgqkODD56mlfVdu+AR3rjKzQ6sxtBg2Jy53MbHuGG rY7KUBZODBaIS91CjVaZuZ1u4QYwBUOons7klla+U7u0WOuJ/oTKuGR92BPw/Ni5 6waqtAR+vKiYXicebDi4Rd567xyw5JBg6mplzp8/RweXaOm9q8fEjOMhbJzjXBV4 qCA83rcQq6a2Uamg9gZnG7w2iqsophumDx3tLLLwB2xkF1rAMZf77v2+p6fSGVwG yec7bLz5q4nf5SJzQO8o4weCXpOv2Yc2mGJSEDLKIWugQHhxtqd0YfYAoDS79I0c XEuIwL3SzTrvTxp3C4iKqj9D5KIUvHDfoYPXcNPY9so5Vy2PodyJ+LD+B0oKY/q0 8PeEYOa69454YzhSdV29YlmyUw3ZFToDs7Cc36QORw40rj3/Q19yNlVhFV4TNqi6 TrMl+9d8y2T0YXmOk7gpy802pbd5GhdQhx89BjVdaVI2eaBf1AfoR+oRBzsdP5Iv Yc+OvuDe/N9pm0J1qh85WWKo/Lk7mBLhmLRXn4JPQXtLvgH51cJi4Ab2m/hEUWN2 oB6ZEUtgiW1dtKIG/aGiQ9FkzIi/wq8N+mWD1fexqzwF0NN7DJXd561BHmvThlO4 c0msgOcYkI/0eeNmiMxw =pFDm -----END PGP SIGNATURE----- --8KmZJhJMEENkOiL3-- From owner-freebsd-fs@freebsd.org Thu Sep 1 13:14:04 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 635CDBCBC78 for ; Thu, 1 Sep 2016 13:14:04 +0000 (UTC) (envelope-from juergen.gotteswinter@internetx.com) Received: from mx1.internetx.com (mx1.internetx.com [62.116.129.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2585CF1F for ; Thu, 1 Sep 2016 13:14:04 +0000 (UTC) (envelope-from juergen.gotteswinter@internetx.com) Received: from localhost (localhost [127.0.0.1]) by mx1.internetx.com (Postfix) with ESMTP id 5C20845FC0FF; Thu, 1 Sep 2016 15:13:56 +0200 (CEST) X-Virus-Scanned: InterNetX GmbH amavisd-new at ix-mailer.internetx.de Received: from mx1.internetx.com ([62.116.129.39]) by localhost (ix-mailer.internetx.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNwRHPvaHjOK; Thu, 1 Sep 2016 15:13:49 +0200 (CEST) Received: from [192.168.100.26] (pizza.internetx.de [62.116.129.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.internetx.com (Postfix) with ESMTPSA id A2A604C4C70C; Thu, 1 Sep 2016 15:13:49 +0200 (CEST) Reply-To: juergen.gotteswinter@internetx.com Subject: Re: HAST + ZFS + NFS + CARP References: <472bc879-977f-8c4c-c91a-84cc61efcd86@internetx.com> <20160817085413.GE22506@mordor.lan> <465bdec5-45b7-8a1d-d580-329ab6d4881b@internetx.com> <20160817095222.GG22506@mordor.lan> <52d5b687-1351-9ec5-7b67-bfa0be1c8415@kateley.com> <92F4BE3D-E4C1-4E5C-B631-D8F124988A83@gmail.com> <6b866b6e-1ab3-bcc5-151b-653e401742bd@kateley.com> <7468cc18-85e8-3765-2b2b-a93ef73ca05a@internetx.com> <4c34cbf9-84b5-5d42-e0b4-bf18aa1ef9a7@kateley.com> <3F002B89-353E-41CE-8ACF-B34D7D774BCC@sarenet.es> <20160901130618.GT1779@mordor.lan> To: Julien Cigar , Borja Marcos Cc: freebsd-fs@freebsd.org From: InterNetX - Juergen Gotteswinter Organization: InterNetX GmbH Message-ID: <43390124-1abd-7d3b-3785-fd99f90ea5f9@internetx.com> Date: Thu, 1 Sep 2016 15:13:47 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160901130618.GT1779@mordor.lan> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 13:14:04 -0000 do i get this right, that the pool runs on top of iscsi luns? Am 01.09.2016 um 15:06 schrieb Julien Cigar: > back on this .. :) > > So.. I finally had the time to test my setup here for a week and I > haven't managed to corrupt the zpool with the following failover > (SLAVE->MASTER) script > https://gist.github.com/silenius/ceb37c392763db3c5a55033d97e3739a > > I tested with heavy writes, plug the power cable off, power on both > machines at the same time, etc .. > > I'd really appreciate some feedbacks on my failover script above (things > I wouldn't have thought, etc) > > (The SLAVE (old MASTER) -> MASTER (old SLAVE) failover is done manually) > > Thanks! > Julien > > On Fri, Aug 19, 2016 at 10:49:20AM +0200, Borja Marcos wrote: >> >>> On 18 Aug 2016, at 19:19, Linda Kateley wrote: >>>> here: running nexenta ha setup since several years with one catastrophic >>>> failure due to split brain >>> Just trying to say I don't see projects ongoing.. just at beginning >> >> I saw consultants near the Tännhauser Gate… >> >> Some kind of feedback loop is terrific, really! ;) >> >> >> Borja. >> >> _______________________________________________ >> 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 Thu Sep 1 13:18:46 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18926BCBF55 for ; Thu, 1 Sep 2016 13:18:46 +0000 (UTC) (envelope-from julien@perdition.city) Received: from relay-b02.edpnet.be (relay-b02.edpnet.be [212.71.1.222]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "edpnet.email", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3EDE831 for ; Thu, 1 Sep 2016 13:18:45 +0000 (UTC) (envelope-from julien@perdition.city) X-ASG-Debug-ID: 1472735920-0a7b8d2599192c430001-3nHGF7 Received: from mordor.lan (77.109.124.121.adsl.dyn.edpnet.net [77.109.124.121]) by relay-b02.edpnet.be with ESMTP id s15DvHsoDoh2eB0Z (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 01 Sep 2016 15:18:42 +0200 (CEST) X-Barracuda-Envelope-From: julien@perdition.city X-Barracuda-Effective-Source-IP: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Apparent-Source-IP: 77.109.124.121 Date: Thu, 1 Sep 2016 15:18:40 +0200 From: Julien Cigar To: InterNetX - Juergen Gotteswinter Cc: Borja Marcos , freebsd-fs@freebsd.org Subject: Re: HAST + ZFS + NFS + CARP Message-ID: <20160901131840.GU1779@mordor.lan> X-ASG-Orig-Subj: Re: HAST + ZFS + NFS + CARP References: <465bdec5-45b7-8a1d-d580-329ab6d4881b@internetx.com> <20160817095222.GG22506@mordor.lan> <52d5b687-1351-9ec5-7b67-bfa0be1c8415@kateley.com> <92F4BE3D-E4C1-4E5C-B631-D8F124988A83@gmail.com> <6b866b6e-1ab3-bcc5-151b-653e401742bd@kateley.com> <7468cc18-85e8-3765-2b2b-a93ef73ca05a@internetx.com> <4c34cbf9-84b5-5d42-e0b4-bf18aa1ef9a7@kateley.com> <3F002B89-353E-41CE-8ACF-B34D7D774BCC@sarenet.es> <20160901130618.GT1779@mordor.lan> <43390124-1abd-7d3b-3785-fd99f90ea5f9@internetx.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JNs4m2JFMNhdiK2v" Content-Disposition: inline In-Reply-To: <43390124-1abd-7d3b-3785-fd99f90ea5f9@internetx.com> User-Agent: Mutt/1.6.1 (2016-04-27) X-Barracuda-Connect: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Start-Time: 1472735920 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://212.71.1.222:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 1955 X-Virus-Scanned: by bsmtpd at edpnet.be X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.5000 1.0000 0.0100 X-Barracuda-Spam-Score: 0.01 X-Barracuda-Spam-Status: No, SCORE=0.01 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.32528 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 13:18:46 -0000 --JNs4m2JFMNhdiK2v Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 01, 2016 at 03:13:47PM +0200, InterNetX - Juergen Gotteswinter = wrote: > do i get this right, that the pool runs on top of iscsi luns? yes, it's a zpool mirror over 4 disks (2 locals, 2 iSCSI): https://gist.github.com/silenius/43ab0a099957a1d075db2f4c0c74339b >=20 > Am 01.09.2016 um 15:06 schrieb Julien Cigar: > > back on this .. :) > >=20 > > So.. I finally had the time to test my setup here for a week and I > > haven't managed to corrupt the zpool with the following failover > > (SLAVE->MASTER) script > > https://gist.github.com/silenius/ceb37c392763db3c5a55033d97e3739a > >=20 > > I tested with heavy writes, plug the power cable off, power on both > > machines at the same time, etc .. > >=20 > > I'd really appreciate some feedbacks on my failover script above (things > > I wouldn't have thought, etc)=20 > >=20 > > (The SLAVE (old MASTER) -> MASTER (old SLAVE) failover is done manually) > >=20 > > Thanks! > > Julien > >=20 > > On Fri, Aug 19, 2016 at 10:49:20AM +0200, Borja Marcos wrote: > >> > >>> On 18 Aug 2016, at 19:19, Linda Kateley wrote: > >>>> here: running nexenta ha setup since several years with one catastro= phic > >>>> failure due to split brain > >>> Just trying to say I don't see projects ongoing.. just at beginning > >> > >> I saw consultants near the T=C3=A4nnhauser Gate=E2=80=A6 > >> > >> Some kind of feedback loop is terrific, really! ;) > >> > >> > >> Borja. > >> > >> _______________________________________________ > >> 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" > >=20 --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --JNs4m2JFMNhdiK2v Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCgAGBQJXyCqtAAoJELK7NxCiBCPAAl0P/j7C6nIoHfruxazl3+ukr7DI 1vm6N7M4A8P3Aw+3rrZD42dj4LBrOukZ3QQCJ1L0q4SYVfC30qkfEteqmUu0kz4v eEA7mkIraBJyENNsHEx139GgPeH6iJgr/VAK4fxH5+el0g0FKreTe3Z6e0A9ajFC vw4hX6H69Del2ONaf//NHPLh18MdSS8F2oivCptxsreTWsV7FWLFuiceBWA+i37A NqUo3VgOibqi3PYJL+tHu7+vTaCkbgGp6d0gZcIoSVdL/eKEwqAiQWPfuyyM0y1U b460dgZAiL3rDxlJwYO6RZzkPn+Zu6JqAThznHNWeHyC/WpR7ujBXfUS+2r8ZbDC P+KaIkmEO8C5SnHE07zTjCbkAV8GYypjwzRysfOihk5qTw0cdS5G1HW4Q6GWEdVR NvhnLQ4BCkPk1beIsW3ff6rtIztPGNdiC01Gvts81Z0xG9Sz8/kZiqnPy/9ocEF/ TJL8T2kQfyCYpQ+6DNIMD0diDlTqSNz1ID0ELQ5ZIDkyqyl/mwf7UDpb65zfQ2t0 QAoXM+SRo9eEmtk8gVr+DeEusqEoNIUF6Ln1VryBzNPvKn5rIqEeOoM3T5QeJRi0 /cV3CFcWr1fqhzvmiUHZTa7sD6nwzcqPwmZcsAFsStTISNER/Olby4Q4RAVqRD29 2QpvnZneJ9IBSl2HGzQj =TGKu -----END PGP SIGNATURE----- --JNs4m2JFMNhdiK2v-- From owner-freebsd-fs@freebsd.org Thu Sep 1 21:37:36 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80342BCBE28 for ; Thu, 1 Sep 2016 21:37:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5756B1DC for ; Thu, 1 Sep 2016 21:37:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u81LbZJ7091220 for ; Thu, 1 Sep 2016 21:37:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212318] sysutils/fusefs-libs: fails to unmount due to a uniq dev node Date: Thu, 01 Sep 2016 21:37:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ben.rubson@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name Message-ID: 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.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 21:37:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212318 Bug ID: 212318 Summary: sysutils/fusefs-libs: fails to unmount due to a uniq dev node Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: ben.rubson@gmail.com CC: brendan+freebsd@bbqsrc.net, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org Flags: maintainer-feedback?(brendan+freebsd@bbqsrc.net) Hello, I found a bug with fusefs. In function fuse_unmount_compat22, the following command is used to find out the device to unmount : /usr/bin/fstat /dev/fuse* Here is its output with FreeBSD 11.0-RC2 : # fstat /dev/fuse* USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME user1 encfs 15513 4 /dev 60 crw-rw---- fuse rw /dev/= fuse user2 encfs 15504 4 /dev 60 crw-rw---- fuse rw /dev/= fuse user3 encfs 15456 4 /dev 60 crw-rw---- fuse rw /dev/= fuse user4 encfs 15431 4 /dev 60 crw-rw---- fuse rw /dev/= fuse As you can see all users use the same dev node /dev/fuse. So when unmounting, user3 will get for example the following message : umount: unmount of /home/user2/encfs failed: Operation not permitted I'm not sure where is the issue, if we should expect a uniq dev node per mounted FS, or if the unmount command is to correct. Many thanks for your help ! Ben --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Fri Sep 2 07:37:37 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6DFCBCC583 for ; Fri, 2 Sep 2016 07:37:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B68BAD0E for ; Fri, 2 Sep 2016 07:37:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u827bbgt089466 for ; Fri, 2 Sep 2016 07:37:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212323] tests/sys/acl/01:main fails due to changes in NFSv4 ACL behavior Date: Fri, 02 Sep 2016 07:37:37 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 07:37:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212323 Ngie Cooper changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mav@FreeBSD.org, | |ngie@FreeBSD.org, | |trasz@FreeBSD.org Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Sep 2 07:37:53 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B265FBCC5F1 for ; Fri, 2 Sep 2016 07:37:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A204CDE4 for ; Fri, 2 Sep 2016 07:37:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u827br2i089804 for ; Fri, 2 Sep 2016 07:37:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212323] tests/sys/acl/01:main fails due to changes in NFSv4 ACL behavior on ^/head Date: Fri, 02 Sep 2016 07:37:53 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc 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.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 07:37:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212323 Ngie Cooper changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|tests/sys/acl/01:main fails |tests/sys/acl/01:main fails |due to changes in NFSv4 ACL |due to changes in NFSv4 ACL |behavior |behavior on ^/head --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Sep 2 16:06:48 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87574BCD82F for ; Fri, 2 Sep 2016 16:06:48 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 58CE5791 for ; Fri, 2 Sep 2016 16:06:48 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: by mail-it0-x230.google.com with SMTP id e124so45385605ith.0 for ; Fri, 02 Sep 2016 09:06:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kateley-com.20150623.gappssmtp.com; s=20150623; h=reply-to:from:organization:to:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=PbOF7vreYwNuVG0tht9pj6pMdo57J+pHA8ySIZ5BOkA=; b=ToFN0ZT/Icwshj/glxyxzGobyWPQi3i1GJn2BWUP2IELZVay7+NqPek0OLcegpGXR7 fAYWm4rKynCJyHZ2O0VTdhTmk4+nGVv9X3I+560tLDMEbg4qzfTBE9jg9DwuUkNn6X8d k20V1r0jFllcc5Ir78Bud2adn0HA/evka+YBWQDubYpexkjwotfLGYeQQlx3NO20uLkI Zz1H7t7tWxp6A6J/tigw46u+WJ4fTpaTY++xfUgRydJmkiJuumldYkiCBU7jEUEZihx9 CU93EXHrQMiTq1OKaiNigHM0ToJOhnQ6Ey4bFVQM4teZLcjT979NTeOTQfRs+erTWoLI YoDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:from:organization:to:subject:message-id :date:user-agent:mime-version:content-transfer-encoding; bh=PbOF7vreYwNuVG0tht9pj6pMdo57J+pHA8ySIZ5BOkA=; b=QI/6jN+c/W+D6Z80VjnV0JYLzMfx5NNyyihGEMmHQOOjbJvli3ODxsLogCdXKOr/vy QqXiIRld7H/QMWqZgrBFPRAKA6q58uhH36UgwnHQs0MHfUnUz2yz4EH3PM8c1849mEvD EKpJxzbS0EiB3+7jNd34fo4mvyT4RugFadIWGEg/ed8Zk9c72RpIjq5wTnLOfmQQ/8Mb HuNk4SHyxvs8IXFJP7s5AtdHl9b4Yf+GLWX1u8RxZYkMtRkDUifVTOUt/XMnxxvU62d/ 5EMIZFu092Egdn9AXQnjHUJxoxt4qhI3+sYnCs4mPLAzgwNuYV6bmTsJ9aVAEHWTLLbQ Rb8g== X-Gm-Message-State: AE9vXwNWkqyhQWdQcBktsjWYQrR0EHlAKBmkfhfo0AxswALb8Z3GRAv5neJXwJminxTSNw== X-Received: by 10.36.237.6 with SMTP id r6mr5657182ith.62.1472832407363; Fri, 02 Sep 2016 09:06:47 -0700 (PDT) Received: from Kateleyco-iMac.local (c-50-188-36-30.hsd1.mn.comcast.net. [50.188.36.30]) by smtp.googlemail.com with ESMTPSA id 194sm2823781itu.4.2016.09.02.09.06.46 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Sep 2016 09:06:46 -0700 (PDT) Reply-To: linda@kateley.com From: Linda Kateley Organization: Kateley Company To: FreeBSD Filesystems Subject: phantom snapshots Message-ID: <58816ff0-3ab2-cbae-3d50-c4d5e89d9773@kateley.com> Date: Fri, 2 Sep 2016 11:06:46 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 16:06:48 -0000 So I think I have isolated this to a phantom snapshot. At the end of this zpool status although the names change everytime I run scrub, it show unrecoverable error of files in a snapshot that doesn't exit. It also has in that zfs dataset it has a .zfs directory with a name of old snaps. Anyone know how to view or clear these phantom snaps? I tried to remove the files in the snapshot directory, but it is read-only. Ideas? Linda pool: pool state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Fri Sep 2 10:42:48 2016 46.8T scanned out of 144T at 2.48G/s, 11h11m to go 46.5G resilvered, 32.40% done config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 12 raidz3-0 ONLINE 0 0 0 gptid/ac108605-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/ac591d4e-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/ac92fd0d-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/accd3076-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/ad067e97-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/ad46cbee-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/ad91ba17-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/adcbdd0a-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/ae07dc0d-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/ae494d10-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/ae93a3a5-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 raidz3-1 ONLINE 0 0 0 gptid/12f6a4c5-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/511ea1f9-1932-11e6-9b1e-0cc47a599098 ONLINE 0 0 0 gptid/14436fcf-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/14f50aa3-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/159b5654-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/163d682b-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/16ee624e-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/1799dde3-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/184c2ea4-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/18f51c30-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 gptid/19a861ea-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 raidz3-2 ONLINE 0 0 24 gptid/5f80fc42-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/60369e0f-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/60e8234a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/61a235f2-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/62580471-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/6316a38a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/63d4bce8-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/ebfc2b99-6893-11e6-9b09-0cc47a599098 ONLINE 0 0 0 (resilvering) gptid/654f143a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/66236b33-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/66eda3f6-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 raidz3-3 ONLINE 0 0 24 gptid/c77a9da9-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/c83e100e-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/c8fd9ced-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/c9bb21ba-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/ca7a48db-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/cb422329-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/cbfe4c21-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/ccc43528-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/cd93a34c-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/ce622f51-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 gptid/cf2591d3-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 cache gptid/aedd3872-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 gptid/af559c10-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: <0x597>:<0x1246> <0x597>:<0x1249> <0x597>:<0x125e> <0x597>:<0x1261> <0x597>:<0x127d> <0x597>:<0x1280> <0x599>:<0xe2c> <0x599>:<0xe2f> <0x599>:<0xe40> <0x599>:<0xe43> <0x599>:<0xe59> <0x599>:<0xe62> <0x5bc>:<0x2ad06> <0x5bc>:<0x2aef3> <0x5bc>:<0x2aef6> pool/.system@auto-20160720.2300-2d:<0x0> <0x5dc>:<0x397411> <0x5dc>:<0x397414> <0x5dc>:<0x38ee26> <0x5dc>:<0x38ee29> <0x5dc>:<0x38ee2c> <0x5dc>:<0x45b2e> <0x5dc>:<0x38ee2f> <0x5dc>:<0x38ee32> <0x5dc>:<0x394e58> <0x5dc>:<0x394e5b> <0x5dc>:<0x394e5e> <0x5dc>:<0x394e61> <0x5dc>:<0x394e64> <0x5dc>:<0x394e67> <0x5dc>:<0x394e6a> <0x5dc>:<0x397285> From owner-freebsd-fs@freebsd.org Fri Sep 2 16:15:27 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 201B9BCDAD9 for ; Fri, 2 Sep 2016 16:15:27 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA705D50 for ; Fri, 2 Sep 2016 16:15:26 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id i138so3464758wmf.3 for ; Fri, 02 Sep 2016 09:15:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=AkKCLTVrrU5MkCMTcm58nDounMkK/QY1XHRwnxbxjlc=; b=cRowdlUR1wd59o2jg7T5NH/7PYvUxm4qFhLne75O0TglRIT+lg4UKpRTYiN+O+FGrX BwSNOWx6FbWx2hwny4aZ4C4pLmAaU4ifpp30BASBb/s+AHYVYSp/IsXY+rSaPe2Jhe5k FYNqnYKAYKG+68nDJpZFilv6smIxutTwdwGzTR2TFskwfdIZAJGeRM1m3EuFrGPNEzec IMsVmFDSv3aV97CX2enyS1fCnec9aUaLJVD3itaOR2mZktRZtB+itNsh/qVvCPuf0WrV rWvq74Hkmm1OsynXPO4a0oXsBgpQ2kIAFJebaXobvVjkM2FonOAv0T91iWVcnjihXXDd ikWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=AkKCLTVrrU5MkCMTcm58nDounMkK/QY1XHRwnxbxjlc=; b=WiyzeZ8Zkp1JWKall4hnn6l8RHSdheuLDBUVkpxobtbVLRgu30vLCO28bSxUlqzwyd xESSDEvuUqYQcebFMkzpIh3VcE9TYOu7bjfxo5TEK9CPQGC5gUzzXum4vmU8h7YeBq0s fjuIObLLeoYJCXwaJypwMQrBq7iuxZEWtFqQwGe/8A1Z97QxI6548UfwFTLSuGCjsh0+ jvpbU5SG66CS1gy63xctYOofnamtGFca4AGMq3namSxBBRCBcpJcikJPMRHJ8qWfBTDM QIP+ON3vdMRWR64gevsYjmo+jVt4eZPTlrcqGkO5VrLlWyS9k2biXhLEbY6GNuia83vC Tdcg== X-Gm-Message-State: AE9vXwOmpTppXhOSmrsYocm6G7MdQB8P9DMAhyELYTZt+6zQkbv2AJ6RhssXZ0t4ss9fYQ== X-Received: by 10.28.158.142 with SMTP id h136mr3954001wme.10.1472832924795; Fri, 02 Sep 2016 09:15:24 -0700 (PDT) Received: from macbook-air-de-benjamin-1.home (ANice-651-1-362-61.w83-201.abo.wanadoo.fr. [83.201.110.61]) by smtp.gmail.com with ESMTPSA id kq2sm11137776wjc.41.2016.09.02.09.15.23 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 02 Sep 2016 09:15:24 -0700 (PDT) From: Ben RUBSON Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: [ZFS] refquota is very slow ! Message-Id: Date: Fri, 2 Sep 2016 18:15:23 +0200 To: FreeBSD FS Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 16:15:27 -0000 Hello, When I set refquota on a dataset, write IOs are done very sloooowwwly = some MB below the limit. And I can't manage to reach it, dd (used to create a file to fulfil = space) seems to stall. No problem however with quota, dd goes to the end and returns with : "Disc quota exceeded" Any clue ? I would have been interested to use refquota to avoid impacting users = with snapshots'fs space, but this option is quite unusable as is. Thank you very much ! Ben From owner-freebsd-fs@freebsd.org Fri Sep 2 18:03:36 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5AF8BCD1DF for ; Fri, 2 Sep 2016 18:03:36 +0000 (UTC) (envelope-from Shiva.Bhanujan@Quorum.net) Received: from mail.quorumlabs.com (mail.quorum.net [64.74.133.216]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.quorumlabs.com", Issuer "Go Daddy Secure Certification Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D5527FD3 for ; Fri, 2 Sep 2016 18:03:35 +0000 (UTC) (envelope-from Shiva.Bhanujan@Quorum.net) Received: from QLEXC01.Quorum.local ([fe80::fcc3:c03f:ab83:3cfc]) by QLEXC01.Quorum.local ([fe80::fcc3:c03f:ab83:3cfc%14]) with mapi id 14.02.0318.001; Fri, 2 Sep 2016 11:02:25 -0700 From: Shiva Bhanujan To: "freebsd-fs@freebsd.org" Subject: dnode_evict_dbufs leads to panic Thread-Topic: dnode_evict_dbufs leads to panic Thread-Index: AdIFQ1vC9nt9yylZSTu2+SkzNbv8Zg== Date: Fri, 2 Sep 2016 18:02:24 +0000 Message-ID: <3A5A10BE32AC9E45B4A22F89FC90EC07013044B954@QLEXC01.Quorum.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.20.7.61] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 18:03:37 -0000 Hello, We're running FreeBSD 10.2-RELEASE-p20, as a VM (HVM) on XenServer 6.5. It= serves as a backend storage system, and exports ZFS via NFS. After runnin= g for a day and a half, we notice the FreeBSD VM getting hung, or has crash= ed. Looking at the following traceback, I have found this issue being reported = multiple times. #1 0xffffffff8093ce62 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:451 #2 0xffffffff8093d245 in vpanic (fmt=3D, ap=3D) at /usr/src/sys/kern/kern_shutdown.c:758 #3 0xffffffff8093d0d3 in panic (fmt=3D0x0) at /usr/src/sys/kern/kern_shutdown.c:687 #4 0xffffffff80d3f22b in trap_fatal (frame=3D, eva=3D) at /usr/src/sys/amd64/amd64/trap.c:851 #5 0xffffffff80d3f52d in trap_pfault (frame=3D0xfffffe032937f660, usermode=3D) at /usr/src/sys/amd64/amd64/trap.c:67= 4 #6 0xffffffff80d3ebca in trap (frame=3D0xfffffe032937f660) at /usr/src/sys/amd64/amd64/trap.c:440 #7 0xffffffff80d24f42 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff8094550b in _sx_xlock_hard (sx=3D0xfffff800b3e35918, tid=3D18446735282677829632, opts=3D, file=3D0xfffff8012dad5000 "", line=3D49749) at /usr/src/sys/kern/kern_s= x.c:568 #9 0xffffffff8094501d in _sx_xlock (sx=3D0xfffff8012dad5000, opts=3D766332= 928, file=3D, line=3D766332928) at sx.h:152 #10 0xffffffff819ca67d in dnode_evict_dbufs (dn=3D0xfffff8008c4728d0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/f= s/zfs/dnode_sync.c:416 #11 0xffffffff819c151b in dmu_objset_evict_dbufs (os=3D) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/f= s/zfs/dmu_objset.c:620 #12 0xffffffff81a49ff1 in zfsvfs_teardown (zfsvfs=3D0xfffff800adb6e000, unmounting=3D) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/f= s/zfs/zfs_vfsops.c:1915 #13 0xffffffff81a4b965 in zfs_umount (vfsp=3D0xfffff8007035e330, fflag=3D) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/f= s/zfs/zfs_vfsops.c:2009 #14 0xffffffff809d951f in dounmount (mp=3D0xfffff8007035e330, flags=3D52428= 8, td=3D0xfffff8012dad5000) at /usr/src/sys/kern/vfs_mount.c:1316 #15 0xffffffff809d9026 in sys_unmount (td=3D0xfffff8012dad5000, uap=3D0xfffffe032937fb80) at /usr/src/sys/kern/vfs_mount.c:1208 #16 0xffffffff80d3fb47 in amd64_syscall (td=3D0xfffff8012dad5000, traced=3D= 0) at subr_syscall.c:134 However, I haven't been able to find a definite answer as to how this is to= be fixed. Can anybody provide some guidance if this is something that has= a fix in a subsequent FreeBSD release? If there is more information that = is needed, please do let me know? I can send the core file if needed, have= n't attached it here so as not to spam. Please let me know if I should pro= vide it? Regards, Shiva From owner-freebsd-fs@freebsd.org Fri Sep 2 19:24:55 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37A2DBCDAF5 for ; Fri, 2 Sep 2016 19:24:55 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) by mx1.freebsd.org (Postfix) with ESMTP id 9CBDCBA1 for ; Fri, 2 Sep 2016 19:24:54 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.160] (probe.42.lan [172.29.1.160]) by limbo.b1t.name (Postfix) with ESMTPSA id B44FEF6 for ; Fri, 2 Sep 2016 22:24:43 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=b1t.name; s=mail; t=1472844284; bh=FDy5nOIDx6OPETvsjRX3YYVRHuJs0uZ6gSAkwSdxy0g=; h=Subject:To:References:From:Date:In-Reply-To; b=7y+1uGvef/0nn+2ui6HsCmwityq3uYllGNt6IsoqFZMMD5nmQzbobgjdFhHI65te/ hh8qxxy/B+ZE5tSTijQBEznEoip46oLA/djZiOCZcKQzV6JOqx0HVpnCeZXMRn+Wpo 9lGEcLqmHu6ojfptuUq54UNSF6O7RucN64Jd4ADM= Subject: Re: phantom snapshots To: FreeBSD Filesystems References: <58816ff0-3ab2-cbae-3d50-c4d5e89d9773@kateley.com> From: Volodymyr Kostyrko Message-ID: <57C9D1FB.6040904@b1t.name> Date: Fri, 2 Sep 2016 22:24:43 +0300 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <58816ff0-3ab2-cbae-3d50-c4d5e89d9773@kateley.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 19:24:55 -0000 Linda Kateley wrote: > So I think I have isolated this to a phantom snapshot. At the end of > this zpool status although the names change everytime I run scrub, it > show unrecoverable error of files in a snapshot that doesn't exit. > > It also has in that zfs dataset it has a .zfs directory with a name of > old snaps. > > Anyone know how to view or clear these phantom snaps? I tried to remove > the files in the snapshot directory, but it is read-only. This looks like pointers to files that were already deleted/purged. I once faced this errors but that was on bad controller, I don't think this can be caused by bad memory/errors. When that happened I scrubbed pool, removed all files noted, cleaned zpool errors (they are persistent, even the file was removed and snapshots doen't exist they are still shown) and scrubbed the pool again. > > Ideas? > > Linda > > > pool: pool > state: ONLINE > status: One or more devices is currently being resilvered. The pool will > continue to function, possibly in a degraded state. > action: Wait for the resilver to complete. > scan: resilver in progress since Fri Sep 2 10:42:48 2016 > 46.8T scanned out of 144T at 2.48G/s, 11h11m to go > 46.5G resilvered, 32.40% done > config: > > NAME STATE READ > WRITE CKSUM > pool ONLINE 0 0 12 > raidz3-0 ONLINE 0 0 0 > gptid/ac108605-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/ac591d4e-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/ac92fd0d-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/accd3076-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/ad067e97-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/ad46cbee-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/ad91ba17-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/adcbdd0a-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/ae07dc0d-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/ae494d10-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/ae93a3a5-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > raidz3-1 ONLINE 0 0 0 > gptid/12f6a4c5-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/511ea1f9-1932-11e6-9b1e-0cc47a599098 ONLINE 0 0 0 > gptid/14436fcf-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/14f50aa3-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/159b5654-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/163d682b-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/16ee624e-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/1799dde3-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/184c2ea4-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/18f51c30-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > gptid/19a861ea-c929-11e5-8075-0cc47a599098 ONLINE 0 0 0 > raidz3-2 ONLINE 0 0 24 > gptid/5f80fc42-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/60369e0f-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/60e8234a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/61a235f2-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/62580471-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/6316a38a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/63d4bce8-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/ebfc2b99-6893-11e6-9b09-0cc47a599098 ONLINE 0 0 0 > (resilvering) > gptid/654f143a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/66236b33-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/66eda3f6-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > raidz3-3 ONLINE 0 0 24 > gptid/c77a9da9-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/c83e100e-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/c8fd9ced-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/c9bb21ba-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/ca7a48db-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/cb422329-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/cbfe4c21-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/ccc43528-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/cd93a34c-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/ce622f51-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > gptid/cf2591d3-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 0 0 > cache > gptid/aedd3872-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > gptid/af559c10-265c-11e5-9a02-0cc47a599098 ONLINE 0 0 0 > > errors: Permanent errors have been detected in the following files: > > <0x597>:<0x1246> > <0x597>:<0x1249> > <0x597>:<0x125e> > <0x597>:<0x1261> > <0x597>:<0x127d> > <0x597>:<0x1280> > <0x599>:<0xe2c> > <0x599>:<0xe2f> > <0x599>:<0xe40> > <0x599>:<0xe43> > <0x599>:<0xe59> > <0x599>:<0xe62> > <0x5bc>:<0x2ad06> > <0x5bc>:<0x2aef3> > <0x5bc>:<0x2aef6> > pool/.system@auto-20160720.2300-2d:<0x0> > <0x5dc>:<0x397411> > <0x5dc>:<0x397414> > <0x5dc>:<0x38ee26> > <0x5dc>:<0x38ee29> > <0x5dc>:<0x38ee2c> > <0x5dc>:<0x45b2e> > <0x5dc>:<0x38ee2f> > <0x5dc>:<0x38ee32> > <0x5dc>:<0x394e58> > <0x5dc>:<0x394e5b> > <0x5dc>:<0x394e5e> > <0x5dc>:<0x394e61> > <0x5dc>:<0x394e64> > <0x5dc>:<0x394e67> > <0x5dc>:<0x394e6a> > <0x5dc>:<0x397285> > > _______________________________________________ > 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" -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@freebsd.org Fri Sep 2 19:42:02 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D585BCDF55 for ; Fri, 2 Sep 2016 19:42:02 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 353A838A for ; Fri, 2 Sep 2016 19:42:02 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: by mail-it0-x235.google.com with SMTP id c198so57347066ith.1 for ; Fri, 02 Sep 2016 12:42:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kateley-com.20150623.gappssmtp.com; s=20150623; h=reply-to:subject:references:to:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=NqP+XuS21ielDDIt5U4a75zaiYTRPZJ+E9t7rCm+Pqo=; b=cGPHNNu8IeM1wSXOribNS3oq/v43GCDUId8nF6I/5aHD5BjpTA52L109CFdA7r+VCm E87GVdVC0BKOs1S1g21di8gpoLxec4+p8q33PWl+OwaLM43xAlBdonV2OWSMq5xcVbB8 dZnrDSzurEChTbAoX4d/Z13tS6zhR65TiTN+inuprQJfIeByoGwMB599EujEbkGkWbs5 FwpH/KoJOOwPsnB3qCx5WWBAqLa3rDGX2T432rjoNNGTA49sd7F7M2SoWjTf+Q4szRec vy8Tt64TnyWPpY42Q3h1OszP+01b+s4tnZTB6SXL2AaGfK3wk/D9eDxMMr+/jjQsX4wz JIFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=NqP+XuS21ielDDIt5U4a75zaiYTRPZJ+E9t7rCm+Pqo=; b=ihB7qDUeedt7H7gigz1qjzzMmjwc2fQjkasATw8mLEBQvy2A5Qyeg2bzvPia5RUuy7 vv2p3+5JxXjAuaaI4S729/3UL87Pfk2Gj1DBiRKnIRw5h5DYQBmcmjgaIvWwo/rsc5aj ZMXQtnPjc2G+qggAwJI3/MS5qWwukVKJ4hSJmDI+IlGFVN+ZS/NV7/SsS0miuWw6pMon tcgs0LR7xHw1D0eGthSfi/IygPsYp7Uywb3qpN23Onm4O0lGXR19KDGAUAqn3LMtWY0e bqhrWCjjMDkdsWw30Lq2E8vuTTUgm6MJ0SqnFPE8LmeuY7M6OWhzvWqBt2xI8Fc+AJn3 umTQ== X-Gm-Message-State: AE9vXwPVV7udEWtQRencfn045z89X2Hj91fr/WH9+lEoB7VN1ft9Oy78cDkk0mIpKeDD6A== X-Received: by 10.36.189.68 with SMTP id x65mr6524773ite.97.1472845320291; Fri, 02 Sep 2016 12:42:00 -0700 (PDT) Received: from [192.168.0.19] (67-4-134-32.mpls.qwest.net. [67.4.134.32]) by smtp.googlemail.com with ESMTPSA id v7sm3128865ita.9.2016.09.02.12.41.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Sep 2016 12:41:59 -0700 (PDT) Reply-To: linda@kateley.com Subject: Re: phantom snapshots References: <58816ff0-3ab2-cbae-3d50-c4d5e89d9773@kateley.com> <57C9D1FB.6040904@b1t.name> To: freebsd-fs@freebsd.org From: Linda Kateley Organization: Kateley Company Message-ID: Date: Fri, 2 Sep 2016 14:41:58 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <57C9D1FB.6040904@b1t.name> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 19:42:02 -0000 On 9/2/16 2:24 PM, Volodymyr Kostyrko wrote: > Linda Kateley wrote: >> So I think I have isolated this to a phantom snapshot. At the end of >> this zpool status although the names change everytime I run scrub, it >> show unrecoverable error of files in a snapshot that doesn't exit. >> >> It also has in that zfs dataset it has a .zfs directory with a name of >> old snaps. >> >> Anyone know how to view or clear these phantom snaps? I tried to remove >> the files in the snapshot directory, but it is read-only. > > This looks like pointers to files that were already deleted/purged. I > once faced this errors but that was on bad controller, I don't think > this can be caused by bad memory/errors. When that happened I scrubbed > pool, removed all files noted, cleaned zpool errors (they are > persistent, even the file was removed and snapshots doen't exist they > are still shown) and scrubbed the pool again. How did you remove the files in the snapshot? I keep trying but it is read-only? Can I remount it read-write? > >> >> Ideas? >> >> Linda >> >> >> pool: pool >> state: ONLINE >> status: One or more devices is currently being resilvered. The pool >> will >> continue to function, possibly in a degraded state. >> action: Wait for the resilver to complete. >> scan: resilver in progress since Fri Sep 2 10:42:48 2016 >> 46.8T scanned out of 144T at 2.48G/s, 11h11m to go >> 46.5G resilvered, 32.40% done >> config: >> >> NAME STATE READ >> WRITE CKSUM >> pool ONLINE 0 >> 0 12 >> raidz3-0 ONLINE 0 >> 0 0 >> gptid/ac108605-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ac591d4e-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ac92fd0d-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/accd3076-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ad067e97-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ad46cbee-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ad91ba17-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/adcbdd0a-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ae07dc0d-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ae494d10-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ae93a3a5-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> raidz3-1 ONLINE 0 >> 0 0 >> gptid/12f6a4c5-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/511ea1f9-1932-11e6-9b1e-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/14436fcf-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/14f50aa3-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/159b5654-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/163d682b-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/16ee624e-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/1799dde3-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/184c2ea4-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/18f51c30-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/19a861ea-c929-11e5-8075-0cc47a599098 ONLINE 0 >> 0 0 >> raidz3-2 ONLINE 0 >> 0 24 >> gptid/5f80fc42-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/60369e0f-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/60e8234a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/61a235f2-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/62580471-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/6316a38a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/63d4bce8-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ebfc2b99-6893-11e6-9b09-0cc47a599098 ONLINE 0 0 0 >> (resilvering) >> gptid/654f143a-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/66236b33-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/66eda3f6-4e00-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> raidz3-3 ONLINE 0 >> 0 24 >> gptid/c77a9da9-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/c83e100e-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/c8fd9ced-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/c9bb21ba-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ca7a48db-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/cb422329-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/cbfe4c21-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ccc43528-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/cd93a34c-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/ce622f51-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/cf2591d3-4e02-11e6-b7cf-0cc47a599098 ONLINE 0 >> 0 0 >> cache >> gptid/aedd3872-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> gptid/af559c10-265c-11e5-9a02-0cc47a599098 ONLINE 0 >> 0 0 >> >> errors: Permanent errors have been detected in the following files: >> >> <0x597>:<0x1246> >> <0x597>:<0x1249> >> <0x597>:<0x125e> >> <0x597>:<0x1261> >> <0x597>:<0x127d> >> <0x597>:<0x1280> >> <0x599>:<0xe2c> >> <0x599>:<0xe2f> >> <0x599>:<0xe40> >> <0x599>:<0xe43> >> <0x599>:<0xe59> >> <0x599>:<0xe62> >> <0x5bc>:<0x2ad06> >> <0x5bc>:<0x2aef3> >> <0x5bc>:<0x2aef6> >> pool/.system@auto-20160720.2300-2d:<0x0> >> <0x5dc>:<0x397411> >> <0x5dc>:<0x397414> >> <0x5dc>:<0x38ee26> >> <0x5dc>:<0x38ee29> >> <0x5dc>:<0x38ee2c> >> <0x5dc>:<0x45b2e> >> <0x5dc>:<0x38ee2f> >> <0x5dc>:<0x38ee32> >> <0x5dc>:<0x394e58> >> <0x5dc>:<0x394e5b> >> <0x5dc>:<0x394e5e> >> <0x5dc>:<0x394e61> >> <0x5dc>:<0x394e64> >> <0x5dc>:<0x394e67> >> <0x5dc>:<0x394e6a> >> <0x5dc>:<0x397285> >> >> _______________________________________________ >> 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 Fri Sep 2 20:16:43 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10681BCD5E0 for ; Fri, 2 Sep 2016 20:16:43 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) by mx1.freebsd.org (Postfix) with ESMTP id B63557DD for ; Fri, 2 Sep 2016 20:16:42 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.160] (probe.42.lan [172.29.1.160]) by limbo.b1t.name (Postfix) with ESMTPSA id 3DAF7105 for ; Fri, 2 Sep 2016 23:16:39 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=b1t.name; s=mail; t=1472847400; bh=qWf3LT2Wgizndbj1V2gA1snj3/4whN4IlNc1SSOXqxA=; h=Subject:To:References:From:Date:In-Reply-To; b=VWqyScVdOzvinivKM0+LOrfOi2ZTtocuQOnb1MAmYG4Ioyok1yDfHkIghh/SDiR7i vkDiD9dpJNSS3ToZnmNSjYxPLP0dyIN9ohzlRqIX6G1CCqc9GKXQQ4JBi2BVewWat3 3l+0fs/kAycQBBHdL5njqK+dWU7otb3Cpv3BFFPk= Subject: Re: phantom snapshots To: freebsd-fs@freebsd.org References: <58816ff0-3ab2-cbae-3d50-c4d5e89d9773@kateley.com> <57C9D1FB.6040904@b1t.name> From: Volodymyr Kostyrko Message-ID: <57C9DE27.8020806@b1t.name> Date: Fri, 2 Sep 2016 23:16:39 +0300 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 20:16:43 -0000 Linda Kateley wrote: > > > On 9/2/16 2:24 PM, Volodymyr Kostyrko wrote: >> Linda Kateley wrote: >>> So I think I have isolated this to a phantom snapshot. At the end of >>> this zpool status although the names change everytime I run scrub, it >>> show unrecoverable error of files in a snapshot that doesn't exit. >>> >>> It also has in that zfs dataset it has a .zfs directory with a name of >>> old snaps. >>> >>> Anyone know how to view or clear these phantom snaps? I tried to remove >>> the files in the snapshot directory, but it is read-only. >> >> This looks like pointers to files that were already deleted/purged. I >> once faced this errors but that was on bad controller, I don't think >> this can be caused by bad memory/errors. When that happened I scrubbed >> pool, removed all files noted, cleaned zpool errors (they are >> persistent, even the file was removed and snapshots doen't exist they >> are still shown) and scrubbed the pool again. > How did you remove the files in the snapshot? I keep trying but it is > read-only? Can I remount it read-write? I just removed snapshots. Snapshot can't be remounted r/w. Snapshot can be cloned to obtain writable FS access, but after that snapshots become indestructible until only one snapshot successor remains. -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@freebsd.org Fri Sep 2 23:13:08 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77161BCD4FB for ; Fri, 2 Sep 2016 23:13:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D64BA41 for ; Fri, 2 Sep 2016 23:13:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u82ND7mP014320 for ; Fri, 2 Sep 2016 23:13:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Fri, 02 Sep 2016 23:13: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.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: gjb@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 23:13:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 --- Comment #13 from Glen Barber --- (In reply to Kirk McKusick from comment #10) > It appears that there is an item on the worklist that has been prematurely > freed. This freeing should be impossible as anything on a worklist has its > ONWORKLIST flag set and the worklist freeing routine will panic if the > ONWORKLIST flag is set. However I have written the following check to see= if > we are finding freed items on the worklist in softdep_disk_io_initiation(= ): >=20 > Index: sys/ufs/ffs/ffs_softdep.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- sys/ufs/ffs/ffs_softdep.c (revision 305057) > +++ sys/ufs/ffs/ffs_softdep.c (working copy) > @@ -9949,6 +9949,13 @@ >=20=20 > if ((wk =3D LIST_FIRST(&bp->b_dep)) =3D=3D NULL) > return; > + if (wk->wk_type > D_LAST + 1) { > + printf("dead worklist: %p next %p prev %p type %s state > 0x%X\n", > + wk, wk->wk_list.le_next, wk->wk_list.le_prev, > + TYPENAME(wk->wk_type), wk->wk_state); > + LIST_INIT(&bp->b_dep); > + return; > + } > ump =3D VFSTOUFS(wk->wk_mp); >=20=20 > marker.wk_type =3D D_LAST + 1; /* Not a normal workitem */ >=20 > I would appreciate your running with this patch and reporting if you get = the > "dead worklist" error message. I do not know what information you want from ddb, and I never thought I'd e= ver say this, but "yay, the machine finally crashed again." I will leave the machine in its current state unless instructed otherwise. dead worklist: 0xfffffd080edd5400 next 0xdeadc0dedeadc0de prev 0xdeadc0dedeadc0de type ??? state 0xDEADC0 panic: Bad link elm 0xfffffd00b7e0ba00 prev->next !=3D elm Please let me know what additional information you want. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Sep 3 10:26:29 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC8E6BCB353 for ; Sat, 3 Sep 2016 10:26:29 +0000 (UTC) (envelope-from juergen.gotteswinter@internetx.com) Received: from mx1.internetx.com (mx1.internetx.com [62.116.129.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92F7719E for ; Sat, 3 Sep 2016 10:26:29 +0000 (UTC) (envelope-from juergen.gotteswinter@internetx.com) Received: from localhost (localhost [127.0.0.1]) by mx1.internetx.com (Postfix) with ESMTP id A39A74C4C5C9; Sat, 3 Sep 2016 12:26:20 +0200 (CEST) X-Virus-Scanned: InterNetX GmbH amavisd-new at ix-mailer.internetx.de Received: from mx1.internetx.com ([62.116.129.39]) by localhost (ix-mailer.internetx.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cyCSc0DTf6qc; Sat, 3 Sep 2016 12:26:18 +0200 (CEST) Received: from [192.168.100.26] (pizza.internetx.de [62.116.129.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.internetx.com (Postfix) with ESMTPSA id 68CF54C4C597; Sat, 3 Sep 2016 12:26:18 +0200 (CEST) Reply-To: juergen.gotteswinter@internetx.com Subject: Re: [ZFS] refquota is very slow ! References: To: Ben RUBSON , FreeBSD FS From: InterNetX - Juergen Gotteswinter Organization: InterNetX GmbH Message-ID: Date: Sat, 3 Sep 2016 12:26:18 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2016 10:26:29 -0000 cant confirm this, works like a charm without difference to normal quota setting Am 02.09.2016 um 18:15 schrieb Ben RUBSON: > Hello, > > When I set refquota on a dataset, write IOs are done very sloooowwwly some MB below the limit. > And I can't manage to reach it, dd (used to create a file to fulfil space) seems to stall. > > No problem however with quota, dd goes to the end and returns with : > "Disc quota exceeded" > > Any clue ? > I would have been interested to use refquota to avoid impacting users with snapshots'fs space, but this option is quite unusable as is. > > Thank you very much ! > > Ben > > > _______________________________________________ > 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 Sat Sep 3 13:22:27 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2EE2BCB637 for ; Sat, 3 Sep 2016 13:22:27 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30081EAC for ; Sat, 3 Sep 2016 13:22:27 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id c133so64491457wmd.1 for ; Sat, 03 Sep 2016 06:22:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:mime-version:subject:message-id:date :references:in-reply-to:to; bh=1ew3K6oADQWUXvrg5AFVsZHdeVWB3h7dCpSRu8vF3DY=; b=Oe1Fbl8tSOSkBhgNf+qZ9aJyeE0b652ncS4HwMMguLZ5cLESt3XhAnUgjAWHohzKE/ SrlHbwhqZpItIiZHHf7Hp2rFQoA0Ue5jimJX1R21GU5Zx8nfAoc1aei8LJfg8PCZYn5C 9N/trpK49qu0VpSWafU+27mLYZYzOb74aH3Krc/aenw7xr5wDQapLIOjqn+v9k4d2OJk 6fPlnGyoL0IHBygZGINxGJqdYum/Hc2lB6yz0+MbKAcuGdDuX9l6QyoSVDej0eZaV9yl OiUwofeDA3w+QxxS7onrzyVCujk6b9YY0ANNGsTenQ9Xl2DtrLOxnqjBCEJfpEBhWKM+ VoDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:references:in-reply-to:to; bh=1ew3K6oADQWUXvrg5AFVsZHdeVWB3h7dCpSRu8vF3DY=; b=JyoqUKSqQGuADsBW3mKIJsEsPN5/8MCa2k+jm7jZ0lMsH1X5ss8dAlyQiYnI8NIq60 +Yf/p1nodnris5EU/33JZSiP6LlrKkETT10KxcU/xuvVKGlw2Y6copZkyFHBkgk/jEQH QWCgutPDL93mWBzkq3Ugk1WM+3yHR/QGD7UVTwCPHS/GqD2Rnlv2z8EjbobVrkEc33E0 ya9PYIJ2J/VySccYovFYMqJMXJCVLLAK6PvowA9TWiKvkMzuiYDBhH0ip5ifQhfWFO6M whKosOzttG/OtJsMdmyW06CddB94a2JHEslDpPj/qirDtffXn5Uu01QE5Cz9PzVzPc4D A1JQ== X-Gm-Message-State: AE9vXwPzJCnoIUnivi4anWRxEOC3Dtg8ltfQuBbiKGIAIjRqXeVuUDgiBh1qgoC11sA2fw== X-Received: by 10.28.182.136 with SMTP id g130mr7329763wmf.21.1472908945570; Sat, 03 Sep 2016 06:22:25 -0700 (PDT) Received: from [10.136.241.35] ([80.12.55.35]) by smtp.gmail.com with ESMTPSA id v137sm3011914wmf.3.2016.09.03.06.22.24 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 03 Sep 2016 06:22:24 -0700 (PDT) From: Ben RUBSON Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: HAST + ZFS + NFS + CARP Message-Id: <62938BA3-67EC-466E-8A0E-E8B6FA544D74@gmail.com> Date: Sat, 3 Sep 2016 15:22:20 +0200 References: <61283600-A41A-4A8A-92F9-7FAFF54DD175@ixsystems.com> <20160704183643.GI41276@mordor.lan> <20160704193131.GJ41276@mordor.lan> <20160811091016.GI70364@mordor.lan> <1AA52221-9B04-4CF6-97A3-D2C2B330B7F9@sarenet.es> <20160811101539.GM70364@mordor.lan> <20160811110235.GN70364@mordor.lan> <20160811114919.GP70364@mordor.lan> In-Reply-To: <20160811114919.GP70364@mordor.lan> To: freebsd-fs@freebsd.org X-Mailer: iPhone Mail (13G36) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2016 13:22:27 -0000 > On 11 Aug 2016, at 13:49, Julien Cigar wrote: >=20 > BTW any idea if some sort of checksum for payload is made in the iSCSI > protocol? There is ! Interesting paper related to this : https://www.anixter.com/content/dam/Suppliers/viavi/White%20Paper/Understand= ing%20sCASI%20Digest.pdf Ben= From owner-freebsd-fs@freebsd.org Sat Sep 3 15:30:11 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68759BCE71C for ; Sat, 3 Sep 2016 15:30:11 +0000 (UTC) (envelope-from sodynet1@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D6A3614 for ; Sat, 3 Sep 2016 15:30:11 +0000 (UTC) (envelope-from sodynet1@gmail.com) Received: by mail-it0-x232.google.com with SMTP id c198so88046701ith.1 for ; Sat, 03 Sep 2016 08:30:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xz/gmzP+Ie6/oyLmZMs8mWNkY0yqqm75fQle/uEn8NE=; b=Slvxh1bNokzgjXVW+sJvElel11mimbxdNiWgU/HeSxRZtiTrCKlNV55j/4m3ykaQMB QATCPeJmiKnekrYiT1GMPk7HZwx2V13GILDPxa8vJm1Jnuht5idLep7WOBDrw+5QMJP6 /td53zIqN+2oPR6Pw9uWJzC95dGS88g+T5GjY9zI/S9mcZcpVOvkQs3cwS/0JMyODxTH lKUOOxBsSM/j6plEkM57Mkxsddap7FbGOXIBXKAXB10FDVMkz5wwK+s6nhLh6dtrVOBH hRnTGOYxwb18d7MLvoNWEIcwo7W7Iiz7lIkBPYAI9kryIiPGzUYSxdF1q/CFKc2DINwl zy+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xz/gmzP+Ie6/oyLmZMs8mWNkY0yqqm75fQle/uEn8NE=; b=Q5/nsufy2t7w61FrLEgq3UI4hdLrwihFF83bMwL2xh3nADxSCho0pLNGwHNJHrWPVG iFjutdbxSKqTU+fQyi4l12he6jNqugb9aL2bOXRyn+w4HLtMji1awHxFpq3AduO5zvJz YmHz+1ybxHB8L5zrUhg0e5ZaLzGnMDHwHEGAgZ11scuzr+ZuA7Y8Bz3r8dtgE3glYLvh gbbf2JjTSrU7KpFS3jun6b3qrGpMeJsn3dJV2Z+BbVD8Ok6HH9luJJOPbKhoktWqR7ZU KA96JvBEuk8DZD0bJOiypKssB84TZOMuFXmu5Js78YkGmV+q755ZXb9D/D+pFgcfXOB5 Jeuw== X-Gm-Message-State: AE9vXwOXwLc/EUz1B0ZnMSvLNcC2VGK8Asx94kz6azym3lpV4CLGMQTyenB29e2EJc6+5DaywoSRdDoKRL3nFQ== X-Received: by 10.36.156.197 with SMTP id b188mr12332902ite.28.1472916610616; Sat, 03 Sep 2016 08:30:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.142.17 with HTTP; Sat, 3 Sep 2016 08:30:07 -0700 (PDT) Received: by 10.107.142.17 with HTTP; Sat, 3 Sep 2016 08:30:07 -0700 (PDT) In-Reply-To: <62938BA3-67EC-466E-8A0E-E8B6FA544D74@gmail.com> References: <61283600-A41A-4A8A-92F9-7FAFF54DD175@ixsystems.com> <20160704183643.GI41276@mordor.lan> <20160704193131.GJ41276@mordor.lan> <20160811091016.GI70364@mordor.lan> <1AA52221-9B04-4CF6-97A3-D2C2B330B7F9@sarenet.es> <20160811101539.GM70364@mordor.lan> <20160811110235.GN70364@mordor.lan> <20160811114919.GP70364@mordor.lan> <62938BA3-67EC-466E-8A0E-E8B6FA544D74@gmail.com> From: Sami Halabi Date: Sat, 3 Sep 2016 18:30:07 +0300 Message-ID: Subject: Re: HAST + ZFS + NFS + CARP To: Ben RUBSON Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2016 15:30:11 -0000 Hi To download the file there is need to go to anixter.com and register and login otherwise it wont download Sami =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A 3 =D7=91=D7=A1=D7=A4=D7=98=D7=B3 2016 = 16:22,=E2=80=8F "Ben RUBSON" =D7=9B=D7=AA=D7=91: > > > > On 11 Aug 2016, at 13:49, Julien Cigar wrote: > > > > BTW any idea if some sort of checksum for payload is made in the iSCSI > > protocol? > > There is ! > Interesting paper related to this : > https://www.anixter.com/content/dam/Suppliers/viavi/ > White%20Paper/Understanding%20sCASI%20Digest.pdf > > Ben > _______________________________________________ > 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" >