From owner-freebsd-fs@freebsd.org Sun May 8 10:43: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 3580BB32739 for ; Sun, 8 May 2016 10:43:34 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2237018B6 for ; Sun, 8 May 2016 10:43:34 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1DE44B32738; Sun, 8 May 2016 10:43:34 +0000 (UTC) Delivered-To: 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 1D89BB32737 for ; Sun, 8 May 2016 10:43:34 +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 D9A9118B5 for ; Sun, 8 May 2016 10:43:33 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:7448:9e99:d76f:b82]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 2761E44D; Sun, 8 May 2016 13:43:30 +0300 (MSK) Date: Sun, 8 May 2016 13:43:26 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <07228891.20160508134321@serebryakov.spb.ru> To: "Poul-Henning Kamp" , "George Neville-Neil" CC: fs@freebsd.org Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories In-Reply-To: <59877.1462639101@critter.freebsd.dk> References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="----------0E214309925CB393F" 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, 08 May 2016 10:43:34 -0000 ------------0E214309925CB393F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: base64 SGVsbG8gUG91bC1IZW5uaW5nLA0KDQpTYXR1cmRheSwgTWF5IDcsIDIwMTYsIDc6Mzg6MjEg UE0sIHlvdSB3cm90ZToNCg0KPiBIeWJyaWQgImRpc2sgd2l0aCBTU0QgY2FjaGUiIGlzIGEg dHJhbnNpdGlvbmFyeSBwaGVub21lbmEsIGl0J3MNCj4gcHJvYmFibHkgbm90IGdvaW5nIHRv IGJlIHJlbGV2YW50IGluIGZpdmUgeWVhcnMsIHdoaWNoIG1lYW5zDQo+IHRoYXQgaXQgaXMg YWxtb3N0IGFscmVhZHkgdG9vIGxhdGUgdG8gZGV2ZWxvcCBhIG5ldyBmaWxlc3lzdGVtDQo+ IGZvciBpdDogIEJ5IHRoZSB0aW1lIHRoZSBjb2RlIGlzIHRydXN0d29ydGh5LCBub2JvZHkg d2lsbCBuZWVkDQo+IGl0IGFueSBtb3JlLg0KICAgRG8geW91IGNvbnNpZGVyIG5ldyBJbnRl bCBOVk0gIjNEIFhQb2ludCIgdGVjaG5vbG9neT8gVGhleSh0bSkgcHJvbWlzZQ0KIHByaWNl cyBsb3dlciB0aGFuIERSQU0sIGJ1dCBoaWdoZXIgdGhhbiBTU0QuIEFuZCBzYW1lIGZvciBz cGVlZC4gTG9va3MNCiBsaWtlLCB0aGVyZSB3aWxsIGJlIFRIUkVFIGxheWVycyBvZiBOVk0g aW4gbmVhciBmdXR1cmU6IHZlcnkgbGFyZ2UgYW5kIHNsb3cNCiAoSERELCBpU0NTSS9GQyBh dHRhY2hlZCAic2hlbGYiLCB0aGluZ3MgbGlrZSB0aGlzLCBtdWx0aXRlcmFieXRlKSwgU1NE DQogKGluIDEtMTAgdGVyYWJ5dGUgcmFuZ2UpIGFuZCB0aGlzIFhQb2ludCBpbiBjdXJyZW50 IFNTRCByYW5nZS4NCg0KLS0gDQpCZXN0IHJlZ2FyZHMsDQogTGV2ICAgICAgICAgICAgICAg ICAgICAgICAgICAgIG1haWx0bzpsZXZARnJlZUJTRC5vcmc= ------------0E214309925CB393F Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJXLxhOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePD3wP/0eOH+QmPVHBsVdqkgX/QIjJ +NAbtv1x2Zs6ErHGnDVjPjwBvlqZCV0eEkXIFEsqXzpGuLirupjVTqpbyLVOKWPZ MxsYzTX9+HxunoDGWeaabnx0UD9Ihc/dQp/N4wU+jB3W4EHCwCQ3A9fOpdksF6WP rusQVdyivBpBwVJJIG3Do2kkWdZMdCemy706VPwAVvwIx8tFK0FaBkZef79k55n1 N4u6Po1FJhzdZVJ3NmaFVGbZUDIzVtOM6GcmKqALmdhTtLZ4Qeo5Z1cRRVBm6lYY DY9E7D1wfb7bfBSypACDNEN3hJaYz4gRc9/GNfYqBU7/stL1XeuYteXp+ZwrC8Tg T7c6Rm6LtQ2Gh5QP+L4Ak8X8BwScr6VGO8GLkqn5FQtltGm+EONbY21vPNn3bREn P+emuXbayk15BoDxdm4BPBwjyrsBVcHzp+UY92J/1cXYHMQeNU6JtptIHX/NazIu Gs87PmX24u2EEvZDH1LReAfOxqOH/dYfusEq/1Zo0C0BLg3H0aBSTQ+aDIG52O4Z T5Gp/OH2DR0ZIuf+0ftyvvZtsFHB/6wZajkwoqMiMJGQeb/B1HbauC/gvnS0P9Mc JxvxMXekgdPzPKxLOl5AKUNqnfwEn6S2LeWeVsADM/YPabJqdWz05cip0diaujBb wKVzYMSkLFGfZoPpKkZS =3HP8 -----END PGP MESSAGE----- ------------0E214309925CB393F-- From owner-freebsd-fs@freebsd.org Sun May 8 10:47: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 E45A5B32826 for ; Sun, 8 May 2016 10:47:43 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D099F1A14 for ; Sun, 8 May 2016 10:47:43 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: by mailman.ysv.freebsd.org (Postfix) id CFF45B32825; Sun, 8 May 2016 10:47:43 +0000 (UTC) Delivered-To: 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 CF9E3B32824 for ; Sun, 8 May 2016 10:47:43 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 9B67A1A13; Sun, 8 May 2016 10:47:43 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 624CD4FB03; Sun, 8 May 2016 10:47:41 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u48AldSb062926; Sun, 8 May 2016 10:47:40 GMT (envelope-from phk@phk.freebsd.dk) To: lev@FreeBSD.org cc: "George Neville-Neil" , fs@freebsd.org Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories In-reply-to: <07228891.20160508134321@serebryakov.spb.ru> From: "Poul-Henning Kamp" References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <62924.1462704459.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sun, 08 May 2016 10:47:39 +0000 Message-ID: <62925.1462704459@critter.freebsd.dk> 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, 08 May 2016 10:47:44 -0000 -------- In message <07228891.20160508134321@serebryakov.spb.ru>, Lev Serebryakov w= rites : The problem with that kind of hardware is that either you specialize 100% for that vendors product, with resulting lock-in, or you satisfy yourself with a generic solution which works an anything sensible. I don't think FreeBSD has the bandwidth for anything but the second option= . -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-fs@freebsd.org Sun May 8 10:56: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 E8A7DB32D87 for ; Sun, 8 May 2016 10:56:18 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (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 76D461F1D for ; Sun, 8 May 2016 10:56:18 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 862F03A69 for ; Sun, 8 May 2016 10:56:07 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/862F03A69; dkim=none; dkim-atps=neutral Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories To: freebsd-fs@freebsd.org References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> From: Matthew Seaman Message-ID: Date: Sun, 8 May 2016 11:56:00 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <07228891.20160508134321@serebryakov.spb.ru> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="52WxEOuqfanQLgriumuJ1uH4h5HoxWdt9" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk 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, 08 May 2016 10:56:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --52WxEOuqfanQLgriumuJ1uH4h5HoxWdt9 Content-Type: multipart/mixed; boundary="S0019WSxuoFIWlr8Np2vdhKURpBeWRpiD" From: Matthew Seaman To: freebsd-fs@freebsd.org Message-ID: Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> In-Reply-To: <07228891.20160508134321@serebryakov.spb.ru> --S0019WSxuoFIWlr8Np2vdhKURpBeWRpiD Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 08/05/2016 11:43, Lev Serebryakov wrote: > Hello Poul-Henning, >=20 > Saturday, May 7, 2016, 7:38:21 PM, you wrote: >=20 >> Hybrid "disk with SSD cache" is a transitionary phenomena, it's >> probably not going to be relevant in five years, which means >> that it is almost already too late to develop a new filesystem >> for it: By the time the code is trustworthy, nobody will need >> it any more. > Do you consider new Intel NVM "3D XPoint" technology? They(tm) promi= se > prices lower than DRAM, but higher than SSD. And same for speed. Looks= > like, there will be THREE layers of NVM in near future: very large and= slow > (HDD, iSCSI/FC attached "shelf", things like this, multiterabyte), SSD= > (in 1-10 terabyte range) and this XPoint in current SSD range. 3D X-Point is only something like a factor of 30x slower than current DRAM modules (which is to say thousands of times faster than existing Flash modules), and I believe Intel are planning on selling it packaged as DIMMs as well as PCIx NVME devices. Kirk mentioned a memory-based variant of UFS in his run through of the history of filesystems during his talk at EuroBSDCon last year -- looks like that could suddenly become relevant again. Cheers, Matthew --S0019WSxuoFIWlr8Np2vdhKURpBeWRpiD-- --52WxEOuqfanQLgriumuJ1uH4h5HoxWdt9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXLxtHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATdLAP/RywGFEYOBvizjQyfpDfnm/z aj2ZK9Wv/AOmJql9CjJFpQHATcHJsoZLBj/ttqBevqxP1IWZuQXy8DYZfbLRYqHo qrP1N90qQchZBu4LxCA47sty9vh5gd+k+TdYJ0IOIvLdEOhbly2XSR+Y3OV9vu5L u8UwMJ5zcZ3T95UgXy+d3FUGYI982HgvdDNmc29obVPLDYPd8iBfJfNjoBPGNa5O 1Ik80mD65aaVjU7DtcPCT6igTPnQq7DpEXXvKhEikVNCreTFXLLdvUGo4VgJnN03 8iXaz/bG73YwGwGhuropOKPABIhoNdUXqX5OaPpaf0cZLKxcrfoygOR0KJNxCHm5 f/VnnISvwp6r8aREZRoWmdZVRfr6qI+ueth3v/8wHyadTnZGWdFzcHBvS3BQ2fP0 2mmlRCcV/DyTAQB/GcE07ZWD7CGC1oulHQXq2NCzyh/lF/HyDcAItZi/NQS7ogjF 0rOeulURv1kZKkfFU5+UFwhxfiTIFmmeb1VlE3H9VtkVd/OHJBVNBY/qJbnepnAn jn8YQzD8I9ImhENAuW6lM/z6Glz5NWQQeTUU6kbvMZUrTa4xi5avn2eTuGPnMAr4 e9Arf+pdbsetdvNsIfiPP0cY1LZIlEFk8njtgX+Ono4oCBkVP7BIRoFTO2+AYa4s P2coiAVOYAf1Ia7viCJW =IItI -----END PGP SIGNATURE----- --52WxEOuqfanQLgriumuJ1uH4h5HoxWdt9-- From owner-freebsd-fs@freebsd.org Sun May 8 11:02: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 D9779B32FBF for ; Sun, 8 May 2016 11:02:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C93111653 for ; Sun, 8 May 2016 11:02:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id C8803B32FBE; Sun, 8 May 2016 11:02:36 +0000 (UTC) Delivered-To: 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 C8283B32FBD for ; Sun, 8 May 2016 11:02:36 +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 5DC9F1652 for ; Sun, 8 May 2016 11:02:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:7448:9e99:d76f:b82]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 2DB0C45A for ; Sun, 8 May 2016 14:02:28 +0300 (MSK) Date: Sun, 8 May 2016 14:02:27 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <886527019.20160508140221@serebryakov.spb.ru> To: fs@freebsd.org Subject: ZFS hierathy, snapshots and backup tool -- how to traverse snapshotted tree properly? MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="----------04417A05A0890A6CE" 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, 08 May 2016 11:02:36 -0000 ------------04417A05A0890A6CE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: base64 SGVsbG8gRnMsDQoNCiAgSSdtIHdyaXRpbmcgc29tZSBiYWNrdXAgdG9vbCAoeWV0IGFub3Ro ZXIsIGRvbid0IGFzayEpIGFuZCBlbmNvdW50ZXIgc29tZQ0KICJpbmNvbnZlbmllbmNlIiBp biBaRlMgc25hcHNob3Qgc3lzdGVtLCBmb3Igd2hpY2ggSSBkb24ndCBzZWUgZ29vZCBzb2x1 dGlvbg0KIChhbGwgSSBjb3VsZCBpbWFnaW5lIGlzIGtsdWRneSBhbmQgdWdseSkuIE1heWJl LCB0aGVyZSBpcyBzb21lIGFwcHJvYWNoIEkNCiBkaWRuJ3Qgbm90aWNlIG9yIHNvbWUgWkZT LXNwZWNpZmljIEFQSSBJIHNob3VsZCBub3c/DQoNCiAgTGV0cyBzYXksIGhlcmUgaXMgc29t ZSBoaWVyYXJjaHkgb2YgWkZTIGZpbGUgc3lzdGVtcy4gRm9yIGV4YW1wbGUsIEkgd2lsbA0K ICB1c2UgIi9ob21lIiB3aGljaCBoYXZlIG9uZSBmaWxlc3lzdGVtIHBlciB1c2VyOg0KDQog ICAgenBvb2wvaG9tZS91c2VyMSAtPiAvaG9tZS91c2VyMQ0KICAgIHpwb29sL2hvbWUvdXNl cjIgLT4gL2hvbWUvdXNlcjINCiAgICB6cG9vbC9ob21lL3VzZXIzIC0+IC9ob21lL3VzZXIz DQoNCiBCdXQgaXQgY291bGQgYmUgbXVjaCBtb3JlIGNvbXBsZXggaGllcmFyY2h5Lg0KDQog Tm93LCB3ZSBoYXZlIGJhY2t1cCB0b29sLCB3aGljaCB3b3JrcyB3aXRoIGZpbGVzeXN0ZW0g dHJlZS4gSWYgSSB3YW50IHRvDQpiYWNrdXAgYWxsIG15IHVzZXJzLCBJIGNvdWxkIHNldHVw IGl0IHRvIGJhY2t1cCAiL2hvbWUiIGFuZCBldmVyeXRoaW5nDQp3b3JrcyBldmVuIGlmIHVz ZXJzIHdpbGwgYmUgYWRkZWQgKG9yIHJlbW92ZWQpIGluIGZ1dHVyZS4NCg0KICBCdXQgU1RP UCEgV2Ugd2FudCB0byBiYWNrdXAgc25hcHNob3QsIGlmIG91ciBmaWxlc3lzdGVtIHN1cHBv cnRzDQpzbmFwc2hvdHMhIEl0IGlzIGdvb2QgaWRlYSEgWkZTIHN1cHBvcnRzIHNuYXBzaG90 IQ0KDQogIEl0IGlzIGVhc3kgdG8gdGVhY2ggYmFja3VwIHRvb2wgdG8gY2FsbA0KDQp6ZnMg c25hcHNob3QgLXIgJHtiYWNrdXBfcm9vdH1AJHtyYW5kb21uYW1lfQ0KDQogIGF0IGJlZ2lu bmluZyBhbmQNCg0KemZzIGRlc3Ryb3kgLXIgJHtiYWNrdXBfcm9vdH1AJHtyYW5kb21uYW1l fQ0KDQogIGF0IHRoZSBlbmQgb2YgdGhlIHByb2Nlc3MuIE5vIHByb2JsZW1zIGhlcmUuDQoN CiAgIFByb2JsZW1zIGFyZSwgaG93IGJhY2t1cCB0b29sIHNob3VsZCBUUkFWRVJTRSBzbmFw c2hvdHRlZCBkaXJlY3RvcnkgdHJlZQ0KIG5vdz8NCg0KICAgU2ltcGxlICJnbyB0byAke2Jh Y2t1cF9yb290fS8uemZzLyR7cmFuZG9tbmFtZX0iIERPRVNOJ1QgV09SSyEgQmVjYXVzZQ0K IC9ob21lLy56ZnMvJHtyYW5kb21uYW1lfSBkb2VzIG5vdCBjb250YWluIHVzZXIgZGlyZWN0 b3JpZXMuIFRoZXkgYXJlDQogc2VwYXJhdGUgRlNlcyBhbmQgaGF2ZSBzZXBhcmF0ZSBwYXRo cyBmb3IgdGhlaXIgc25hcHNob3RzLiBUcmF2ZXJzaW5nDQogImxpdmUiIHRyZWUgYnV0IGdl dHRpbmcgZGF0YSBmcm9tIHNuYXBzaG90cyBpcyBub3QgcHJvcGVyIHdheSB0byBkbyB0aGlz LA0KIGZvciBzdXJlLCBhcyBpdCBpcyBkZXByZWNpYXRlIHdob2xlIGlkZWEgb2Ygc25hcHNo b3RzLg0KDQogIElzIGhlcmUgZ29vZCBzb2x1dGlvbiBmb3IgdGhpcyBwcm9ibGVtPw0KDQog IE9mIGNvdXJzZSwgaXQgaXMgcG9zc2libGUgdG8gY29uZmlndXJlIGVhY2ggRlMgZm9yIGJh Y2t1cCB0b29sIG9uZS1ieS1vbmUsDQogYnV0IEkgZG9uJ3QgbGlrZSB0aGlzICBzb2x1dGlv biwgYXMgaW4gWkZTIHdvcmxkIHRoZXJlIGNvdWxkIGJlIHZlcnkgZGVlcA0KIGFuZCBuZXN0 ZWQgRlMgIGhpZXJhcmNoaWVzLiBBbHNvLCBjb25maWd1cmluZyBlYWNoIEZTIHNlcGFyYXRl bHkgaW4gYmFja3VwDQogdG9vbCBjb25maWd1cmF0aW9uIGxlYWRzIHRvIGZvcmdvdHRlbiBG U2VzIGluIGxvbmctdGVybSBtYWludGVuYW5jZSBmb3INCiBzdXJlLg0KDQotLSANCkJlc3Qg cmVnYXJkcywNCiBMZXYgICAgICAgICAgICAgICAgICAgICAgICAgIG1haWx0bzpsZXZARnJl ZUJTRC5vcmc= ------------04417A05A0890A6CE Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJXLxzDXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePr0oP/A1oOzA+bJ/hzpgNimvYEiS8 X/aEzthaekt1/Bzism+sVBmRPSima8D2o7iwUQ5mBkycokXJOREfgPbDyBvjsKBi mspA7G2B6oU6Ui53xXzNoVS77VD+WJd1m6PzGSvKxjNwWwWXDvBKVsLgk9aqtIWu 7Fzm98koz6xiY2rbzpFxFfqtlACV8TckvV2O1g8Dyb35W20+ANmoKg2AvC7LIJbW zdVi0Ev9VqSqFalu+lgn5AaV3U3axWhb5q4tPZibrrMylSQijrjo/HDr4ne+VB4z wTr0BmTPyNUbYUjJKgexGzXIdJlM9uA6uhGjZOhQT2NEH7sCG8b1wfE4QkmCTvfi rJee6nhNNVwljrzXu95NIxRpa2jZVdza+No6b94C9m9Etpku4YIMQwml3en+3R8R WfRHdI0RGBDKna5Y6pSu4FL40tN9I5NqO9l+EtUsvPB+15bDJUFC7xwtbCiiz7Qk lw59xPlH+4e3CPeZq/BO2jKeSamygvf4f5FkyvQMZTmJX0SdHG5tiQVROFspuCCu grjSoaAchq/Hd+ZzW+nQMMePMvn0VCXYfkh24dKgu6xI3BTuSCn+i98rkiZHM37S soIEW2Lbe3+tJd/Q0tHOgV/Maoa5r9f6KmlaL9vHLtVybxQ1pckLtKCwra19jaBM jYPfzSAj2tpUyxBbOp3h =eKje -----END PGP MESSAGE----- ------------04417A05A0890A6CE-- From owner-freebsd-fs@freebsd.org Sun May 8 11:08:49 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 DDC0BB22117 for ; Sun, 8 May 2016 11:08:49 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C9A6118BF for ; Sun, 8 May 2016 11:08:49 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id C846CB22113; Sun, 8 May 2016 11:08:49 +0000 (UTC) Delivered-To: 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 C7EC0B22112 for ; Sun, 8 May 2016 11:08:49 +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 918A418BE for ; Sun, 8 May 2016 11:08:49 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:7448:9e99:d76f:b82]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 2C0B345E; Sun, 8 May 2016 14:08:48 +0300 (MSK) Date: Sun, 8 May 2016 14:08:47 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1058947919.20160508140842@serebryakov.spb.ru> To: "Poul-Henning Kamp" CC: George Neville-Neil , fs@freebsd.org Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories In-Reply-To: <62925.1462704459@critter.freebsd.dk> References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> <62925.1462704459@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="----------0ED10706A2318C632" 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, 08 May 2016 11:08:50 -0000 ------------0ED10706A2318C632 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: base64 SGVsbG8gUG91bC1IZW5uaW5nLA0KDQpTdW5kYXksIE1heSA4LCAyMDE2LCAxOjQ3OjM5IFBN LCB5b3Ugd3JvdGU6DQoNCj4gVGhlIHByb2JsZW0gd2l0aCB0aGF0IGtpbmQgb2YgaGFyZHdh cmUgaXMgdGhhdCBlaXRoZXIgeW91IHNwZWNpYWxpemUNCj4gMTAwJSBmb3IgdGhhdCB2ZW5k b3JzIHByb2R1Y3QsIHdpdGggcmVzdWx0aW5nIGxvY2staW4sIG9yIHlvdSBzYXRpc2Z5DQo+ IHlvdXJzZWxmIHdpdGggYSBnZW5lcmljIHNvbHV0aW9uIHdoaWNoIHdvcmtzIGFuIGFueXRo aW5nIHNlbnNpYmxlLg0KDQo+IEkgZG9uJ3QgdGhpbmsgRnJlZUJTRCBoYXMgdGhlIGJhbmR3 aWR0aCBmb3IgYW55dGhpbmcgYnV0IHRoZSBzZWNvbmQgb3B0aW9uLg0KDQogIFJlYWxseSwg SW50ZWwgaXMgbm90ICJ0aGF0IHZlbmRvciIgbm93LiBJdCBpcyBUSEUgVmVuZG9yLiBGcmVl QlNEIGhhcyBhIExPVA0Kb2Ygc3BlY2lhbGl6YXRpb24gZm9yIHRoaXMgdmVuZG9yIChhbGwg aTM4NiBjb2RlLCBOVk1lLCBhbmQgb3RoZXIpLCBhbmQgbWFueQ0KdGhpbmcgZnJvbSBJbnRl bCAob3Igd2hpY2ggYmVjb21lcyB3aWRlc3ByZWFkIGluIEludGVsLWJhc2VkIHN5c3RlbXMs IGxpa2UNClBDSSwgd2hpY2ggaXMgbm90IGV4YWN0bHkgImZyb20gSW50ZWwiLCBvZiBjb3Vy c2UpIGJlY29tZXMgaW5kdXN0cmlhbA0Kc3RhbmRhcmQuDQoNCiBJIGRvbid0IHRoaW5rIHN1 Y2ggdHlwZSBvZiBtZW1vcnkgd2lsbCBiZSB2ZXJ5LUludGVsLXNwZWNpZmljIGZvciBsb25n LiBIUA0Kd29ya3Mgb24gc29tZXRoaW5nIGNvbXBhcmFibGUsIGFuZCBvdGhlciBjb21wYW5p ZXMgdG9vLg0KDQotLSANCkJlc3QgcmVnYXJkcywNCiBMZXYgICAgICAgICAgICAgICAgICAg ICAgICAgICAgbWFpbHRvOmxldkBGcmVlQlNELm9yZw== ------------0ED10706A2318C632 Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJXLx4/XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePGQcQANnutMRktOfrPIaXCxRDa7ZS TGTpYpiAArM6czZpvOwAD9UerMt8YjqvHWxn6E8P32fhxysqxekAsji3Tta0Di3L L4XK88Dus3//rkGhNlLxuBr5yGZ3WuXZjdfl3b5nAMvodhymdGi5EW4EJzgPsyUu 14dRYEf26WvL7ZsfNLuOuVCCmm5lxtea0MkP03M6a7popJlYPLfk2nA2TvElw1bo PzuUyzEjMT3VVn2GqsJ2JGyxebsFFpvQIuZK+a+IUA+UCJF9XEf0gXlKVXCZ5rnI LT1O34ze7gFmpe/2YS09v1w/se4ZFJJ1nB7KjAnFkjjrApV3bDBh9nCkMrLJ2Gzj LB+U0jPL9cs7l7u8ZPpf/frmNsOE9tBY8mVnuk3VS9TCGvnV/yxv7DXoZ83rV07E 7biDXQbuQtHltG61kL6OIrsHqxtuwm608VUlX7A1to34NSt2gs8TJ08F11LEPS0E PJo8jLZ+aRKLUEo+705qjBMti9uZtg6Ax4N0vidY1darb+wQb0GXWSvhBkwAZg7t WinvfmztJyWaSWDMl1dyPgzuiLD2ZoKzZs4ToF3Sb4OZFXuAPmDhj3B4T0J2Dh+C Efh07e2q6vjctyjD5KMsviyqJp39okadj+y8NMzj1gQamSNV2SkminGEdBgfQPqM 12Ce/QZ+UDsHbZ8MBKzj =LIOP -----END PGP MESSAGE----- ------------0ED10706A2318C632-- From owner-freebsd-fs@freebsd.org Sun May 8 11:17:03 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 3434FB22675 for ; Sun, 8 May 2016 11:17:03 +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 BA6241DFA; Sun, 8 May 2016 11:17:02 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:7448:9e99:d76f:b82]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 66843461; Sun, 8 May 2016 14:16:59 +0300 (MSK) Date: Sun, 8 May 2016 14:16:56 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1799639504.20160508141650@serebryakov.spb.ru> To: Matthew Seaman , freebsd-fs@freebsd.org Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories In-Reply-To: References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="----------08F0CA0FC2C071DDA" 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, 08 May 2016 11:17:03 -0000 ------------08F0CA0FC2C071DDA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: base64 SGVsbG8gTWF0dGhldywNCg0KU3VuZGF5LCBNYXkgOCwgMjAxNiwgMTo1NjowMCBQTSwgeW91 IHdyb3RlOg0KDQo+PiAgICBEbyB5b3UgY29uc2lkZXIgbmV3IEludGVsIE5WTSAiM0QgWFBv aW50IiB0ZWNobm9sb2d5PyBUaGV5KHRtKSBwcm9taXNlDQo+PiAgcHJpY2VzIGxvd2VyIHRo YW4gRFJBTSwgYnV0IGhpZ2hlciB0aGFuIFNTRC4gQW5kIHNhbWUgZm9yIHNwZWVkLiBMb29r cw0KPj4gIGxpa2UsIHRoZXJlIHdpbGwgYmUgVEhSRUUgbGF5ZXJzIG9mIE5WTSBpbiBuZWFy IGZ1dHVyZTogdmVyeSBsYXJnZSBhbmQgc2xvdw0KPj4gIChIREQsIGlTQ1NJL0ZDIGF0dGFj aGVkICJzaGVsZiIsIHRoaW5ncyBsaWtlIHRoaXMsIG11bHRpdGVyYWJ5dGUpLCBTU0QNCj4+ ICAoaW4gMS0xMCB0ZXJhYnl0ZSByYW5nZSkgYW5kIHRoaXMgWFBvaW50IGluIGN1cnJlbnQg U1NEIHJhbmdlLg0KPiAzRCBYLVBvaW50IGlzIG9ubHkgc29tZXRoaW5nIGxpa2UgYSBmYWN0 b3Igb2YgMzB4IHNsb3dlciB0aGFuIGN1cnJlbnQNCj4gRFJBTSBtb2R1bGVzICh3aGljaCBp cyB0byBzYXkgdGhvdXNhbmRzIG9mIHRpbWVzIGZhc3RlciB0aGFuIGV4aXN0aW5nDQo+IEZs YXNoIG1vZHVsZXMpLCBhbmQgSSBiZWxpZXZlIEludGVsIGFyZSBwbGFubmluZyBvbiBzZWxs aW5nIGl0IHBhY2thZ2VkDQo+IGFzIERJTU1zIGFzIHdlbGwgYXMgUENJeCBOVk1FIGRldmlj ZXMuDQogICAib25seSAzMHggc2xvd2VyIiBpcyBub3QgIm9ubHkiLiAiTWVtb3J5IGlzIGEg bmV3IGRpc2siIGlzIHZlcnkgbWFudHJhIG9mDQogaGlnaC1wZXJmb3JtYW5jZSBwcm9ncmFt bWluZywgYW5kIGFkZGl0aW9uYWwgIjMweCBzbG93ZXIiIGlzIGEga2lsbGVyLA0KIHJlYWxs eS4gWW91IHdpbGwgbmVlZCB0byBoYXZlIERSQU0tbWVtb3J5IGNhY2hlIGFueXdoZXJlLCBv ciB5b3VyIENQVSB3aWxsDQogd2FpdCBmb3IgSS9PIGZvcmV2ZXIuIEFuZCBzaXplcyB3aWxs IG5vdCBiZSBzdWNoIGJpZyB0byBzdG9yZSBhbGwgZGF0YSBpbg0KIHRoaXMgbWVtb3J5LCB0 b28uDQoNCiAgU28sIElNSE8sIGl0IGlzIHN0aWxsIGhpZXJhcmNoeSBvZiAocGVyc2lzdGVu dCkgY2FjaGVzIC0tIG5vbi1wZXJzaXN0ZW50DQogUkFNLCB2ZXJ5IGZhc3QgbmV3IE5WUkFN LCBmYXN0IGJsb2NrIGRldmljZSAoU1NEKSwgZXRjLg0KDQogIEFuZCB0aGlzIG1lbW9yeSBp biBESU1NIGZvcm0tZmFjdG9yIGlzIHZlcnkgZGlmZmVyZW50IHN0b3J5LiBBbGxvY2F0aW5n DQogcGFnZXMgZm9yIHN0YWNrLCBkYXRhLCBjb2RlIG9mICJvcmRpbmFyeSIgcHJvY2Vzc2Vz IChhbmQga2VybmVsIG5lZWRzKSBvbg0KIGl0IGJlY2F1c2UgaXQgaXMgaW4gY29tbW9uIFJB TSBhZGRyZXNzIHNwYWNlPyBSaWRpY3Vsb3VzLiBJdCBpcyBzbG93LCBpdCBpcw0KIHZhbHVh YmxlIGFuZCBhbGwgImdlbmVyaWMiIGFsbG9jYXRpb25zIGluIFZNIChhbGwgYWxsb2NhdGlv bnMgd2UgaGF2ZQ0KIHRvZGF5ISkgZG9lc24ndCBiZWxvbmcgdG8gaXQgZm9yIHN1cmUuIFdo YXQgd291bGQgd2UgZG8/IEkgZG9uJ3Qga25vdy4gT1Nlcw0KIG5lZWQgbmV3IEFQSSBmb3Ig ZGF0YWJhc2VzIGFuZCBzdWNoIHRvIGdpdmUgdGhlbSBhY2Nlc3MgdG8gdGhpcyBtZW1vcnks IGl0DQogZG9lc24ndCBsb29rIGxpa2UgY3VycmVudCAidGhpcyBpcyBoZWFwIiBhbmQgInRo aXMgaXMgZmlsZXN5c3RlbSINCiBhYnN0cmFjdGlvbnMgd29yayB3ZWxsIGhlcmUuDQoNCi0t IA0KQmVzdCByZWdhcmRzLA0KIExldiAgICAgICAgICAgICAgICAgICAgICAgICAgICBtYWls dG86bGV2QEZyZWVCU0Qub3Jn ------------08F0CA0FC2C071DDA Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJXLyAoXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePNOcQAN1djkHRHiT2W6psCFPJnGUQ LSnNjM9ZuF1uByQXFnjmoAmwUJZR6MI1SIntytPpuhgzdv8UW+zeXtMIijyfVAZ4 sW7Mb2BB6FmTYfZ//JIt5hxL24DCo76U3ftA6Y01/DNEO1bPo4GHAXaBXXj0191P Ch2eeVsVY40AVhN2VsHdZ9xZebsvyPFQmOZH1hmn+558RmUIdgifVGddaPG5JT4P PDyTG6YXVXN9F6xgCPHeAnCARb6otHKH5/FUuftpL6bWhlGT3LViU8LeZajqacmI nQy52FuQU0TjAEtsu3kCQk1IrMgEMKJa9hTuI+HO/0ktQybzePsE9WVpJq9EFof2 Ge98RSEM+2vctMaa4ZR8D2NutbZkD0GGo+tUzcQqvO42PKk2ZEH1b3utfuRLOMqJ jEWxYsICznOvUnB1C7GrFJ7l0GF0DQhTXKYAwPf7df2B5oqp5qdChphtxbSJG7p7 fHOdgaD9R0Oaovs93mXvh6CJnNKy06RUjJiOQBfPfvUeHgCFwIxFVlgpH+pzm0Fs wgqwOXExw20Uuy+3UrHoi6zsabesjsGk6q8SHavR+TiNCXwzyl/e1y7qZUjzeY2y st90y7iKcEkeoUkgte1qhL6zlh2dit1deQ1AJOkPDxKRLWei2eouV00pujgAf72Q ah9rtn3Ps6APCyIQsQGw =oRi8 -----END PGP MESSAGE----- ------------08F0CA0FC2C071DDA-- From owner-freebsd-fs@freebsd.org Sun May 8 15:18: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 1DB82B32BFF for ; Sun, 8 May 2016 15:18: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 0E7B61A5F for ; Sun, 8 May 2016 15:18: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 u48FIXaA098554 for ; Sun, 8 May 2016 15:18:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 208691] "panic: ffs_valloc: dup alloc" as soon as UFS root partition is mounted Date: Sun, 08 May 2016 15:18: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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: martinwguy@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug 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, 08 May 2016 15:18:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208691 --- Comment #5 from Martin Guy --- An alternative to prevent the observed behaviour, of rebooting continually, would be to always fully fsck the filesystem when it is dirty, rather than = the current fsck -p behaviour of replaying the journal and applying simpler che= cks. I'm not sure a new "filesystem panic flag" would help, as there's not a lot= of difference between the state the FS can be left in after to a kernel panic = and when it stops due to a power failure. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun May 8 16:09: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 57BFCB337B3 for ; Sun, 8 May 2016 16:09:38 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 23F211F71 for ; Sun, 8 May 2016 16:09:37 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1azRGp-0008D1-S7 for freebsd-fs@freebsd.org; Sun, 08 May 2016 18:09:28 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-fs@freebsd.org Subject: Re: [Bug 208691] "panic: ffs_valloc: dup alloc" as soon as UFS root partition is mounted References: Date: Sun, 08 May 2016 18:09:27 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: a8ecdd0179e5342c74548fafd5461917 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, 08 May 2016 16:09:38 -0000 On Sun, 08 May 2016 17:18:34 +0200, wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208691 > > --- Comment #5 from Martin Guy --- > An alternative to prevent the observed behaviour, of rebooting > continually, > would be to always fully fsck the filesystem when it is dirty, rather > than the > current fsck -p behaviour of replaying the journal and applying simpler > checks. > > I'm not sure a new "filesystem panic flag" would help, as there's not a > lot of > difference between the state the FS can be left in after to a kernel > panic and > when it stops due to a power failure. > Maybe it is interesting if you know the panic originated in an inconsistent filesystem. Ronald. From owner-freebsd-fs@freebsd.org Sun May 8 16:22:56 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 AD0C4B33AEF for ; Sun, 8 May 2016 16:22:56 +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 9D96817A7 for ; Sun, 8 May 2016 16:22:56 +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 u48GMuCn077409 for ; Sun, 8 May 2016 16:22:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 208691] "panic: ffs_valloc: dup alloc" as soon as UFS root partition is mounted Date: Sun, 08 May 2016 16:22: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: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug 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, 08 May 2016 16:22:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208691 --- Comment #6 from Kirk McKusick --- You suggest ``An alternative to prevent the observed behaviour, of rebooting continually, would be to always fully fsck the filesystem when it is dirty, rather than the current fsck -p behaviour of replaying the journal and appl= ying simpler checks.'' To get this behavior, turn off journalling using the command: tunefs -j disable /filesystem/to/disable When the system finds a clean filesystem at boot, it skips fsck. When the system finds a dirty filesystem at boot and no journal, it runs a full fsck. You note ``I'm not sure a new "filesystem panic flag" would help, as there's not a lot of difference between the state the FS can be left in after to a kernel panic and when it stops due to a power failure.'' When a panic occurs, the filesystem code never gets another chance to run, = thus there is no way for it to set a `filesystem panic'ed flag'. The only indica= tion of something unexpected having happened is the absence of a `filesystem cle= anly unmounted flag'. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun May 8 18:33: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 C5E23B33D77 for ; Sun, 8 May 2016 18:33:45 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B25C11A42 for ; Sun, 8 May 2016 18:33:45 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: by mailman.ysv.freebsd.org (Postfix) id B1B88B33D76; Sun, 8 May 2016 18:33:45 +0000 (UTC) Delivered-To: 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 B15DEB33D75 for ; Sun, 8 May 2016 18:33:45 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F2DD1A41; Sun, 8 May 2016 18:33:45 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1azTWR-0005jf-CN; Sun, 08 May 2016 20:33:43 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: fs@freebsd.org, "Lev Serebryakov" Subject: Re: ZFS hierathy, snapshots and backup tool -- how to traverse snapshotted tree properly? References: <886527019.20160508140221@serebryakov.spb.ru> Date: Sun, 08 May 2016 20:33:40 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <886527019.20160508140221@serebryakov.spb.ru> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 2c269fdec788119c0964d98755c55204 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, 08 May 2016 18:33:45 -0000 On Sun, 08 May 2016 13:02:27 +0200, Lev Serebryakov wrote: > Hello Fs, > > I'm writing some backup tool (yet another, don't ask!) and encounter > some > "inconvenience" in ZFS snapshot system, for which I don't see good > solution > (all I could imagine is kludgy and ugly). Maybe, there is some approach > I > didn't notice or some ZFS-specific API I should now? > > Lets say, here is some hierarchy of ZFS file systems. For example, I > will > use "/home" which have one filesystem per user: > > zpool/home/user1 -> /home/user1 > zpool/home/user2 -> /home/user2 > zpool/home/user3 -> /home/user3 > > But it could be much more complex hierarchy. > > Now, we have backup tool, which works with filesystem tree. If I want to > backup all my users, I could setup it to backup "/home" and everything > works even if users will be added (or removed) in future. > > But STOP! We want to backup snapshot, if our filesystem supports > snapshots! It is good idea! ZFS supports snapshot! > > It is easy to teach backup tool to call > > zfs snapshot -r ${backup_root}@${randomname} > > at beginning and > > zfs destroy -r ${backup_root}@${randomname} > > at the end of the process. No problems here. > > Problems are, how backup tool should TRAVERSE snapshotted directory > tree > now? > > Simple "go to ${backup_root}/.zfs/${randomname}" DOESN'T WORK! Because > /home/.zfs/${randomname} does not contain user directories. They are > separate FSes and have separate paths for their snapshots. Traversing > "live" tree but getting data from snapshots is not proper way to do > this, > for sure, as it is depreciate whole idea of snapshots. > > Is here good solution for this problem? > > Of course, it is possible to configure each FS for backup tool > one-by-one, > but I don't like this solution, as in ZFS world there could be very > deep > and nested FS hierarchies. Also, configuring each FS separately in > backup > tool configuration leads to forgotten FSes in long-term maintenance for > sure. > I have used a monitoring tool like Nagios to periodically check if all filesystems are configured in the backup tool and vice versa. Ronald. From owner-freebsd-fs@freebsd.org Sun May 8 20:10: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 91719B33F1D for ; Sun, 8 May 2016 20:10: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 827FB1BD0 for ; Sun, 8 May 2016 20:10: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 u48KAXKn055477 for ; Sun, 8 May 2016 20:10:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 9619] [nfs] Restarting mountd kills existing mounts Date: Sun, 08 May 2016 20:10:33 +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: 3.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal 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, 08 May 2016 20:10:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D9619 --- Comment #11 from commit-hook@freebsd.org --- A commit references this bug: Author: rmacklem Date: Sun May 8 20:10:23 UTC 2016 New revision: 299242 URL: https://svnweb.freebsd.org/changeset/base/299242 Log: Make "-S" a default option for mountd. After a discussion on freebsd-fs@ there seemed to be a consensus that the "-S" option for mountd should become the default. Since the only known issue w.r.t. using "-S" was fixed by r299201, this commit adds "-S" to the default mountd_flags. Discussed on: freebsd-fs PR: 9619, 131342, 206855 MFC after: 2 weeks Relnotes: yes Changes: head/etc/defaults/rc.conf --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun May 8 20:10: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 2CD69B33F33 for ; Sun, 8 May 2016 20:10: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 1D20D1BF1 for ; Sun, 8 May 2016 20:10: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 u48KAbKu055618 for ; Sun, 8 May 2016 20:10:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 131342] [nfs] mounting/unmounting of disks causes NFS to fail Date: Sun, 08 May 2016 20:10:38 +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: 7.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: Normal 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, 08 May 2016 20:10:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D131342 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: rmacklem Date: Sun May 8 20:10:23 UTC 2016 New revision: 299242 URL: https://svnweb.freebsd.org/changeset/base/299242 Log: Make "-S" a default option for mountd. After a discussion on freebsd-fs@ there seemed to be a consensus that the "-S" option for mountd should become the default. Since the only known issue w.r.t. using "-S" was fixed by r299201, this commit adds "-S" to the default mountd_flags. Discussed on: freebsd-fs PR: 9619, 131342, 206855 MFC after: 2 weeks Relnotes: yes Changes: head/etc/defaults/rc.conf --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun May 8 21:00: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 5FF0EB33F86 for ; Sun, 8 May 2016 21:00:48 +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 250961BBD for ; Sun, 8 May 2016 21:00:48 +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 u48L0186058769 for ; Sun, 8 May 2016 21:00:48 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201605082100.u48L0186058769@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, 08 May 2016 21:00:48 +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, 08 May 2016 21:00:48 -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 | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f 4 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Sun May 8 23:50: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 AF1C0B33C5A for ; Sun, 8 May 2016 23:50:43 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from vms173021pub.verizon.net (vms173021pub.verizon.net [206.46.173.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9659D1AD2 for ; Sun, 8 May 2016 23:50:43 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from vz-proxy-m003.mx.aol.com ([64.236.83.2]) by vms173021.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0O6V00LABRFXAA40@vms173021.mailsrvcs.net> for freebsd-fs@freebsd.org; Sun, 08 May 2016 17:50:26 -0500 (CDT) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=WpDWSorv c=1 sm=1 tr=0 a=EDCZS3Slg7tGr17y9w9vtg==:117 a=yrkiwgmsf1kA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=vWrOAUsZxBf9V1wrjssA:9 a=QEXdDO2ut3YA:10 a=XfjFEbw-H6gUT74DNbEA:9 a=cst8Gz9rkyu-I9JR:21 a=_W_S_7VecoQA:10 Received: by 100.1.241.90 with SMTP id 4daacc55; Sun, 08 May 2016 22:50:26 GMT To: freebsd-fs From: "Mikhail T." Subject: df displays total space incorrectly... sometimes Message-id: <08073f39-4f37-9258-f40d-44ffb3e0e777@aldan.algebra.com> Date: Sun, 08 May 2016 18:50:21 -0400 MIME-version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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: Sun, 08 May 2016 23:50:43 -0000 Hello! I have a pair of systems (foo and bar) mounting each other's ZFS shares. One on of them I recently started getting errors from some applications complaining about disk being full. An examination with `df -m' on the NFS client (foo) revealed: bar:/bar 353010 922208 -569198 261% /bar The same `df -m' run on the server shows: bar 4547314 922208 3625105 20% /bar Note, that the Used-column (second) matches. Note also, that the Total column on the NFS-client is remainder of the real value seen on the server. Hex makes this easier to see: % printf '%X %X\n' 4547314 353010 4562F2 562F2 The difference is exactly 0x400000. If it were df itself messing up the number, it would've done the same thing on the server as well. What's broken on the client side? I don't think, I saw this, when I first switched to ZFS (and giant storage-sizes with it) from multiple single drives. But the recent kernel (foo is running 10.3 from April 18) displays this behavior... Things work fine in the other direction, where bar is the client and foo is the server: foo:/foo 4778760 919 4777840 0% /foo The kernel on bar is from today (10.3 as of May 8th) -- was this problem fixed in the three weeks between these dates? Thanks! -mi From owner-freebsd-fs@freebsd.org Mon May 9 06:26: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 17100B34FB7 for ; Mon, 9 May 2016 06:26:34 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EE5861D06 for ; Mon, 9 May 2016 06:26:33 +0000 (UTC) (envelope-from peter@rulingia.com) Received: by mailman.ysv.freebsd.org (Postfix) id EA465B34FB6; Mon, 9 May 2016 06:26:33 +0000 (UTC) Delivered-To: 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 E7BF6B34FB5 for ; Mon, 9 May 2016 06:26:33 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 858611D03; Mon, 9 May 2016 06:26:32 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vps.rulingia.com (8.15.2/8.15.2) with ESMTPS id u496PbFO012458 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 9 May 2016 16:25:43 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id u496PV9a024022 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 9 May 2016 16:25:32 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id u496PSlf024021; Mon, 9 May 2016 16:25:28 +1000 (AEST) (envelope-from peter) Date: Mon, 9 May 2016 16:25:28 +1000 From: Peter Jeremy To: Lev Serebryakov Cc: Poul-Henning Kamp , George Neville-Neil , fs@freebsd.org Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories Message-ID: <20160509062528.GB57227@server.rulingia.com> References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> <62925.1462704459@critter.freebsd.dk> <1058947919.20160508140842@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline In-Reply-To: <1058947919.20160508140842@serebryakov.spb.ru> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.6.0 (2016-04-01) X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-4.4.3 (vps.rulingia.com [103.243.244.15]); Mon, 09 May 2016 16:25:45 +1000 (AEST) 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, 09 May 2016 06:26:34 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2016-May-08 14:08:47 +0300, Lev Serebryakov wrote: >Hello Poul-Henning, > >Sunday, May 8, 2016, 1:47:39 PM, you wrote: > >> The problem with that kind of hardware is that either you specialize >> 100% for that vendors product, with resulting lock-in, or you satisfy >> yourself with a generic solution which works an anything sensible. > >> I don't think FreeBSD has the bandwidth for anything but the second opti= on. > > Really, Intel is not "that vendor" now. It is THE Vendor. FreeBSD has a = LOT >of specialization for this vendor (all i386 code, NVMe, and other), and ma= ny >thing from Intel (or which becomes widespread in Intel-based systems, like >PCI, which is not exactly "from Intel", of course) becomes industrial >standard. There's a difference between FreeBSD having i386/amd64 as the main Tier-1 platform and supporting hardware that is only supported by some (not even all) x86 CPUs manufactured by Intel. There are a number of other vendors that supply i386/amd64-compatible CPUs. Whilst we do have CPU-specific code (for CPU initialisation and hwpmc), there's a big step between that and supporting a filesystem that requires vendor-specific hardware and a vendor-specific CPU. > I don't think such type of memory will be very-Intel-specific for long. HP >works on something comparable, and other companies too. "Something comparable" doesn't mean it'll be compatible - Intel have a vested interest in locking customers into their CPUs. And the hype surrounding "The Machine" has been toned down significantly - suggesting that HP are having a harder time productizing their NVM than they expected. --=20 Peter Jeremy --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXMC1YXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0XAIQAIRWSAas0E6a6Kzt9irEgSPP hFoiQMzdvBSUgPMwMs6gwURd5ezWLnvFojgHx8AZ+Be9ycs/bqV4PY52VWj0LBLp xkbx67DZfxjNTp3WfhFzGsnikQ9aRfb3e3aKyo8ISjMP/QmB1kLnk+cmEAXXIJUg xeESXtZcX+Rw799vqXpKVG1h0de47+8urQXQ5HEq4JkPz31nB00oFOAjssWY1U9o zbp54igEHzb8kkF8T0bLfBiBZQ4+s/qi4+staT3oSnNzFTbu7cqfaCTK78ecZlQt vhL9GCZOMG3MnBa/p67I1vEDFN/cZdQJL9yyQJ6mNgdR0FF/884hmc+L4EVzw4Gi dcK1m3uBUNDGHzhxqS90mS+ZgmQGtmJ7aYDBJMCyrQ3mhsFEfP9iFlHIusVCrv6P WsmaHQCNWlGr3aEhwqkH1f+Qmxf9w+9inbQMsSj2QY7+bGck7GoryZM72hX9agVu WjtZd4QWJRp+n+Zj2M5YKPR5hqN2QyUhjn+neTsx96ZJlSa+Mfn4RRCebhK/jfBh cee2b4S79fA5ObDYeaxMpBIwYnJLWgiiuUwrXwTDgmy/vDOwUXO9OjIkMnUpxd87 yiUSGFgSEetSAFnHtWwj7O1/eXG+Uv/+5hLYNhXdVl0RzR1sxrZKLtNIZwuMCSIS d19myfHoqVN788Mx7AcM =XVCz -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9-- From owner-freebsd-fs@freebsd.org Mon May 9 12:21:23 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 377CCB337D1 for ; Mon, 9 May 2016 12:21:23 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 17612168C for ; Mon, 9 May 2016 12:21:23 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 169D1B337D0; Mon, 9 May 2016 12:21:23 +0000 (UTC) Delivered-To: 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 09ACDB337CF for ; Mon, 9 May 2016 12:21:23 +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 83DFA1689 for ; Mon, 9 May 2016 12:21:22 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [127.0.0.1] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 4529F58C; Mon, 9 May 2016 15:21:15 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> <62925.1462704459@critter.freebsd.dk> <1058947919.20160508140842@serebryakov.spb.ru> <20160509062528.GB57227@server.rulingia.com> To: Peter Jeremy Cc: Poul-Henning Kamp , George Neville-Neil , fs@freebsd.org From: Lev Serebryakov Organization: FreeBSD Message-ID: <573080B4.1030708@FreeBSD.org> Date: Mon, 9 May 2016 15:21:08 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160509062528.GB57227@server.rulingia.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MmQ39RK2BM05nkt045q0OHjV4P9kGqUKN" 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, 09 May 2016 12:21:23 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MmQ39RK2BM05nkt045q0OHjV4P9kGqUKN Content-Type: multipart/mixed; boundary="FfrCPXPLnCelbVfmfMdqBtk4WIk1FMXCk" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: Peter Jeremy Cc: Poul-Henning Kamp , George Neville-Neil , fs@freebsd.org Message-ID: <573080B4.1030708@FreeBSD.org> Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> <62925.1462704459@critter.freebsd.dk> <1058947919.20160508140842@serebryakov.spb.ru> <20160509062528.GB57227@server.rulingia.com> In-Reply-To: <20160509062528.GB57227@server.rulingia.com> --FfrCPXPLnCelbVfmfMdqBtk4WIk1FMXCk Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 09.05.2016 09:25, Peter Jeremy wrote: > There's a difference between FreeBSD having i386/amd64 as the main Tier= -1 > platform and supporting hardware that is only supported by some (not ev= en > all) x86 CPUs manufactured by Intel. NVMe cards will not be supported on other platforms?! Or DIMMs will be really not standard-complaint DIMMs but something other? --=20 // Lev Serebryakov --FfrCPXPLnCelbVfmfMdqBtk4WIk1FMXCk-- --MmQ39RK2BM05nkt045q0OHjV4P9kGqUKN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXMIC7XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePWfoQALmYtd4tS2obzwvuJxVLoAzi 1nobZR9vgl0eeG9FdLaqiG9fek9oFBqDX4RU9PSfvWF8nQHxZ6w5dqEtqobrd4qQ HDTi1CxGNocsHWsh9teHC7iIX6sP0a6RahrHn/Wt+PjdT6xH/7A/FgwptSC/4F+5 /Zf8BzxjnyPrUpp1uYfXbAhSuuiZbHxUNzbbY2mygVn7U4em4di/0gQgXhmkc2Yd NId5YYylbR/XWh0Ih3Q2R4S+ZW6Q7Z6CcCOhgIDU2vYBYnzGAb99oFecSFkCdZbL dvCnVccTsRWqH/dXJsA810iQNU5pxFhZwZsfUg4OxlEKhfbZGH5V/CmBBq9PJ4Dr +SJOeiBgls+SucHKvPTFN+9XViB8zFHoVbzE6mkAtKRxDr75H5TZWRwwauW5S4+u DRareq0pmMzi4jZlLjMlGh7Fb39WffNcv6+vyZtTwCgQBH9+pHBM3yOia69wfik1 f100r5Jzo4HGe/eUkxLoVYwLMnGRyN2ahH/kIb4+6e1x2OLDBEilXcnqp56diT3p KuuFqaNJYhuAPm6K+Crr6eNBECyj3BjypHWRXEuYudyRxLZTWlcDfGv8gVAxCoiP ilN8+1pNJD5GoCz9a2yQfgnoyz/BHS485DCf9DK0BWELyeljXQiIc8vGrRvLZ4eT BwKDtwsPPmKxfXHbekTY =Y93+ -----END PGP SIGNATURE----- --MmQ39RK2BM05nkt045q0OHjV4P9kGqUKN-- From owner-freebsd-fs@freebsd.org Mon May 9 17:15: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 19564B3482F for ; Mon, 9 May 2016 17:15:31 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0AF4D119C for ; Mon, 9 May 2016 17:15:31 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 04D7C1629 for ; Mon, 9 May 2016 17:15:31 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id B03881CB7B for ; Mon, 9 May 2016 17:15:30 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id tGgX4A_VopFu for ; Mon, 9 May 2016 17:15:28 +0000 (UTC) To: freebsd-fs@freebsd.org DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 23F221CB76 From: Bryan Drewery Subject: NFS inuse vnode sillyrename with > 1 links Organization: FreeBSD Message-ID: Date: Mon, 9 May 2016 10:15:27 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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, 09 May 2016 17:15:31 -0000 The context for this is in https://reviews.freebsd.org/D6254 with some discussion already. First my use-case: cd some_nfs_dir/ mkdir src dst touch src/foo ln src/foo dst/foo tail -F dst/foo & rm -rf src/ This fails in rm/FTS (Directory not empty) in rmdir(1) since the removal of src/foo renames it to src/.nfs*. Then FTS tries to rmdir not realizing there is a new file. My real use-case is building Python in a temporary directory, hardlinking it into a staging directory (for running from without polluting /). I then run the staging version of python for the rest of the build. If I try to rebuild Python while something else is running the hard-linked Python from the staging directory then the Python build fails since it is trying to rm -Rf a directory that just got a silly rename, even though I was executing a different named link. I understand that a vnode inuse count is on the vnode and not the name, but in this case I expect rm -Rf to just work since I wasn't running the link being deleted. Implementation complexities and history aside, this should just work, even if it means a hack to FTS/rm rather than nfs_remove. It makes no sense from a user-perspective and has no sane workaround except to not hardlink or use userland r/w locking to avoid removing a binary in-use. So to NFS. I know nothing about the protocol or history. I just know that in this case it seems fine to not do a silly rename on a file if it has multiple links, since the vnode will still be around to be used by the kernel for in-use consumers. --=20 Regards, Bryan Drewery From owner-freebsd-fs@freebsd.org Mon May 9 20:04:10 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 3FCDDB3408C for ; Mon, 9 May 2016 20:04:10 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id D08A6131F; Mon, 9 May 2016 20:04:08 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:VCItMh+dIQrDT/9uRHKM819IXTAuvvDOBiVQ1KB91OMcTK2v8tzYMVDF4r011RmSDdSdsqgP0rGJ+4nbGkU+or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6anHS+4HYoFwnlMkItf6KuSt+U1p78jrvts7ToICx2xxOFKYtoKxu3qQiD/uI3uqBFbpgL9x3Sv3FTcP5Xz247bXianhL7+9vitMU7q3cYk7sb+sVBSaT3ebgjBfwdVWx+cjN92Mq+nwPSRA3HymERTWgMg1IcCQTf4Q73RIbZnDH3u8BG9G+dJ8KgHp4uXjH31aZgS1fNgSwEMzM8uDXNj8V7j6ZWpTq8oBNizorMYMeePawtLevmYdoGSD8ZDY5qXCtbD9b5NtNXAg== X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CtBADN7DBX/61jaINdhA19BrkegXYXC4UkSgKBchMBAQEBAQEBAWQngi2CFAEBAQMBAQEBICsgCwULAgEIDgoCAg0ZAgInAQkmAgQIBwQBHASIAggOrj2QbwEBAQEBAQEDAQEBAQEBAQEUBHyFJIF+gk6EIgEBgxuCWQWNXopEhX2FMZIFjzkCIgE/ggUbgWcgMgeHQQkXBBt/AQEB X-IronPort-AV: E=Sophos;i="5.24,601,1454994000"; d="scan'208";a="282483673" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-annu.net.uoguelph.ca with ESMTP; 09 May 2016 16:04:07 -0400 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 6BE5D15F58C; Mon, 9 May 2016 16:04:07 -0400 (EDT) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id pB-v1sAszYHH; Mon, 9 May 2016 16:04:06 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id D872815F58D; Mon, 9 May 2016 16:04:06 -0400 (EDT) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7qQ_UVCRIKea; Mon, 9 May 2016 16:04:06 -0400 (EDT) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id C051B15F58C; Mon, 9 May 2016 16:04:06 -0400 (EDT) Date: Mon, 9 May 2016 16:04:06 -0400 (EDT) From: Rick Macklem To: Bryan Drewery Cc: freebsd-fs@freebsd.org Message-ID: <11118918.93955875.1462824246725.JavaMail.zimbra@uoguelph.ca> In-Reply-To: References: Subject: Re: NFS inuse vnode sillyrename with > 1 links MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF46 (Win)/8.0.9_GA_6191) Thread-Topic: NFS inuse vnode sillyrename with > 1 links Thread-Index: 1p9B1EZQSzWBIWONWsQBAI1ulZmTPw== 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, 09 May 2016 20:04:10 -0000 Bryan Drewery wrote: > The context for this is in https://reviews.freebsd.org/D6254 with some > discussion already. > > First my use-case: > > cd some_nfs_dir/ > mkdir src dst > touch src/foo > ln src/foo dst/foo > tail -F dst/foo & > rm -rf src/ > > This fails in rm/FTS (Directory not empty) in rmdir(1) since the removal > of src/foo renames it to src/.nfs*. Then FTS tries to rmdir not > realizing there is a new file. > > My real use-case is building Python in a temporary directory, > hardlinking it into a staging directory (for running from without > polluting /). I then run the staging version of python for the rest of > the build. If I try to rebuild Python while something else is running > the hard-linked Python from the staging directory then the Python build > fails since it is trying to rm -Rf a directory that just got a silly > rename, even though I was executing a different named link. I > understand that a vnode inuse count is on the vnode and not the name, > but in this case I expect rm -Rf to just work since I wasn't running the > link being deleted. Implementation complexities and history aside, this > should just work, even if it means a hack to FTS/rm rather than > nfs_remove. Unfortunately, NFS is not (and cannot be) a POSIX compliant file system since it does not have a POSIX open. As such, certain POSIX behaviour cannot "just work". The "silly rename" trick is an attempt to more closely approximate POSIX behaviour, but it cannot always work. The discussion under the phabricator review (especially jhb@'s recent comment) I believe does cover how modifying the "silly rename trick" could break other cases. I noted in the phabricator discussion that I did not know if this change should be done or not. I did express concern, since the current (without this patch) semantic has been in place for over 20years (probably close to 30years) and a change in semantics might result in a POLA violation. It may be preferable to come up with a patch for FTS, if your use case can be fixed that way. rick > It makes no sense from a user-perspective and has no sane > workaround except to not hardlink or use userland r/w locking to avoid > removing a binary in-use. > > So to NFS. I know nothing about the protocol or history. I just know > that in this case it seems fine to not do a silly rename on a file if it > has multiple links, since the vnode will still be around to be used by > the kernel for in-use consumers. > > -- > Regards, > Bryan Drewery > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Tue May 10 08:18: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 75646B344F2 for ; Tue, 10 May 2016 08:18:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6679B1CC9 for ; Tue, 10 May 2016 08:18:18 +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 u4A8IHqp027263 for ; Tue, 10 May 2016 08:18:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207464] Panic when destroying ZFS snapshot Date: Tue, 10 May 2016 08:18:18 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: avg@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, 10 May 2016 08:18:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207464 --- Comment #20 from Andriy Gapon --- (In reply to Howard Powell from comment #17) Thank you for the fix. I'll update the patch. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue May 10 08:18:56 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 80B5AB345AA for ; Tue, 10 May 2016 08:18:56 +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 71DD31E3F for ; Tue, 10 May 2016 08:18:56 +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 u4A8ItdE028177 for ; Tue, 10 May 2016 08:18:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207464] Panic when destroying ZFS snapshot Date: Tue, 10 May 2016 08:18: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: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: avg@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, 10 May 2016 08:18:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207464 --- Comment #21 from Andriy Gapon --- (In reply to Howard Powell from comment #19) I meant the code without the patch. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue May 10 08:19: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 0F540B34637 for ; Tue, 10 May 2016 08:19: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 007561EE7 for ; Tue, 10 May 2016 08:19: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 u4A8Ja2g029103 for ; Tue, 10 May 2016 08:19:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207464] Panic when destroying ZFS snapshot Date: Tue, 10 May 2016 08:19:36 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@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: Tue, 10 May 2016 08:19:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207464 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-fs@FreeBSD.org Assignee|freebsd-fs@FreeBSD.org |avg@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue May 10 09:37: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 4EA2DB340F0 for ; Tue, 10 May 2016 09:37: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 2E6101E62 for ; Tue, 10 May 2016 09:37: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 u4A9b6AI003001 for ; Tue, 10 May 2016 09:37:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207464] Panic when destroying ZFS snapshot Date: Tue, 10 May 2016 09:37:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created 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, 10 May 2016 09:37:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207464 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #170024|0 |1 is obsolete| | --- Comment #22 from Andriy Gapon --- Created attachment 170172 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D170172&action= =3Dedit proposed patch for testing --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue May 10 20:04:32 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 F3BC3B36E31 for ; Tue, 10 May 2016 20:04:31 +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 E4F3F12A2 for ; Tue, 10 May 2016 20:04:31 +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 u4AK4UCS018320 for ; Tue, 10 May 2016 20:04:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207464] Panic when destroying ZFS snapshot Date: Tue, 10 May 2016 20:04:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: karl@denninger.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@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, 10 May 2016 20:04:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207464 --- Comment #23 from karl@denninger.net --- I am running the patch at the present time -- so far no panics, but my regu= lar workload usually requires a few days (often as much as a week) before it happens. If my backup routine detects an "aw crap" (which usually comes before it go= es "boom") I'll advise. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed May 11 20:23: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 745DAB37206 for ; Wed, 11 May 2016 20:23:36 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5676E1FA7 for ; Wed, 11 May 2016 20:23:36 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Message-ID:Subject:To:From:Date:Content-Transfer-Encoding: Content-Type:MIME-Version:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=nb0dKl+n4iuqF3eJZa6e8cDPvsR9cQnJneWXBkLuOZY=; b=pozaj87gnzV5FMqUYRW2CUMvEA VWvnJKlq3Wni7Pqu3HborNf/DRRQMdrqK0uXwbEFNqXkMkcoxXKC9rmn29wpIITRRrBEzxbizjo/l hIotNUhjxOiHg8m4GlVoDE3qAvSZoADXGWKwQ+r1HUws1Ehm2wjZQgJ/LMMhfFlhAATY=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:23734 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b0afP-000IXj-Ep for freebsd-fs@freebsd.org; Wed, 11 May 2016 15:23:35 -0500 Received: from proxy.na.alcatel-lucent.com ([135.245.48.71]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Wed, 11 May 2016 15:23:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 11 May 2016 15:23:35 -0500 From: Larry Rosenman To: Freebsd fs Subject: ZFS/Duplicated ZAP? Message-ID: <0df84959a28476a61654a9d4893f3f11@thebighonker.lerctr.org> X-Sender: ler@lerctr.org User-Agent: Roundcube Webmail/1.1.4 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, 11 May 2016 20:23:36 -0000 What can I do to fix these? A scrub does not. From looking at comments where this is generated, seems like it maybe dedupe related. Rebuilding the pool is NOT an option at present. thebighonker.lerctr.org /home/ler $ grep -i zfs /var/log/messages May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libssl.a). May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libzpool.so). May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libtinfo_p.a). May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry detected (libumem.so). thebighonker.lerctr.org /home/ler $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From owner-freebsd-fs@freebsd.org Wed May 11 20:31: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 A755FB376AA; Wed, 11 May 2016 20:31:47 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87E1E199B; Wed, 11 May 2016 20:31:47 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=13BThe9DMA5I7EinHuW0585s0jVRI1t+YJ9qouFGKYk=; b=vdMsVhzB+Ty6QXSUYIzSQNtEqj JBBYeuq4IQW23QvWRJ0PpAbkRkPOFcENJegESMXY5AqYSSiRK8WWmb0CoXEw2p8l8QOKwE+N5vOVF SbD4C2CkXMKSkcCI750o04ng6OiPYZZ2qByikFCGnryvN0zEfByhCqPh4/utbrSKXbu8=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:17547 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b0anK-000InB-VE; Wed, 11 May 2016 15:31:47 -0500 Received: from proxy.na.alcatel-lucent.com ([135.245.48.71]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Wed, 11 May 2016 15:31:46 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 11 May 2016 15:31:46 -0500 From: Larry Rosenman To: Freebsd fs Cc: owner-freebsd-fs@freebsd.org Subject: Re: ZFS/Duplicated ZAP? In-Reply-To: <0df84959a28476a61654a9d4893f3f11@thebighonker.lerctr.org> References: <0df84959a28476a61654a9d4893f3f11@thebighonker.lerctr.org> Message-ID: <2f38a63e226d1f88f68af69725111b85@thebighonker.lerctr.org> X-Sender: ler@lerctr.org User-Agent: Roundcube Webmail/1.1.4 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, 11 May 2016 20:31:47 -0000 On 2016-05-11 15:23, Larry Rosenman wrote: > What can I do to fix these? A scrub does not. From looking at > comments where this is > generated, seems like it maybe dedupe related. Rebuilding the pool is > NOT an option at present. > > thebighonker.lerctr.org /home/ler $ grep -i zfs /var/log/messages > May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libssl.a). > May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libzpool.so). > May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libtinfo_p.a). > May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry > detected (libumem.so). > thebighonker.lerctr.org /home/ler $ I had dedup on originally, but have since turnef it off, but... thebighonker.lerctr.org /home/ler $ zfs get -r all zroot|grep ded zroot dedup off local zroot/ROOT dedup off inherited from zroot zroot/ROOT/default dedup off inherited from zroot zroot/ezjail dedup off inherited from zroot zroot/ezjail/basejail dedup off inherited from zroot zroot/ezjail/lists.austiniot.com dedup off inherited from zroot zroot/ezjail/newjail dedup off inherited from zroot zroot/ezjail/portal.metro25.com dedup off inherited from zroot zroot/home dedup off inherited from zroot zroot/home/ler dedup off inherited from zroot zroot/home/mrm dedup off inherited from zroot zroot/pg-data dedup off inherited from zroot zroot/tmp dedup off inherited from zroot zroot/usr dedup off inherited from zroot zroot/usr/local dedup off inherited from zroot zroot/usr/obj dedup off inherited from zroot zroot/usr/ports dedup off inherited from zroot zroot/usr/src dedup off inherited from zroot zroot/var dedup off inherited from zroot zroot/var/crash dedup off inherited from zroot zroot/var/log dedup off inherited from zroot zroot/var/tmp dedup off inherited from zroot thebighonker.lerctr.org /home/ler $ uname -aKU FreeBSD thebighonker.lerctr.org 10.3-STABLE FreeBSD 10.3-STABLE #40 r299365: Tue May 10 09:14:53 CDT 2016 root@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64 1003501 1003501 thebighonker.lerctr.org /home/ler $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From owner-freebsd-fs@freebsd.org Fri May 13 03:45: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 9045CB38F6A for ; Fri, 13 May 2016 03:45:37 +0000 (UTC) (envelope-from bounce@imagemail.eu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 703511EED for ; Fri, 13 May 2016 03:45:37 +0000 (UTC) (envelope-from bounce@imagemail.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 6F604B38F67; Fri, 13 May 2016 03:45:37 +0000 (UTC) Delivered-To: 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 6C8A4B38F65 for ; Fri, 13 May 2016 03:45:37 +0000 (UTC) (envelope-from bounce@imagemail.eu) Received: from server.imagemail.eu (server.imagemail.eu [51.254.123.47]) by mx1.freebsd.org (Postfix) with ESMTP id E63541EEB for ; Fri, 13 May 2016 03:45:36 +0000 (UTC) (envelope-from bounce@imagemail.eu) Received: by server.imagemail.eu (Postfix, from userid 500) id BFE5539CD48; Fri, 13 May 2016 06:40:20 +0300 (EEST) DKIM-Filter: OpenDKIM Filter v2.10.3 server.imagemail.eu BFE5539CD48 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imagemail.eu; s=default; t=1463110820; bh=gcHFH/3vnIZhlVRCI22fDqCAD3G5uXX1LsmX30JZxrQ=; h=To:Subject:Date:From:Reply-To:From; b=fF9I6s4P1jfYtnzVoOBSxqj5/jf5DHwEx2UDK3iJM8fv+LTF1Z3Y4vnS9MYDEsvsO 4l9Qa5809Y5VxoH3YRfmbkGWLSkLcnSfE4fjJjyEbdumGZfbM4184UJ8PHh0IhU9/L rpT97KB0xmhQx93+eFdTS+EpApYlccAZyEb8MVMl98NfH599d8tB4V3WNSmvV6MpYr p1VrJrfme/ZVQjt7mcAbWe6fEF3TvsgS8OplYf7KZwoNr1HByJNYFhEwLWpcnr2sQD szWFXGzCpvjA0NpqGiZson6ibEK/dw96yIr60GpKRC86rdkOxtdZBYto1nV5DTWLa8 kAgCg3hfqMTdw== To: Fs Subject: =?utf-8?B?zqbOuc67zr/Ovs61zr3Or86xIM65z4PPhM6/z4POtc67zq/OtM6xz4Igzro=?= =?utf-8?B?zrHOuSDOus6xz4TOv8+Hz43Pgc+Jz4POtyDOv869z4zOvM6xz4TOv8+CIM6z?= =?utf-8?B?zrnOsSDPjM67zr/Phc+CICEhIQ==?= X-PHP-Originating-Script: 500:class.phpmailer.php DKIM-Signature: v=1; a=rsa-sha1; q=dns/txt; l=66345; s=acy; t=1463110820; c=relaxed/simple; h=from:to:subject; d=imagemail.eu; bh=M0kfq8k3wNj2mQAn9hH8Wr/gBJ4=; b=RvlS/x4skeX2foMuoJrESiz069l4sHlifgsU7X9gRIjsrhjNDWyL3GYVJypI mDS0Zo/SmQ+aZmv65m5IAqdy0pgsLK8zvu3oEPZtcEnvvsEBvtsL2xvbIfbS nvTES7EPMxa610zpgGUbfyBi+nl9utvbexTVUbSxTGAb0yxk12k= Date: Fri, 13 May 2016 05:40:02 +0200 From: IMAGE Advertising Email Makreting Reply-To: IMAGE Advertising Email Makreting Message-ID: X-Mailer: PHPMailer 5.2.11 (https://github.com/PHPMailer/PHPMailer/) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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, 13 May 2016 03:45:37 -0000 Φιλοξενία ιστοσελίδας & ​Κατοχύρωση ονόματος Εύκολα και οικονομικά !!! ​Έχετε ιστοσελίδα και πληρώνετε πολλά για τη φιλοξενία της; Τότε δείτε τις ΕΚΠΛΗΚΤΙΚΕΣ προσφορές μας... Φιλοξενία ιστοσελίδας: 3 € / μήνα Κατοχύρωση ονόματος: 10 € / χρόνο Η ιστοσελίδα σας φορτώνει αργά και δεν έχει επισκέπτες; Τότε ελάτε στην IMAGE που σας προσφέρει... * Φιλοξενία σε ταχύτατους Ευρωπαϊκούς Servers * Βελτιστοποίηση για κορυφαία αποτελέσματα στην Google * Καθημερινά αντίγραφα ασφαλείας των δεδομένων σας * 20ετή εμπειρία στο χώρο του internet Δεν χρειάζεται να κάνετε τίποτε... Ένα τηλεφώνημα ή ένα email μόνο αρκεί και ξεγνιάσατε. Αναλαμβάνουμε εμείς όλη τη διαδικασία μεταφοράς της ιστοσελίδας σας σε εμάς. Επικοινωνήστε στο 6946-270217 ή στο hosting@imagemail.eu ΣΥΝΕΧΙΖΟΥΜΕ ΤΗ ΦΙΛΟΞΕΝΙΑ ΣΑΣ ... ΔΩΡΕΑΝ !!! Έχετε ήδη συνδρομή σε κάποια άλλη εταιρία και δεν θέλετε να χάσετε χρήματα; Ενημερώστε μας για την υπάρχουσα συνδρομή σας, και μέχρι να λήξει το τρέχον συμβόλαιό σας Εμείς θα φιλοξενούμε την σελίδα σας ΔΩΡΕΑΝ !!! IMAGE Διαφημιστική Κερκύρας 23 Ιωάννινα Τηλ: 26510 68500 ​ Διαγραφή από τη λίστα ( http://imagemail.eu/index.php?subid=1&option=com_acymailing&ctrl=user&task=out&mailid=43&key=MNcWJRzzqeQup7 ) From owner-freebsd-fs@freebsd.org Fri May 13 15:19: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 7AAA0B396AD for ; Fri, 13 May 2016 15:19:38 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A6D81D12 for ; Fri, 13 May 2016 15:19:38 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Message-ID:References:In-Reply-To:Subject:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=FbeWQG9kyagDECOgQCfO6aHjYP7Co7AaN9xctv8eCco=; b=XjZ/GIeD9IiweGqOIFf4oc4gxf HIPJs7rVRuG1DAeKkMAN8wTp5V+lCZ7+wtymln7jYNMBsvncC3hY6O/aquIvqfVO4gd36oetbeLiv DKYu83nwd9k97LAaMcfTCAgKbo/r3HRQQWtas2wILOspU3gUQ6rojnVSuBJuxfYmJdn0=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:17780 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b1EsL-000Cg0-Nu for freebsd-fs@freebsd.org; Fri, 13 May 2016 10:19:37 -0500 Received: from proxy.na.alcatel-lucent.com ([135.245.48.84]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Fri, 13 May 2016 10:19:37 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 13 May 2016 10:19:37 -0500 From: Larry Rosenman To: Freebsd fs Subject: Re: ZFS/Duplicated ZAP? In-Reply-To: <2f38a63e226d1f88f68af69725111b85@thebighonker.lerctr.org> References: <0df84959a28476a61654a9d4893f3f11@thebighonker.lerctr.org> <2f38a63e226d1f88f68af69725111b85@thebighonker.lerctr.org> Message-ID: <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org> X-Sender: ler@lerctr.org User-Agent: Roundcube Webmail/1.1.4 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, 13 May 2016 15:19:38 -0000 Anyone? On 2016-05-11 15:31, Larry Rosenman wrote: > On 2016-05-11 15:23, Larry Rosenman wrote: >> What can I do to fix these? A scrub does not. From looking at >> comments where this is >> generated, seems like it maybe dedupe related. Rebuilding the pool is >> NOT an option at present. >> >> thebighonker.lerctr.org /home/ler $ grep -i zfs /var/log/messages >> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 00:07:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 00:10:50 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 00:15:05 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 00:24:38 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 00:24:54 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 00:42:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:01:00 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:01:04 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:02:07 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:03:21 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:04:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:05:11 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:07:33 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:17:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libssl.a). >> May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libzpool.so). >> May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libtinfo_p.a). >> May 11 03:24:32 thebighonker kernel: ZFS WARNING: Duplicated ZAP entry >> detected (libumem.so). >> thebighonker.lerctr.org /home/ler $ > > I had dedup on originally, but have since turnef it off, but... > > thebighonker.lerctr.org /home/ler $ zfs get -r all zroot|grep ded > zroot dedup > off local > zroot/ROOT dedup > off inherited from zroot > zroot/ROOT/default dedup > off inherited from zroot > zroot/ezjail dedup > off inherited from zroot > zroot/ezjail/basejail dedup > off inherited from zroot > zroot/ezjail/lists.austiniot.com dedup > off inherited from zroot > zroot/ezjail/newjail dedup > off inherited from zroot > zroot/ezjail/portal.metro25.com dedup > off inherited from zroot > zroot/home dedup > off inherited from zroot > zroot/home/ler dedup > off inherited from zroot > zroot/home/mrm dedup > off inherited from zroot > zroot/pg-data dedup > off inherited from zroot > zroot/tmp dedup > off inherited from zroot > zroot/usr dedup > off inherited from zroot > zroot/usr/local dedup > off inherited from zroot > zroot/usr/obj dedup > off inherited from zroot > zroot/usr/ports dedup > off inherited from zroot > zroot/usr/src dedup > off inherited from zroot > zroot/var dedup > off inherited from zroot > zroot/var/crash dedup > off inherited from zroot > zroot/var/log dedup > off inherited from zroot > zroot/var/tmp dedup > off inherited from zroot > thebighonker.lerctr.org /home/ler $ uname -aKU > FreeBSD thebighonker.lerctr.org 10.3-STABLE FreeBSD 10.3-STABLE #40 > r299365: Tue May 10 09:14:53 CDT 2016 > root@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64 > 1003501 1003501 > thebighonker.lerctr.org /home/ler $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From owner-freebsd-fs@freebsd.org Fri May 13 15:28: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 50AE8B399A7 for ; Fri, 13 May 2016 15:28:45 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (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 D5EB71157 for ; Fri, 13 May 2016 15:28:44 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id CAE5070DB for ; Fri, 13 May 2016 15:28:40 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/CAE5070DB; dkim=none; dkim-atps=neutral Subject: Re: ZFS/Duplicated ZAP? To: freebsd-fs@freebsd.org References: <0df84959a28476a61654a9d4893f3f11@thebighonker.lerctr.org> <2f38a63e226d1f88f68af69725111b85@thebighonker.lerctr.org> <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org> From: Matthew Seaman Message-ID: Date: Fri, 13 May 2016 16:28:31 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BE8Wgxw7gJr81tetaxvqGVXNUa8RWCS41" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk 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, 13 May 2016 15:28:45 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BE8Wgxw7gJr81tetaxvqGVXNUa8RWCS41 Content-Type: multipart/mixed; boundary="1VCT3GEom1vGG6csPna5CA3gHWdTvCgm8" From: Matthew Seaman To: freebsd-fs@freebsd.org Message-ID: Subject: Re: ZFS/Duplicated ZAP? References: <0df84959a28476a61654a9d4893f3f11@thebighonker.lerctr.org> <2f38a63e226d1f88f68af69725111b85@thebighonker.lerctr.org> <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org> In-Reply-To: <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org> --1VCT3GEom1vGG6csPna5CA3gHWdTvCgm8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 05/13/16 16:19, Larry Rosenman wrote: > Anyone? >=20 > On 2016-05-11 15:31, Larry Rosenman wrote: >> On 2016-05-11 15:23, Larry Rosenman wrote: >>> What can I do to fix these? A scrub does not. From looking at >>> comments where this is >>> generated, seems like it maybe dedupe related. Rebuilding the pool i= s >>> NOT an option at present. >>> >>> thebighonker.lerctr.org /home/ler $ grep -i zfs /var/log/messages >>> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entr= y >>> detected (libssl.a). >>> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entr= y >>> detected (libzpool.so). >>> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entr= y >>> detected (libtinfo_p.a). >>> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entr= y >>> detected (libumem.so). You could try doing a zfs send ... | zfs recv ... to create a new copy of the affected ZFSes. This should pretty much unwind any effect of having had deduplication turned on. Then it's a matter of using 'zfs rename' to move the new copy into the expected locations in your zfs hierarchy and have them mount at the correct places in your filesystem. That's something you'll almost certainly need to do while booted from a live CD or similar. Cheers, Matthew --1VCT3GEom1vGG6csPna5CA3gHWdTvCgm8-- --BE8Wgxw7gJr81tetaxvqGVXNUa8RWCS41 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXNfKgAAoJEABRPxDgqeTnX7wQAKXtpw/m1qH8WDwf11NzSXYY KbCmK+eXjDTMsXmLvF+xXIy04D8ofNlaTTwhXU//xi8nDkGXeFD8087KMn9stQ7u RtS5INpm5PXh4HDrZlhlwmVmtju59W8T+brcwF/RzEHlB02Z0XgQe/4gBPiQtVRy fEYjtYv1oYSwxz/etRszBVHImpPSXavMswfABJi7smvPWJ7hXkLeLAhE3BrhWvzk IqGGy0S0qkL39Zp2o98K2vVdIY7Sy3+U+Zug4Cb1pxN2eJGbmTPPREC+5jcCsZ5P +/eWx+x2j5vVxCsudy7WcZtPjv6jUyguxVGgZ8fPCxEPFjhUtl2YZJu0UMOvrVso MQW/MQQoIVyZ1gI6IEQCtfQCoijXsIRRqy1rQ4xrrwWbD2bjSbJONg9CiXOAEQpY yLXDq39EqmKdrFTAxErwzG4s7xBWX3uGLp6sSmUDjPE1pPNgRpTsfeFjGHnxhT53 yGrucq1doYL+2xHfBi9soR/W1NYlOK2xIFPR1KI3yGGsyiVDnGpWk46HmjqboLnt SKjuBxHIvLSFoApAYqEEEmPoiGmjOkkzMgTZQEtP/hCo+KMviMg25yejDfgvtMks 4ESrfF3CKbEYy48VbEFX3k7qFDIBNfoYJUEXz8HLv1Yz4TdTwcPZ8qeOXJgfiMRY fBnKt3HoZzKUrcC2f5BY =LnbW -----END PGP SIGNATURE----- --BE8Wgxw7gJr81tetaxvqGVXNUa8RWCS41-- From owner-freebsd-fs@freebsd.org Sat May 14 08:54:17 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 4BAB8B395B4 for ; Sat, 14 May 2016 08:54:17 +0000 (UTC) (envelope-from quazinode@gmail.com) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8621167D for ; Sat, 14 May 2016 08:54:16 +0000 (UTC) (envelope-from quazinode@gmail.com) Received: by mail-lb0-x229.google.com with SMTP id ww9so25892478lbc.2 for ; Sat, 14 May 2016 01:54:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=7gugMKFgihjrMC7EPodQ/h2Ud3oQTyDhJNevpkdONIY=; b=qXaXqUICEM6SfLv5Ws56w1jUk2FhswQUv4l7dTh/ehr0jRkHkHI5TjVr+U5ZFThMmR W5CHNF+bZbGT4CIcemaNbCMpb9LXSA4K0niOPakGZzwsFOgwywTik6GI727j45IGY8CN xsPaupsYDWMlZH2hFd0gkERXVQmzAX8uqR1h9z5Ryon40RYmkgk1VaXONdlgcv872GXS QNqIKFe3KQlzK/vs6cydazEW6FBkU8wjUFZXQD+XcNhIFSRotujDMFUlPv0cOw0Loi26 LojpjfTugiz3qSRiT67qShWQg9i7Fs5S/FnPa9EXQt5v5auh/r+762kMKmd6iR5aFkWQ Sf7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=7gugMKFgihjrMC7EPodQ/h2Ud3oQTyDhJNevpkdONIY=; b=LzPllHnEntPLMKQysjaKfGldAu1GvCcoQS2V7ZTHOp7H3ddfSw6UGGf90qC1vj3wlW yg7s5MTv/TcCSxerbkbCI+k9Ygs8lt8UrJKoJj3bMU6QdMHFZAe1y+XR8KUgPD4scC8b 3vMkKxuy4LEDOGOfJkmoboSsN/ntxvXzAQ+18J7wKS/Ef5o2n7rPy8RMq6MXIdjtB/HT 0Uidpq0oYdA4xDX8gVLYDudfUo+ZrmoKeY/cX/pSuHZH2fLYAzbi/Bf8Lg8/KQwAq6ul d9yRBWu0hsZlvf19sskV/3o03z44xuEvcKVMDGmhlyw/D0XVQgG48Dw/ZgJSfg24KhUq 4nlw== X-Gm-Message-State: AOPr4FVjK8K+rFvH+DqCqik21fMNvQQjbh8eYvSamDTFXaLk7LLA6tQLtavmA83NdDhcxw== X-Received: by 10.112.154.5 with SMTP id vk5mr8477002lbb.126.1463216054575; Sat, 14 May 2016 01:54:14 -0700 (PDT) Received: from [192.168.0.104] ([46.216.17.194]) by smtp.gmail.com with ESMTPSA id o79sm3541113lfe.18.2016.05.14.01.54.13 for (version=TLSv1/SSLv3 cipher=OTHER); Sat, 14 May 2016 01:54:13 -0700 (PDT) To: freebsd-fs@freebsd.org From: Ruslan Yakauleu Subject: State of native encryption in ZFS Message-ID: <5736E7B4.1000409@gmail.com> Date: Sat, 14 May 2016 11:54:12 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 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: Sat, 14 May 2016 08:54:17 -0000 Hi all! I wish to know somethign new about native encryption in ZFS for FreeBSD. Any works in this direction are conducted? -- Best regards, Ruslan Yakauleu From owner-freebsd-fs@freebsd.org Sat May 14 12:44: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 4660DB39416; Sat, 14 May 2016 12:44:04 +0000 (UTC) (envelope-from mikej@mikej.com) Received: from mx2.paymentallianceintl.com (mx2.paymentallianceintl.com [216.26.158.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx2.paymentallianceintl.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DB6B1E61; Sat, 14 May 2016 12:44:03 +0000 (UTC) (envelope-from mikej@mikej.com) Received: from firewall.mikej.com (f [162.230.214.65]) by mx2.paymentallianceintl.com (8.15.1/8.15.1) with ESMTPS id u4EChtmR016929 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 14 May 2016 08:43:55 -0400 (EDT) (envelope-from mikej@mikej.com) X-Authentication-Warning: mx2.paymentallianceintl.com: Host f [162.230.214.65] claimed to be firewall.mikej.com Received: from mail.mikej.com (firewall.mikej.com [192.168.6.63]) by firewall.mikej.com (8.15.2/8.15.2) with ESMTP id u4EChr1F064848; Sat, 14 May 2016 08:43:53 -0400 (EDT) (envelope-from mikej@mikej.com) DMARC-Filter: OpenDMARC Filter v1.3.1 firewall.mikej.com u4EChr1F064848 Authentication-Results: mail.mikej.com; dmarc=none header.from=mikej.com DKIM-Filter: OpenDKIM Filter v2.10.3 firewall.mikej.com u4EChr1F064848 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mikej.com; s=mail; t=1463229834; bh=doMO+/+5qf7LD8WRq1RSfdGKm1Enia9R5xbXb/woIhU=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=HTMlNKQL2/2tOLzqJ0vWxPva5SJBNWJwb0NKuDO+n1HlN5Zh9QqvKdPhb0ecQ8I98 FbQskNAdJopp58VGaWp5CvNZg3PEAhv9s9kmNmGlzfxBJIv7GN2PMjpyD4jzZeKycy aeZQDYOOmIz5YBpIkAh+F4LP3EsyMVuR6rrz+yydWoJxY+I9/RyoEmneY8KXzgh5KY pPMInNjaZhs8s0t8utZ1lrcqi8Dv1kIwcqGdp27E9MQ8emgK/ul+usaOjTZQYIZvCo Qo1pjcJ/C+q1KpiGYC91tYuRbNAf4Jk285ZSdOcxvZR8wo5p++uA4MshUytAPq9DKi Zl0K7XfNQLRzg== X-Authentication-Warning: firewall.mikej.com: Host firewall.mikej.com [192.168.6.63] claimed to be mail.mikej.com MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 14 May 2016 08:43:51 -0400 From: Michael Jung To: Ruslan Yakauleu Cc: freebsd-fs@freebsd.org, owner-freebsd-fs@freebsd.org Subject: Re: State of native encryption in ZFS In-Reply-To: <5736E7B4.1000409@gmail.com> References: <5736E7B4.1000409@gmail.com> Message-ID: X-Sender: mikej@mikej.com User-Agent: Roundcube Webmail/1.1.5 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, 14 May 2016 12:44:04 -0000 On 2016-05-14 04:54, Ruslan Yakauleu wrote: > Hi all! > > I wish to know somethign new about native encryption in ZFS for > FreeBSD. > Any works in this direction are conducted? I have been using encryption under ZFS for several years without any issue. Note that if your processor does not support AES-NI you will take a CPU hit as encryption will not be hardware excelerated. From owner-freebsd-fs@freebsd.org Sat May 14 13:02:09 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 C319EB398A0 for ; Sat, 14 May 2016 13:02:09 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 5CF8C1713 for ; Sat, 14 May 2016 13:02:09 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: by mail-lf0-x234.google.com with SMTP id j8so99616892lfd.2 for ; Sat, 14 May 2016 06:02:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to; bh=bmL61pXYm2Gzd3IvigPv9IriPDARnOJxkc//7OOIJbc=; b=A/zfAo+dR6RgcvIOcv0MVrVdYKFkFiK2zk/Wy0ivIb5LOSa8OGWX9bcw2X8ChOGybC x1z/8hzBio/g9sJPAlaFZFYlh7dbFLRYqhiyZbXn612AiVtiiEYQ7sdndYl8IPJ40u35 wcXrPW969j/yTcsW9IlYfc7ZAPWUZ/mGLW6zZcO55PeCGREpXx6dK83jzu4G3oSqasTT 1sOT4zKvA6Msa/5KGKiz+g85ILLhHmzS1XJUVnWKE7FjvumoKTPhvudkElseYYPs8Irg M3gBJdunUkFYOGZEzHfLOxIKQfzGr8klV1QOCAcu/CZjWEH1eLA5Z8JujZruqucLG/6l in6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to; bh=bmL61pXYm2Gzd3IvigPv9IriPDARnOJxkc//7OOIJbc=; b=PYtLjNV5hF0qw+rP/BsReGNVb/3HRiXEeEGMUmFJmG9KNPT/byJlNfJtvj4lMNSFoG iFC65LJ+ZkQYMz/yCG7jGrp7r1FwTP6caTf7ke2vqYXL2PnCVT1hxDpeBx74tGq003xC WgLdndVXm9aGJx68qqSiylJ+6BL32tiHTTR43iBYrgRBg9XK2/Kb2BpfWvryz1NMxr6f TScBZYZvmQPq8IsUbZs5SNf48VI4orJl9HNbqzwUVdPZbKHYC0qnOOlk/+mwkeXUkR2K VSvWMYAWlMRq5ywgpmRUT6kJvvOcG8BwNxfgTsZIqVsibZJc3xAfRw2/Rk1uvsVmBzsD r3/g== X-Gm-Message-State: AOPr4FWUlS4IxzSK/XXSx96jZYxO9wxcAU913pC3J7YDod0bVYxkT5dJJwYZuYJo+AGSSx1jnDSEq6ONdZq9FQ== MIME-Version: 1.0 X-Received: by 10.25.64.212 with SMTP id n203mr8909893lfa.54.1463230927236; Sat, 14 May 2016 06:02:07 -0700 (PDT) Sender: thomas.e.zander@googlemail.com Received: by 10.25.21.84 with HTTP; Sat, 14 May 2016 06:02:07 -0700 (PDT) In-Reply-To: References: <5736E7B4.1000409@gmail.com> Date: Sat, 14 May 2016 15:02:07 +0200 X-Google-Sender-Auth: btrFOKYK7YHNfUDDA9qeYb3tjP8 Message-ID: Subject: Re: State of native encryption in ZFS From: Thomas Zander To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 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, 14 May 2016 13:02:09 -0000 On 14 May 2016 at 14:43, Michael Jung wrote: > On 2016-05-14 04:54, Ruslan Yakauleu wrote: >> >> Hi all! >> >> I wish to know somethign new about native encryption in ZFS for FreeBSD. >> Any works in this direction are conducted? > > I have been using encryption under ZFS for several years without any issue. Op was probably referring to encryption being integrated into the ZFS data pipeline, not on top of geli/gdbe: http://open-zfs.org/wiki/Projects#Platform_agnostic_encryption_support In Oracle Solaris this is available, see http://www.oracle.com/technetwork/articles/servers-storage-admin/manage-zfs-encryption-1715034.html IIRC this work has started before Oracle took over Sun, but it has not been open sourced yet. I'd be very surprised to see something like this hit the tree anytime soon. Best regards Riggs From owner-freebsd-fs@freebsd.org Sat May 14 18:03: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 AA3E1B39EE1 for ; Sat, 14 May 2016 18:03:07 +0000 (UTC) (envelope-from jkh@mail.turbofuzz.com) Received: from barracuda.ixsystems.com (barracuda.ixsystems.com [12.229.62.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 90FC01B47 for ; Sat, 14 May 2016 18:03:07 +0000 (UTC) (envelope-from jkh@mail.turbofuzz.com) X-ASG-Debug-ID: 1463248986-08ca045f6814edc0001-3nHGF7 Received: from zimbra.ixsystems.com ([10.246.0.20]) by barracuda.ixsystems.com with ESMTP id kY5XJrrheEuyXSZf (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 14 May 2016 11:03:06 -0700 (PDT) X-Barracuda-Envelope-From: jkh@mail.turbofuzz.com X-Barracuda-RBL-Trusted-Forwarder: 10.246.0.20 X-ASG-Whitelist: Client Received: from localhost (localhost [127.0.0.1]) by zimbra.ixsystems.com (Postfix) with ESMTP id 42945C89106; Sat, 14 May 2016 11:03:06 -0700 (PDT) Received: from zimbra.ixsystems.com ([127.0.0.1]) by localhost (zimbra.ixsystems.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id eB5Ptb9bsLOo; Sat, 14 May 2016 11:03:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zimbra.ixsystems.com (Postfix) with ESMTP id C789CC8910F; Sat, 14 May 2016 11:03:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at ixsystems.com Received: from zimbra.ixsystems.com ([127.0.0.1]) by localhost (zimbra.ixsystems.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yyRsT45QjbpO; Sat, 14 May 2016 11:03:05 -0700 (PDT) Received: from [172.20.0.10] (vpn.ixsystems.com [10.249.0.2]) by zimbra.ixsystems.com (Postfix) with ESMTPSA id 9C0C9C89106; Sat, 14 May 2016 11:03:05 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of native encryption in ZFS From: Jordan Hubbard X-ASG-Orig-Subj: Re: State of native encryption in ZFS In-Reply-To: <5736E7B4.1000409@gmail.com> Date: Sat, 14 May 2016 11:03:05 -0700 Cc: freebsd-fs@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0CE6E456-CC25-4AED-A73E-F5BBE659F795@mail.turbofuzz.com> References: <5736E7B4.1000409@gmail.com> To: Ruslan Yakauleu X-Mailer: Apple Mail (2.3124) X-Barracuda-Connect: UNKNOWN[10.246.0.20] X-Barracuda-Start-Time: 1463248986 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://10.246.0.26:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 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, 14 May 2016 18:03:07 -0000 > On May 14, 2016, at 1:54 AM, Ruslan Yakauleu = wrote: >=20 > I wish to know somethign new about native encryption in ZFS for = FreeBSD. > Any works in this direction are conducted? Short and simple answer: No. We also recently talked to Matt Ahrens (essentially the OpenZFS = =E2=80=9Cproject lead=E2=80=9D and who determines what goes upstream) at = the FreeBSD Storage Summit and he expressed very little interest in = =E2=80=9Cnative encryption=E2=80=9D for ZFS, seeing little to no benefit = (for what would be a lot of engineering work) in doing it at the ZFS = layer vs simply continuing to use the GELI encryption at the = block-device layer that FreeBSD already supports. It=E2=80=99s not even clear how that encryption would be implemented or = exposed. Per pool? Per dataset? Per folder? Per file? There have = been requests for all of the above at one time or another, and the key = management challenges for each are different. They can also be = implemented at a layer above ZFS, given sufficient interest. - Jordan From owner-freebsd-fs@freebsd.org Sat May 14 18:26:40 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 D8FE2B3B345 for ; Sat, 14 May 2016 18:26:40 +0000 (UTC) (envelope-from quazinode@gmail.com) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E6B214A8 for ; Sat, 14 May 2016 18:26:40 +0000 (UTC) (envelope-from quazinode@gmail.com) Received: by mail-lb0-x229.google.com with SMTP id h1so37205867lbj.3 for ; Sat, 14 May 2016 11:26:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=revg84caSsGHSLHDMcpU/qmOzvM/lN6g4+UfSMm2Nho=; b=iXWCTT3HgKs5Yb93hevoF1anKAJ9KzBA02cpWfppvP5hN4NndEt702DtcN0fm919iH x2GjwzYDAv33LLCNRlHojc/5LnfWQgHu4p/Dz4YlAoKwpBcB2/t92NihNFv89g1BGiO9 frLIbjdwoCDeL/KdnLlcuyTl+msiOoBC8hnhm2bkAlaNe4qi66iGrVNDQof5aP7Xnj1T VdBatZiiAA4SFfpAh14tPlFEiWl0WFV9n1UXS0qZV5vS1zmDATGrl6jP/3Y2sK0Zb4hu iwj7iragEn98i+DrGU7oDWSuOxDVh8U42I3kaqHDC1cRsjDMhxLlFLDXOn657nMKwD38 Q8/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=revg84caSsGHSLHDMcpU/qmOzvM/lN6g4+UfSMm2Nho=; b=FE1JXUn3ZPeIQtr3G3btULzbuL7yoYmb90gyHA0teZ8vylyG6tUA4FlXwQhSXmkDtI Ad3IdazVkYvJjarj7DnMNnwXOLR3+R5C6UQVWUJU2EZgkjnxTFirPLsuHnU/mocwLSqk 4co1MXbhkC/qt2Lqz/k9FjH6p/B1z+NYLVC5C0Ux3P75qgZi3pOdHDUl+XK5zMoIYV10 67FX5FLIX7RCJRDOMkoPYYphhY68AGXkHIfGsqkjj5YGdNRuQfUUbuT2AB7Cw++M7AdN +n0XwwY9pOx23oNatH2mOCV4K4TNSV/XZzJxxV+pp+BiiNtAOCjSIZW2iT1/ic2/XKbZ jjfw== X-Gm-Message-State: AOPr4FU82zYWSdJ9NRW1sMXZGCvUtGpemQpjl/ilFLiqFqPwDP17J18PXPo7XlrPXvMubg== X-Received: by 10.112.160.231 with SMTP id xn7mr5056814lbb.4.1463250398357; Sat, 14 May 2016 11:26:38 -0700 (PDT) Received: from [192.168.0.104] ([46.216.17.194]) by smtp.gmail.com with ESMTPSA id q1sm3786851lbo.4.2016.05.14.11.26.36 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 14 May 2016 11:26:37 -0700 (PDT) Subject: Re: State of native encryption in ZFS To: Jordan Hubbard References: <5736E7B4.1000409@gmail.com> <0CE6E456-CC25-4AED-A73E-F5BBE659F795@mail.turbofuzz.com> Cc: freebsd-fs@freebsd.org From: Ruslan Yakauleu Message-ID: <57376DDB.9070409@gmail.com> Date: Sat, 14 May 2016 21:26:35 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <0CE6E456-CC25-4AED-A73E-F5BBE659F795@mail.turbofuzz.com> Content-Type: text/plain; charset=utf-8; format=flowed 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: Sat, 14 May 2016 18:26:40 -0000 On 14.05.2016 21:03, Jordan Hubbard wrote: >> On May 14, 2016, at 1:54 AM, Ruslan Yakauleu wrote: >> >> I wish to know somethign new about native encryption in ZFS for FreeBSD. >> Any works in this direction are conducted? > Short and simple answer: No. > > We also recently talked to Matt Ahrens (essentially the OpenZFS “project lead” and who determines what goes upstream) at the FreeBSD Storage Summit and he expressed very little interest in “native encryption” for ZFS, seeing little to no benefit (for what would be a lot of engineering work) in doing it at the ZFS layer vs simply continuing to use the GELI encryption at the block-device layer that FreeBSD already supports. > > It’s not even clear how that encryption would be implemented or exposed. Per pool? Per dataset? Per folder? Per file? There have been requests for all of the above at one time or another, and the key management challenges for each are different. They can also be implemented at a layer above ZFS, given sufficient interest. > > - Jordan > It is sad. Solution with GELI can't be moved to other machine if some troubles come. Or to other OS. Or from other OS (from Solaris with native encryption, from Linux with LUKS). Too many time need to return any data from HDD if something happens. Also reliability decreased too (more refusal points). I hope in the future ZFS will be one of most stable and portable FS. Best regards, Ruslan Yakauleu From owner-freebsd-fs@freebsd.org Sat May 14 20:20:21 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 44CB8B3BEAD for ; Sat, 14 May 2016 20:20:21 +0000 (UTC) (envelope-from s_sourceforge@nedprod.com) Received: from mail.nedprod.com (europe4.nedproductions.biz [213.251.186.177]) (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 EF1151AA2 for ; Sat, 14 May 2016 20:20:20 +0000 (UTC) (envelope-from s_sourceforge@nedprod.com) Received: from authenticated-user (mail.nedprod.com [213.251.186.177]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.nedprod.com (Postfix) with ESMTPSA id 3172315932 for ; Sat, 14 May 2016 21:13:59 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nedprod.com; s=mail; t=1463256839; bh=QjBGX/yTmJqmcAhGDKnzyPmWcg3xMoRQ3mp66fj81pk=; h=From:To:Date:Subject:In-reply-to:References:From; b=eE2WzNZlvBQ6zm7f3n3zEPYOzvwt2d9hlmU7Ov/53SSg02DCNYrfoUKDMslVSX303 4gVYCRYAz+z7wu4zRACcZN5i0JHrwu8Rj9+LcldQhNIwlECWZcvGLkgAAxzNpspvvv 4gtZ7VTLDzLFETZqris/NLRBCLBqnBAmRoKMj3O6cj63CNgFf2HxhEUI85MUBwCQo4 23HDSUOew7JgrkNbGVtjFcMdOaPNSS8CaWq6bCCwgtOpSEKLkJ/MPXySvwDN78asCB wMadtMHnj8jV0wSONudE6z433fwJLBrkdk3w16RmgoIcIhDzHGJowWQnQG59opu9Nv NKCuSJcOqVEqQ== From: "Niall Douglas" To: freebsd-fs@freebsd.org Date: Sat, 14 May 2016 21:13:59 +0100 MIME-Version: 1.0 Subject: Re: State of native encryption in ZFS Message-ID: <57378707.19425.B54772B@s_sourceforge.nedprod.com> Priority: normal In-reply-to: <0CE6E456-CC25-4AED-A73E-F5BBE659F795@mail.turbofuzz.com> References: <5736E7B4.1000409@gmail.com>, <0CE6E456-CC25-4AED-A73E-F5BBE659F795@mail.turbofuzz.com> X-PM-Encryptor: IDWSM-PM32, 4 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="SMime-=-=-Boundary-=-=-F1A5CA31" 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, 14 May 2016 20:20:21 -0000 --SMime-=-=-Boundary-=-=-F1A5CA31 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: Quoted-printable Content-Description: Mail message body On 14 May 2016 at 11:03, Jordan Hubbard wrote: > It=E2=80=99s not even clea= r how that encryption would be implemented or exposed. > Per pool? Per da= taset? Per folder? Per file? There have been > requests for all of the a= bove at one time or another, and the key > management challenges for each a= re different. They can also be > implemented at a layer above ZFS, given s= ufficient interest. If FreeBSD had a bigger PATH_MAX then stackable encryp= tions layers like ecryptfs (encfs?) would be viable choices. Because encry= pted path components are so long, one runs very rapidly into the maximum p= ath on the system when PATH_MAX is so low. I ended up actually installing Z= FS on Linux with ecryptfs on top to solve this. Every 15 minutes it ZFS sn= apshot syncs with the FreeBSD edition. This works very well, apart from th= e poor performance of ZFS on Linux. ZFS handles long paths with ease. FreeB= SD currently does not :( Niall -- ned Productions Limited Consulting http://w= ww.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/ --SMime-=-=-Boundary-=-=-F1A5CA31 Content-Type: application/x-pkcs7-signature; name=SMime.p7s Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=SMime.p7s MIIY1AYJKoZIhvcNAQcCoIIYxTCCGMECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3 DQEHAaCCFYIwggY0MIIEHKADAgECAgEgMA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNV BAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBD ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAyNTVaFw0xNzEwMjQy MTAyNTVaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEr MCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGll bnQgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDLKIVFnAEs+xny q6UzjCqgDcvQVe1dIoFnRsQPCFO+y92k8RK0Pn3MbQ2Gd+mehh9GBZ+36uUQA7Xj 9AGM6wgPhEE34vKtfpAN5tJ8LcFxveDObCKrL7O5UT9WsnAZHv7OYPYSR68mdmnE nJ83M4wQgKO19b+Rt8sPDAz9ptkQsntCn4GeJzg3q2SVc4QJTg/WHo7wF2ah5LMO eh8xJVSKGEmd6uPkSbj113yKMm8vmNptRPmM1+YgmVwcdOYJOjCgFtb2sOP79jji 8uhWR91xx7TpM1K3hv/wrBZwffrmmEpUeuXHRs07JqCCvFh9coKF4UQZvfEg+x3/ 69xRCzb1AgMBAAGjggGtMIIBqTAPBgNVHRMBAf8EBTADAQH/MA4GA1UdDwEB/wQE AwIBBjAdBgNVHQ4EFgQUrlWDb+wxyrn3HfqvazHzyB3jrLswHwYDVR0jBBgwFoAU TgvvGqRAW6UXaYcwyjRoQ9BBrvIwZgYIKwYBBQUHAQEEWjBYMCcGCCsGAQUFBzAB hhtodHRwOi8vb2NzcC5zdGFydHNzbC5jb20vY2EwLQYIKwYBBQUHMAKGIWh0dHA6 Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNydDBbBgNVHR8EVDBSMCegJaAjhiFo dHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwJ6AloCOGIWh0dHA6Ly9j cmwuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDCBgAYDVR0gBHkwdzB1BgsrBgEEAYG1 NwECATBmMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xp Y3kucGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRl cm1lZGlhdGUucGRmMA0GCSqGSIb3DQEBBQUAA4ICAQA6qScNyNO0FpHvaZTQacVM XH33O51KyEKSRw3IvdQxRu31YR0ZDGdSfgSoOVDVMSBSdmfQfdDInHPzV3LO5DwU XZ+lxjv7z3PO2OkfnFkvTXPfn6dxJ5rJveDsTsCPcJ/Kp6/+qN5g+J6D/SaYcFD0 18B6L42r0Z4VEBy36P4tjRtF14Ex10tl5tJFVKM16qWKQHbpjIgf73s49UB0CQ5l HT2DHKfq3oPfdNc5Mk93w1v4ryVb+qVrZIej8NsrWU+5r4O2IV91edDb/OtHFddZ qHFFXKgS79IHE/hwQ2LW7r3sTX7cDUCg+dfdwO8zeLxuwk2JF8crUoyrl66RGrRI hT8VoG/OJ1Y9uUlOav69V4cG8upi4ZG2l7JZFbcBFk91Wp+Payo5SuF61CmGFrZ3 86umkmpObtFacXda2O/bVoQ9xHQrzoTc/0KZTWvlZCLK3Ke/vGYT9ZdW9lOjGsSF bXrlTA919L84iMK+48WGnvRWY28ZaVHpql43AtEGhXze6iNCbEDACy+4hkQYOytA qDgcxAnQ937mYpeZFPyz/XK9QSt9VNFMuudWxZwDDDJKoQAoSG59Hou9lZ26UrK6 0nRdAQBmEPL8h2nuWgoPh++XVQld9yuhbsWa39Pck8/lcfz5HUVGJF5mc/zk38iV 7FDlF68puiryNq2KXHEpOTCCB3kwggZhoAMCAQICAk++MA0GCSqGSIb3DQEBBQUA MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMv U3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0Ew HhcNMTQwNzE5MDUyOTU4WhcNMTYwNzE4MjE1NTM5WjCBjjEZMBcGA1UEDRMQNjlS SUc0ajZNN2ZpNTRURDELMAkGA1UEBhMCSUUxDTALBgNVBAgTBENvcmsxEzARBgNV BAcTCktlcnJ5IFBpa2UxFjAUBgNVBAMTDU5pYWxsIERvdWdsYXMxKDAmBgkqhkiG 9w0BCQEWGXNfc291cmNlZm9yZ2VAbmVkcHJvZC5jb20wggIiMA0GCSqGSIb3DQEB AQUAA4ICDwAwggIKAoICAQC0mleHTofGvJXwH9xAr0+IU5dTotN0BOF1W/vhVoOT bvD0bxesFkPuemSopttKgc94p8FCgEqymbldJrki1cBsc73gODT4XHEigPktcSaF a2jUxkRmL3gfnhEyQ2d7P+ujJCQcur+Ug1xcJjbpQ8eq1dPI6mznITdARqENYqA6 vhH/VNg2n80ksE5HiA1xx2Trd6synZplenahybHkf1pSlyTS9bKeuKi1awIkF/1w QxsckB+ZBHdgPxT/RdFqE7aPF5+VSvbP2wEyieOCWDMCRG4mpsa0Ow54Ytdvf7za 6iGn8VWHwe8E85QpYzfp5RUGsScdo2vcpccLrGDMUDV3AZrcOWmE1r9oAvb3b0o1 4VY+ZE052arIPDpxYUOtpw2/rlxOGrdB1MemXuv2CQx2J2w0p6iOTeISB7xWtIi+ ZuCB5db62NnEh3txKvqDHCX8SYK6qE4PSrnHtb+ziCrYLkQ28lCWUPuwoamstLu0 B8ngNXEoOYuv8ADXc/OufLDrlPt7O0p0QvkEqIexBHCbjiohqFxqvxNxzYo20g5u A3eMymI2F2XOYz/m+muqFYbfy+/2KXrsgjM8oZ5eUqeZES8zY91VH+Ps9ryo/jv/ un6f0FfwzAjO/PkizTxLc5NS138mNBGk/NpWYHCRiTb0A7WiXn2SnpUiGi+IWFyu uQIDAQABo4IC3zCCAtswCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYw FAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBRpgKYvPXl8EYUnJmSNpjoT f/OpKjAfBgNVHSMEGDAWgBSuVYNv7DHKufcd+q9rMfPIHeOsuzAkBgNVHREEHTAb gRlzX3NvdXJjZWZvcmdlQG5lZHByb2QuY29tMIIBTAYDVR0gBIIBQzCCAT8wggE7 BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENl cnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdh cyBpc3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAyIFZhbGlkYXRpb24gcmVx dWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9u bHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhl IHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeGJWh0 dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUyLWNybC5jcmwwgY4GCCsGAQUFBwEB BIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv Y2xhc3MyL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNz bC5jb20vY2VydHMvc3ViLmNsYXNzMi5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqG GGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEAhR1+ CDw7mNmPZUiu/pEteirAI75LpBVUhwuzuU9xfglwFfhAaNX9z95wP3qMphThpIWr kLR4KkMEgHvJTTJ/3KVq0rnNEt2V3605SZDPPlVnt7MMBOlNN8aeClRP62W/GOXa RBfO/w7k8yheUnD8OYtU51rFopIamQkRFXcqdZ0V1rUG0GLiPD1CuRevKop7ebcT YzVFcO0aHFnW2qtn/4OX7W1gQka0pi9zUNXilqXApNjjWIenOtb44KXBFxEqJ7i/ EozUxRExWu7mov+geijuVVYxOT7N7zoQ9aWTJQVn6vNdGqmqZ5XcKtVXHLLFefhh yTBqa0d2jJ4exZYC5TCCB8kwggWxoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwfTEL MAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNl Y3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0 Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA2MDkxNzE5NDYzNloXDTM2 MDkxNzE5NDYzNlowfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0 ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx KTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MIICIjAN BgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAwYjbCbxsRnx4n5V7tTOQ8nJi1sE2 ICIkXs7pd/JDCqIGZKTMjjb4OOYj8G5tsTzdcqOFHKHTPbQzK9Mvr/7qsEFZZ7bE Bn0KnnSF1nlMgDd63zkFUln39BtGQ6TShYXSw3HzdWI0uiyKfx6P7u000BHHls1S Pboz1t1N3gs7SkufwiYv+rUWHHI1d8o8XebK4SaLGjZ2XAHbdBQl/u21oIgP3XjK LR8HlzABLXJ5+kbWEyqouaarg0kd5fLv3eQBjhgKj2NTFoViqQ4ZOsy1ZqbCa3QH 5Cvhdj60bdj2ROFzYh87xL6gU1YlbFEJ96qryr92/W2b853bvz1mvAxWqq+YSJU6 S9+nWFDZOHWpW+pDDAL/mevobE1wWyllnN2qXcyvATHsDOvSjejqnHvmbvcnZgwa SNduQuM/3iE+e+ENcPtjqqhsGlS0XCV6yaLJixamuyx+F14FTVhuEh0B7hIQDcYy fxj//PT6zW6R6DZJvhpIaYvClk0aErJpF8EKkNb6eSJIv7p7afhwx/p6N9jYDdJ2 T1f/kLfjkdLd78Jgt2c63f6qnPDUi39yIs7Gn5e2+K+KoBCo2fsYxra1XFI8ibYZ KnMBCg8DsxJg8novgdujbv8mMJf1i92JV7atPbOvK8W3dgLwpdYrmoYUKnL24zOM XQlLE9+7jHQTUksCAwEAAaOCAlIwggJOMAwGA1UdEwQFMAMBAf8wCwYDVR0PBAQD AgGuMB0GA1UdDgQWBBROC+8apEBbpRdphzDKNGhD0EGu8jBkBgNVHR8EXTBbMCyg KqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2EtY3JsLmNybDAroCmg J4YlaHR0cDovL2NybC5zdGFydGNvbS5vcmcvc2ZzY2EtY3JsLmNybDCCAV0GA1Ud IASCAVQwggFQMIIBTAYLKwYBBAGBtTcBAQEwggE7MC8GCCsGAQUFBwIBFiNodHRw Oi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjA1BggrBgEFBQcCARYpaHR0 cDovL2NlcnQuc3RhcnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwgdAGCCsGAQUF BwICMIHDMCcWIFN0YXJ0IENvbW1lcmNpYWwgKFN0YXJ0Q29tKSBMdGQuMAMCAQEa gZdMaW1pdGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGlt aXRhdGlvbnMqIG9mIHRoZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0 eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9yZy9w b2xpY3kucGRmMBEGCWCGSAGG+EIBAQQEAwIABzA4BglghkgBhvhCAQ0EKxYpU3Rh cnRDb20gRnJlZSBTU0wgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwDQYJKoZIhvcN AQEFBQADggIBABZsmfRmDDT10IVefQrs2hBOOBxe36YlBUuRMsHoO/E93UQJWwdJ iinLZgK3sZr3JZgJPI4b4d02hytLu2jTOWY9oCbH8jmRHVGrgnt+1c5a5OIDV3Bp lwj5XlimCt+MBppFFhY4Cl5X9mLHegIF5rwetfKe9Kkpg/iyFONuKIdEw5Aa3jip PKxDTWRFzt0oqVzyc3sE+Bfoq7HzLlxkbnMxOhK4vLMR5H2PgVGaO42J9E2TZns8 A+3Tmh2a82VQ9aDQdZ8vr/DqgkOY+GmciXnEQ45GcuNkNhKv9yUeOImQd37Da2q5 w8tES6x4kIvnxyweSxFEyDRSJ80KXZ+FwYnVGnjylRBTMt2AhGZ12bVoKPthLr6E qDjAmRKGpR5nZK0GLi+pcIXHlg98iWX1jkNUDqvdpYA5lGDANMmWcCyjEvUfSHu9 HH5rt52Q9CI7rvj8Ksr6glKg769LVZPrwbXwIousNE4mIgShhyx1SrflfRPXuAxk wDbSyS+GEowjCcEbgjtzSaNqV4eU5dZ4xZlDY+NN4Hct4WWZcmkEGkcJ5g8BViT7 H78OealYLrnECQF+lbptAAY+supKEDnY0Cv1v+x1v5cCxQkbCNxVN+KB+zeEQ2Ig yudWS2Xq/mzBJJMkoTTrBf+aIq6bfT/xZVEKpjBqs/SIHIAN/HKK6INeMYIDGjCC AxYCAQEwgZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgw NgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs aWVudCBDQQICT74wCQYFKw4DAhoFAKBdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B BwEwHAYJKoZIhvcNAQkFMQ8XDTE2MDUxNDIwMTQwMFowIwYJKoZIhvcNAQkEMRYE FJd00ELGADNb1Jtlgwz93OHOLdd1MA0GCSqGSIb3DQEBAQUABIICABzsuVBeC1Ov 93IY7YRk/F8hN9J3O2ln6xDOfgqbsML4ZaDFWDkmB3ycQ6T1/AS1jwKBFAHBX7/w UzPEUV2InX9a2RCf3gS/0bVCd+36azWILj1xRjH722fxADlTXSHA0G3yofgyzIcm +6KlrGiSpmgnXo9ILe8NBKgzvrU2KtSfT4eDEPPZF9V9Ui4mP0R04zNxw7sXWwuR zHE72Z38XLCWI+46GHpiKywXspsP+pbFcoXpHPjnVk9gatCzPbwaIxJZHsqTqyiT xjLkMug7CCrWpaYAod/aqRXD6l0I8+KaAbr+EYfvzMMJ7L/oGYubruSMtMK5O4Nr YaKCRJDAYIMaC2+6uuVUMlTF0mifKECXUKrIJ23gULLTYsd15ifPglZxSXi+hCZS 6fHy/wlhjpnR74LllwP41cIXy2VrC5NVnbzSSKPgPXEm47aJXiayvpg6/x9LAAQt pXJb5rw7CK9QZ0UzeOdAPPzTzujitTkLLBdhumPbZjFFDnaxgjKpPaK06vfeV9Ky yJIfc8gS5N0bnlUwO0JvFe9rNQ15cnIaiA1Lm+msnTvtNvj3Iz6hbMPaijA4KYZ/ Hk/BVer/oB2gjnXHZ7w+S2VO7K/OVFD9kV1urVLIfTCxLATdM3DN2p86LUmkiJ5D ydtN1HZa1+UAqAxndegubxsxhpFjgh0E --SMime-=-=-Boundary-=-=-F1A5CA31-- From owner-freebsd-fs@freebsd.org Sat May 14 23:09: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 C357DB3B3AE for ; Sat, 14 May 2016 23:09:37 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::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 97AA012EE for ; Sat, 14 May 2016 23:09:37 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-io0-x235.google.com with SMTP id f89so172159358ioi.0 for ; Sat, 14 May 2016 16:09:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=FHhEIaJOoVDM3Sdew5YBzjDfAKivihrgG2u+nI9zunA=; b=p2gHDk2WZoCRe/AMR0cmBz/8nJHIIhbYlPhjeHtNgmJHQtPBPKujxKri+fPwS3K/ph 4rMhjRc3ggcdJ1ARAgUJt1wAFgiy/jQdQEVvMTvtNKTbYSBgidb1Yebcw7mTvWAFz1yH tcQbdNI663NMFuznjiZawvZz9sc35NSBLt5znPyvxJVVQoNpJ091H3b8wDyvQmHviYHh 7gUjWnXkwpjPxnHzyNX15srWDb5Hq10DePmeZ6elh30EpTa1/WYIKG7bT9tJ4YFxaYOw n5YUkyj30ImIC0A4YlZU+8c/y0Jaj9aN0hNvT4poVW92LBGlsb+jVi2+Wbgbl5r7VWXq KMJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=FHhEIaJOoVDM3Sdew5YBzjDfAKivihrgG2u+nI9zunA=; b=BEdqmGMT+L/VLVDMRfHHUIQjl2ntMGnRu46D/w16uPyWt/+ucrkQ6w0FcsEgWebdLc FnGJULg/wFAeqCNS0tZJHIWI/7izHGSkuC2YqBJoM/yN/Cvo7uRUd2dG7WxEdlFcEgzR wzkmhTyG3o8n8RkphE5imdd/IBHQXLexF3wDQ9gYhKMGZvlIxocJz8cht5U/mJuG0YBS qzbKwcn3yCV+Tw/v9sa4KXkPxPYCsiZ6A+7CSJvcebrHrh2Ret4GJgfx93E4qNZNLpTC yVLNrC50ONnxTni04P9XjyzhZbmqRTWLajWlq6VQnKFZe74IE4r5tKlckgMuzIyQoZ7O 6Qhw== X-Gm-Message-State: AOPr4FUbaPJzRUqwJB8iz51ykS/qXiWlGxLhmT4Qq24w6B05Px0UqPhny0ZRzjn5BL8+Y5M6x9gZoTdZaBNKhA== MIME-Version: 1.0 X-Received: by 10.107.7.170 with SMTP id g42mr15472224ioi.81.1463267376914; Sat, 14 May 2016 16:09:36 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.107.140.8 with HTTP; Sat, 14 May 2016 16:09:36 -0700 (PDT) In-Reply-To: <57378707.19425.B54772B@s_sourceforge.nedprod.com> References: <5736E7B4.1000409@gmail.com> <0CE6E456-CC25-4AED-A73E-F5BBE659F795@mail.turbofuzz.com> <57378707.19425.B54772B@s_sourceforge.nedprod.com> Date: Sat, 14 May 2016 16:09:36 -0700 X-Google-Sender-Auth: YAhRioaOhietV_bBq9529mueY08 Message-ID: Subject: Re: State of native encryption in ZFS From: "K. Macy" To: Niall Douglas Cc: "freebsd-fs@FreeBSD.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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, 14 May 2016 23:09:37 -0000 On Sat, May 14, 2016 at 1:13 PM, Niall Douglas via freebsd-fs wrote: > On 14 May 2016 at 11:03, Jordan Hubbard wrote: > >> It=E2=80=99s not even clear how that encryption would be implemented or = exposed. >> Per pool? Per dataset? Per folder? Per file? There have been >> requests for all of the above at one time or another, and the key >> management challenges for each are different. They can also be >> implemented at a layer above ZFS, given sufficient interest. > > If FreeBSD had a bigger PATH_MAX then stackable encryptions layers > like ecryptfs (encfs?) would be viable choices. Because encrypted > path components are so long, one runs very rapidly into the maximum > path on the system when PATH_MAX is so low. > > I ended up actually installing ZFS on Linux with ecryptfs on top to > solve this. Every 15 minutes it ZFS snapshot syncs with the FreeBSD > edition. This works very well, apart from the poor performance of ZFS > on Linux. > > ZFS handles long paths with ease. FreeBSD currently does not :( > AFAICT that's a 1 line patch. Have you tried patching that and rebuilding kernel, world, and any vulnerable ports? -M