Hi all, Got a quick question: what are the latest zpool and zfs versions supported in Solaris 10 Update 10? TIA, -- Rich Teer, Publisher Vinylphile Magazine www.vinylphilemag.com
On 09/30/11 11:59 AM, Rich Teer wrote:> Hi all, > > Got a quick question: what are the latest zpool and zfs versions > supported in Solaris 10 Update 10? >In update 10: pool version 29, ZFS version 5. -- Ian.
> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- > bounces at opensolaris.org] On Behalf Of Ian Collins > > > Got a quick question: what are the latest zpool and zfs versions > > supported in Solaris 10 Update 10? > > > In update 10: pool version 29, ZFS version 5.I don''t know what the other differences are, but the first one I noticed is the sync property. Even if you don''t zpool upgrade or zfs upgrade, just by applying the patches to an older solaris 10, you can''t disable ZIL anymore via /etc/system. At least not in the way that formerly worked, as described on the evil tuning guide. Now you use the sync property instead. This is a change for positive, but surprised me.
On Thu, Sep 29, 2011 at 9:51 PM, Edward Ned Harvey <opensolarisisdeadlongliveopensolaris at nedharvey.com> wrote:>> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- >> bounces at opensolaris.org] On Behalf Of Ian Collins >> >> > Got a quick question: what are the latest zpool and zfs versions >> > supported in Solaris 10 Update 10? >> > >> In update 10: pool version 29, ZFS version 5. > > I don''t know what the other differences are, but the first one I noticed is > the sync property. ?Even if you don''t zpool upgrade or zfs upgrade, just by > applying the patches to an older solaris 10, you can''t disable ZIL anymore > via /etc/system. ?At least not in the way that formerly worked, as described > on the evil tuning guide. ?Now you use the sync property instead. ?This is a > change for positive, but surprised me.Another potential difference ... I have been told by Oracle Support (but have not yet confirmed) that just running the latest zfs code (Solaris 10U10) will disable the aclmode property, even if you do not upgrade the zpool version beyond 22. I expect to test this next week, as we _need_ ACLs to work for our data. -- {--------1---------2---------3---------4---------5---------6---------7---------} Paul Kraus -> Senior Systems Architect, Garnet River ( http://www.garnetriver.com/ ) -> Sound Coordinator, Schenectady Light Opera Company ( http://www.sloctheater.org/ ) -> Technical Advisor, RPI Players
On 29/09/2011 23:59, Rich Teer wrote:> Hi all, > > Got a quick question: what are the latest zpool and zfs versions > supported in Solaris 10 Update 10? > > TIA, >root at pstx2200a # zfs upgrade -v The following filesystem versions are supported: VER DESCRIPTION --- -------------------------------------------------------- 1 Initial ZFS filesystem version 2 Enhanced directory entries 3 Case insensitive and File system unique identifier (FUID) 4 userquota, groupquota properties 5 System attributes For more information on a particular version, including supported releases, see the ZFS Administration Guide. root at pstx2200a # zpool upgrade -a This system is currently running ZFS pool version 29. All pools are formatted using this version. root at pstx2200a # cat /etc/release Oracle Solaris 10 8/11 s10x_u10wos_17b X86 Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. Assembled 23 August 2011 root at pstx2200a #
On Thu, Sep 29, 2011 at 07:13:40PM -0700, Paul Kraus wrote:> Another potential difference ... I have been told by Oracle Support > (but have not yet confirmed) that just running the latest zfs code > (Solaris 10U10) will disable the aclmode property, even if you do not > upgrade the zpool version beyond 22. I expect to test this next week, > as we _need_ ACLs to work for our data.I haven''t installed U10, but have confirmed that installing the U10 kernel patch removes aclmode :(. Didn''t expect that Solaris 11 change to be backported... I personally have SR 3-4631579271 open requesting that breakage be fixed, referencing CR #7002239 which is an RFE to restore aclmode to Solaris 11. If you have a service contract and care (or even if you don''t care but would like to help out those who do ;) ), open a ticket requesting the fix for CR #7002239 and get some weight behind it :). Support''s recommended workaround is basically "don''t use chmod" 8-/. As if you can control all the things that call chmod behind your back, let alone the NFS exclusive open issue which stomps on your ACL no matter *what* you do <sigh>... What makes this even more annoying is that U10 backports ngroups_max=1024 support, which I could *really* *really* use... -- Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/ Operating Systems and Network Analyst | henson at csupomona.edu California State Polytechnic University | Pomona CA 91768
On Wed, Oct 5, 2011 at 5:56 PM, Paul B. Henson <henson at acm.org> wrote:> On Thu, Sep 29, 2011 at 07:13:40PM -0700, Paul Kraus wrote: > >> Another potential difference ... I have been told by Oracle Support >> (but have not yet confirmed) that just running the latest zfs code >> (Solaris 10U10) will disable the aclmode property, even if you do not >> upgrade the zpool version beyond 22. I expect to test this next week, >> as we _need_ ACLs to work for our data. > > I haven''t installed U10, but have confirmed that installing the U10 > kernel patch removes aclmode :(. Didn''t expect that Solaris 11 change toI have also confirmed that it is a code change and not tied to on-disk format. A version 22 zpool, when imported on a system with the 10U10 kernel, no longer includes aclmode.> be backported... I personally have SR 3-4631579271 open requesting that > breakage be fixed, referencing CR #7002239 which is an RFE to restore > aclmode to Solaris 11. If you have a service contract and care (or even if > you don''t care but would like to help out those who do ;) ), open a > ticket requesting the fix for CR #7002239 and get some weight behind it > :).I have been told by Oracle Support (not first line, but someone from engineering in response to an escalation) that the code is done to put aclmode back in, and that an IDR can probably be cut against the 10U10 kernel. They are finding out when it will be integrated. We need a snapshot deletion fix that is in zpool 26, but we also need aclmode (or at least functional ACLs), which was removed in the 10U10 kernel.> Support''s recommended workaround is basically "don''t use chmod" 8-/. As > if you can control all the things that call chmod behind your back, let > alone the NFS exclusive open issue which stomps on your ACL no matter > *what* you do <sigh>...> What makes this even more annoying is that U10 backports > ngroups_max=1024 support, which I could *really* *really* use...-- {--------1---------2---------3---------4---------5---------6---------7---------} Paul Kraus -> Senior Systems Architect, Garnet River ( http://www.garnetriver.com/ ) -> Sound Coordinator, Schenectady Light Opera Company ( http://www.sloctheater.org/ ) -> Technical Advisor, RPI Players
On Wed, Oct 05, 2011 at 07:28:02PM -0700, Paul Kraus wrote:> I have been told by Oracle Support (not first line, but someone > from engineering in response to an escalation) that the code is done > to put aclmode back in, and that an IDR can probably be cut against > the 10U10 kernel. They are finding out when it will be integrated.I just got an update on my ticket indicating they plan to restore aclmode in U11, and asking if I can just wait for that. I''m going to push for a U10 patch to restore it and an IDR pending that. What a waste of effort all around :(, it really shouldn''t have been removed in the first place IMHO. -- Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/ Operating Systems and Network Analyst | henson at csupomona.edu California State Polytechnic University | Pomona CA 91768
Hi all, I have a customer who wants to know what is the max characters allowed in creating name for zpool, Are there any restrictions in using special characters? Thanks in advance for advise. Adele
On Tue, October 25, 2011 09:42, Adele.liu at oracle.com wrote:> Hi all, > > I have a customer who wants to know what is the max characters allowed > in creating name for zpool, > > Are there any restrictions in using special characters?255 characters. Try doing a ''man zpool'': Creates a new storage pool containing the virtual devices specified on the command line. The pool name must begin with a letter, and can only contain alphanumeric characters as well as underscore ("_"), dash ("-"), and period ("."). The pool names "mirror", "raidz", "spare" and "log" are reserved, as are names beginning with the pattern "c[0-9]". The vdev specification is described in the "Virtual Devices" section. Or, use the source Luke: Going to http://src.opensolaris.org, and searching for "zpool" turns up: http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/zpool/zpool_main.c Inside of it we have a zpool_do_create() function, which defines a ''char *poolname'' variable. From there we call a zpool_create() in libzfs/common/libzfs_pool.c to zpool_name_valid() to pool_namecheck(), where we end up with the following code snippet: /* * Make sure the name is not too long. * * ZPOOL_MAXNAMELEN is the maximum pool length used in the userland * which is the same as MAXNAMELEN used in the kernel. * If ZPOOL_MAXNAMELEN value is changed, make sure to cleanup all * places using MAXNAMELEN. */ if (strlen(pool) >= MAXNAMELEN) { if (why) *why = NAME_ERR_TOOLONG; return (-1); } Check the function for further restrictions: http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/common/zfs/zfs_namecheck.c#288
David, Appreciated so much for your sharing. Best Regards, Adele On 10/25/2011 10:23 AM, David Magda wrote:> On Tue, October 25, 2011 09:42, Adele.liu at oracle.com wrote: >> Hi all, >> >> I have a customer who wants to know what is the max characters allowed >> in creating name for zpool, >> >> Are there any restrictions in using special characters? > 255 characters. Try doing a ''man zpool'': > > Creates a new storage pool containing the virtual devices specified > on the command line. The pool name must begin with a letter, and > can only contain alphanumeric characters as well as underscore > ("_"), dash ("-"), and period ("."). The pool names "mirror", > "raidz", "spare" and "log" are reserved, as are names beginning > with the pattern "c[0-9]". The vdev specification is described in > the "Virtual Devices" section. > > Or, use the source Luke: > > Going to http://src.opensolaris.org, and searching for "zpool" turns up: > > http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/zpool/zpool_main.c > > Inside of it we have a zpool_do_create() function, which defines a ''char > *poolname'' variable. From there we call a zpool_create() in > libzfs/common/libzfs_pool.c to zpool_name_valid() to pool_namecheck(), > where we end up with the following code snippet: > > /* > * Make sure the name is not too long. > * > * ZPOOL_MAXNAMELEN is the maximum pool length used in the userland > * which is the same as MAXNAMELEN used in the kernel. > * If ZPOOL_MAXNAMELEN value is changed, make sure to cleanup all > * places using MAXNAMELEN. > */ > if (strlen(pool)>= MAXNAMELEN) { > if (why) > *why = NAME_ERR_TOOLONG; > return (-1); > } > > Check the function for further restrictions: > > http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/common/zfs/zfs_namecheck.c#288 > >