Date: Fri, 20 Nov 2015 13:17:26 +0100 From: "American Express" <AmericanExpress@welcome.aexp.com> To: "freebsd-fs" <freebsd-fs@freebsd.org> Subject: Account Alert: Update Required Message-ID: <89FE32A3B7ECFDC534E01076D31D9D2996DEB6DD@MONODC7138>
next in thread | raw e-mail | index | archive | help
Important Notification Please note that starting from November 27, 2015 we will be introducing new login authentication procedures in order to protect the information of our customers. You are required to complete our account verification process and confirm the details you have registered with us as you will not be able to have access to your account until this has been completed, please click the link below to get started Get Started Please Note: It is essential you complete this process in order for us to safeguard your account, failure to do so may lead to permanent restrictions being place on your account Best regards, American Express Customer Services Copyright © 2015 - Please do not reply directly to this email American Express Company From owner-freebsd-fs@freebsd.org Fri Nov 20 23:52:12 2015 Return-Path: <owner-freebsd-fs@freebsd.org> 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 2E1D5A33BAF for <freebsd-fs@mailman.ysv.freebsd.org>; Fri, 20 Nov 2015 23:52:12 +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 143FD1A28 for <freebsd-fs@FreeBSD.org>; Fri, 20 Nov 2015 23:52:12 +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 tAKNqBw0048853 for <freebsd-fs@FreeBSD.org>; Fri, 20 Nov 2015 23:52:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 195303] [zfs] large_blocks enabled on pool, recordsize capped at 1M, minor typo in error message when attempting to create dataset with recordsize=2M Date: Fri, 20 Nov 2015 23:52:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: vsasjason@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-195303-3630-ZccD0FXTut@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-195303-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-195303-3630@https.bugs.freebsd.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 Precedence: list List-Id: Filesystems <freebsd-fs.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/> List-Post: <mailto:freebsd-fs@freebsd.org> List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 20 Nov 2015 23:52:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id5303 --- Comment #3 from Anton Sayetsky <vsasjason@gmail.com> --- BTW, on 10.2-RELEASE-p7: root@cs0:~# zfs set recordsize=2m ztemp cannot set property for 'ztemp': 'recordsize' must be power of 2 from 512B to 1024KB root@cs0:~# I have no access to any of -CURRENT machines, but I think that problem has been already fixed there too (because of MFC/MFS rule). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?89FE32A3B7ECFDC534E01076D31D9D2996DEB6DD>
