On 9/13/2011 5:07 AM, Paul Kraus wrote:
Patch-ID# 144500-19 is the kernel update that is the kernel from
10U10
Yep, the guy posting on sunmanagers confirmed that was the patch he
installed which broke aclmode.
Did update 10 sneak out under cover of darkness or what? I didn't see
any announcements or chatter about it, google doesn't find anything, and
the Oracle download site still only shows update 9:
http://www.oracle.com/technetwork/server-storage/solaris/overview/solaris-latest-version-170418.html
Thank you for flagging this, as Oracle support is telling me I have
to update to this release to get zpool 26 which fixes a zfs bug we
are running into, but if it breaks the ACL inheritance we have been
using, then it is non-starter.
Yup. Fortunately, there are no critical bugs (that Oracle is willing to
fix 8-/) that I've been waiting for. I thought I'd be able to keep an
up-to-date S10 install going while I figure out what to do next; guess
not :(.
He already opened a support ticket, they responded:
-----
ZFS appears to be the only file system supporting NFSv4 ACLs
that attempts to preserve ACLs during chmod(2) operations.
Unfortunately, this requires the ACL to be modified in ways that are
confusing to customers and the time has come to stop the confusion and
to just "discard" the ACL during chmod(2) operations. This implies that
the ZFS aclmode property will no longer be needed and will be removed
from ZFS.
This functionality is targetted to be back in Solaris 11 - as per
CR7002239 want ZFS aclmode property back
-----
Interesting that there's already a new CR to put it back -- I thought
that bridge was already burned. It's already back in Illumos. I wonder
how long it will take to get put back in S10; or I guess it could be one
of those CR's that never gets resolved. I suppose I'll open my own
ticket to voice support.
runs the system out of RAM. The snapshot is a partial zfs recv. I am
told this is a known bug (destruction of large snapshots can run the
system out of RAM as the destroy operation commits as one TXG). There
is a fix, but it in the on-disk format, so just zpool upgrading to
version 26 will not fix existing snapshots. We only have 32 GB in
this system and the faulty snapshot *should* be about 2.5 TB.
Hmm, if updating the zpool won't fix the existing snapshot, how is
support telling you to recover? Is it going to be one of those wipe and
rebuild resolutions 8-/? Good luck...
I imagine a pool upgraded to version 26 will no longer be compatible
with other zfs implementations.
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | hen...@csupomona.edu
California State Polytechnic University | Pomona CA 91768
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
