On Tue, Oct 27 2015 09:49:40 +0100, Jim Klimov wrote:
> So far I use a mix of 'standard' time-slider and additionally my script that
> kills oldest snapshot groups (chosen by pattern of automatic snaps) to keep a
> specified watermark of free space.
Yeah, we were previously using zfs-auto-snap
we’ve been using this, fired off by cron:
https://github.com/MSU-iCER/puppet-zfs-auto-snapshot/blob/master/files/zfs-auto-snapshot.pl
We manage it via puppet. It’s a bit of an older puppet module, but should still
work.
-Greg
> On Oct 27, 2015, at 7:07 AM, Lauri Tirkkonen
27 октября 2015 г. 9:49:40 CET, Jim Klimov пишет:
>23 октября 2015 г. 19:10:47 CEST, Lauri Tirkkonen
>пишет:
>>On Fri, Oct 23 2015 18:54:27 +0200, Jim Klimov wrote:
>>> 23 октября 2015 г. 11:23:28 CEST, Jim Klimov пишет:
>>> >So at the moment it seems
On Tue, Oct 27 2015 12:05:31 +0100, Jim Klimov wrote:
> Heh, in fact this OmniOS installation does not offer a time-slider, but
> rather the ksh93-based scripts for 'zfs/autosnapshot'. Now gotta verify what
> i run elsewhere;)
I think OmniOS ships neither time-slider nor zfs-auto-snapshot. When
Hi Dan,
Now I get :-
root@hp:/root/fio-2.1.10# pkgrecv -s
http://pkg.omniti.com/omnios/r151014/ -d /tank/repo '*'
Processing packages for publisher omnios ...
Retrieving and evaluating 6160 package(s)...
PROCESS ITEMSGET (MB) SEND
(MB)
developer/gcc48
Try -m latest... it could just be the sheer number of packages you're
transferring. We still use the tiny CherryPy webserver at the repo-box end.
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com