Well, as a simple stone-age solution (to simplify your SMF approach),
you can define custom attributes on dataset, zvols included. I think
a custom attr must include a colon ":" in the name, and values can be
multiline if needed. Simple example follows:
# zfs set owner:user=jim pool/rsvd
# zfs set owner:group=staff pool/rsvd
# zfs set owner:chmod=777 pool/rsvd
# zfs set owner:acl="`ls -vd .profile`" pool/rsvd
# zfs get all pool/rsvd
...
pool/rsvd owner:chmod 777
local
pool/rsvd owner:acl -rw-r--r-- 1 root root
54 Nov 11 22:21 .profile
0:owner@:read_data/write_data/append_data/read_xattr/write_xattr
/read_attributes/write_attributes/read_acl/write_acl/write_owner
/synchronize:allow
1:group@:read_data/read_xattr/read_attributes/read_acl/synchronize:allow
2:everyone@:read_data/read_xattr/read_attributes/read_acl/synchronize
:allow local
pool/rsvd owner:group staff
local
pool/rsvd owner:user jim
local
Then you can query the zvols for such attribute values and use them
in chmod, chown, ACL settings, etc. from your script. This way the
main goal is reached: the ownership config data stays within the pool.
HTH,
//Jim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
