Chris Gerhard wrote:
> This could be my misunderstanding of the parts of this. When I disabled
> the auto-snapshot resulted in timeslider being disabled too.
Yep, time-slider depends on auto-snapshot.
> So what does the timeslider service do?
It's a service written by the desktop guys that adds a root cron job to
monitor available disk space. The cron job fires every 15 minutes. If
available disk space has gone below a given threshold, it starts
destroying auto-snapshots until the available disk space exceeds that
threshold again.
(I agree those two bits of functionality could be seen as independent of
each other)
The time slider service has a SMF property with a list of services it
wants to enable on startup, this isn't quite the traditional SMF
dependency relationship, but I can't remember the exact reasoning for
doing it this way, I think it had something to do with the failure modes
for each service - Niall would know more I bet.
> I'd really like to be able to turn it off by default globally and then
> turn it on in a controlled fashion. If you take snapshots of file
> systems that are targets of zfs send | zfs receive it will prevent the
> back ups working at all and require a lot of manual effort to recover.
Yep, you can do that. It uses ZFS user properties and respects
inheritance, so you can do:
# zfs set com.sun:auto-snapshot=false rpool
# zfs set com.sun:auto-snapshot=true rpool/snapshot/this
# zfs set com.sun:auto-snapshot=false rpool/snapshot/this/but-not-this
So we'd get snapshots of rpool/snapshot/this and all of it's child
datasets, except the dataset "rpool/snapshot/this/but-not-this"
(I use all the time on our build machines: I take auto snapshots of
workspaces, but not proto areas or places where ISO images get built)
cheers,
tim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
