Nathan Kunkee<[email protected]> writes:
Hi!
I'm not sure if it relates to your issue, see below, but I had to add
I believe a profile (Basic Solaris User?) to zfssnap for that error to
go away. You may check that the zfssnap user has similar RBAC privs as
below:
Thanks for the detailed input... and showing a quick way to check stuff.
I seem to have all the same settings here:
nathan@openindiana:/tmp$ roles zfssnap
No roles
# roles zfssnap
No roles
nathan@openindiana:/tmp$ auths zfssnap
solaris.admin.wusb.read,solaris.device.cdrw,solaris.device.mount.removable,solaris.mail.mailq,solaris.profmgr.read,solaris.smf.manage.zfs-auto-snapshot
# auths zfssnap
solaris.admin.wusb.read,solaris.device.cdrw,solaris.device.mount.removable,solaris.mail.mailq,solaris.profmgr.read,solaris.smf.manage.zfs-auto-snapshot
nathan@openindiana:/tmp$ profiles zfssnap
zfssnap:
ZFS File System Management
Basic Solaris User
All
# profiles zfssnap
zfssnap:
ZFS File System Management
Basic Solaris User
All
nathan@openindiana:/tmp$ getent passwd zfssnap
zfssnap:x:51:12:ZFS Automatic Snapshots Reserved UID:/:/usr/bin/pfsh
getent passwd zfssnap
zfssnap:x:51:12:ZFS Automatic Snapshots Reserved UID:/:/usr/bin/pfsh
Also, check if any of your datasets have the correct attribute:
zfs get com.sun:auto-snapshot
zfs get com.sun:auto-snapshot|wc -l
24
(just one example:
zp2/hosts/reader com.sun:auto-snapshot true inherited from zp2)
zp2 is the only zpool (besides rpool) so all zfs fs created on it
have inherited that setting
Since time-slider will only archive entries with a true value for that
attribute. For some of my systems, that was on by default; for some,
I've had to manually enable it. (I've had to use the zfs command since
the Nautilus GUI doesn't like NFS.)
I'm not sure now if it was already on everywhere... it is on rpool,
but I set it as I went; creating zfs fs on zp2.
